PROJECT MANAGEMENT

Website redesign work breakdown structure.

A website redesign WBS separates research, design, production and launch work. It gives the project team a shared view of what must be delivered before the new site can go live. The structure starts with a content audit and goals because these decisions inform the sitemap and prototypes. The build phase then separates writing from development, which helps different specialists plan their work. Add technical migration, accessibility or analytics work when it belongs to the project, and use the WBS as the source for a detailed schedule and ownership plan.

UPDATED 2026-09-24
EXAMPLEWebsite redesign work breakdown structure.
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

website-planning

Key decisions

  • Discovery scope: Audit the existing content before deciding what to change.
  • Structure first: Approve the sitemap before detailed prototypes.
  • Launch quality: Include testing and measurement in the delivery scope.

When to reuse this

Use this WBS to plan a small website redesign.

FAQ

Frequently asked questions

Why start a redesign WBS with discovery?01
The audit and goals define what the redesign needs to achieve.
Does the WBS include a sitemap?02
Yes. A sitemap is a design deliverable that should be approved before build work.
Where does testing belong?03
Testing is a launch work package, before the site is released.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.