Preparing your team for a website redesign: content, decisions, and stakeholders

Why redesign projects often feel chaotic inside the company

From the outside, a website redesign looks simple: hire a team, discuss goals, choose a direction, build, launch.

Inside the company, the experience can feel very different. Departments push for their section to be prominent. Content appears late or not at all. Decision-makers join meetings halfway through the project and question fundamental choices. What should have been a three-month redesign turns into a year of small crises.

Most of these problems are not technical; they are organisational. The good news is that you can reduce a lot of the chaos with preparation that has nothing to do with layout files or frameworks.

This article focuses on that preparation. It complements the pieces on redesign ROI, timelines, and project briefs by looking at what you need to do inside your team before a redesign starts.

Step 1: appoint a real project owner

“We will decide together” sounds nice, but it rarely works for design decisions.

Without a clear project owner, every choice becomes a negotiation between different preferences. Design reviews turn into long discussions where nobody feels responsible for closing them. External partners receive mixed signals and are forced to guess whose opinion matters most.

A real project owner:

• Understands the business goals behind the redesign.
• Has enough authority to make decisions and say “no” when needed.
• Is available throughout the project instead of disappearing after kickoff.

They do not have to decide everything alone, but they are the person who synthesises input and carries responsibility. In small companies this is often the founder or managing director; in larger ones, a marketing or product lead.

Step 2: decide where content will come from

Content is one of the most common reasons redesigns slip.

If nobody owns it, content reviews get pushed to “later”, and layouts are built on placeholders. When real copy finally appears, it does not fit the structure, forcing extra rounds of design and development work.

Before you start, answer a few simple questions:

• Which pages will reuse and polish existing content, and which need to be written from scratch?
• Who is responsible for drafting each key page? Who edits and approves?
• Do you need external copywriting support, and is that budgeted?

You do not need final text before design begins, but you do need ownership. Even outlines or bullet points for each page are enough to give designers and developers something real to work with.

Step 3: create a decision framework instead of endless debates

Many redesign arguments are not about the details people claim. They are about different ideas of what the site is supposed to achieve.

One person wants maximum lead volume. Another wants to attract only large, long-term clients. A third wants the site to impress potential hires. The homepage cannot be everything at once.

It helps to write down a small set of priorities before design work starts:

• What are the top two or three outcomes this redesign must support?
• Which audiences are primary, and which are secondary?
• If there is a trade-off between two goals, which one wins?

You can still listen to feedback from across the company, but you judge suggestions against this framework. That keeps reviews focused and gives your external partner a way to resolve conflicts constructively.

Step 4: align expectations about timelines and workload

Redesigns feel more stressful when everyone treats them as something that will magically fit into existing workloads.

Content owners think they will “find time” to write pages. Decision-makers assume they will only be needed for one or two reviews. In reality, both groups have to make space for the project across several weeks or months.

Before you commit to a timeline, be honest about internal capacity:

• How many hours per week can the project owner realistically dedicate?
• When are key decision-makers likely to be unavailable because of travel, quarter-end, or major launches?
• Do content owners have dedicated time blocked, or are you hoping they will write copy between other tasks?

Matching your internal reality to the external timeline avoids a lot of frustration later.

Step 5: communicate the plan to the rest of the company

Even people who are not directly involved will care about how the website represents their work. If they only hear about the redesign when everything is almost finished, they may push back simply because they feel excluded.

A short, clear internal message early in the project can help:

• Explain why the redesign is happening and what outcomes you expect.
• Name the project owner and content leads so people know whom to talk to.
• Set expectations: who will be consulted, who will decide, and how feedback will be handled.

This does not eliminate all late opinions, but it makes them easier to manage because the structure was clear from the start.

Making your next redesign less painful

Create a one-page decision map before kickoff

A redesign becomes easier when everyone can see who contributes, who recommends, and who decides. You do not need a complicated governance model. A one-page decision map is enough:

The important rule is that every line has one final decision-maker. “Leadership team” is not a decision-maker unless that group has a defined voting or escalation process.

Also agree on what happens when the final decision-maker does not respond. A two-business-day review window with documented approval is more useful than an open-ended request for feedback.

Audit content and evidence, not only pages

Most redesign inventories list URLs but miss the material needed to create credible pages. Build a second inventory for evidence:

• approved client logos and testimonials;
• case-study metrics and who can approve them;
• product screenshots or service-process visuals;
• team biographies and current photography;
• security, compliance, accessibility, or certification statements;
• pricing logic, qualification rules, and sales objections;
• legal copy and the owner responsible for validating it.

Mark every item as ready, needs revision, missing, or blocked. This makes the real project risk visible early. A missing homepage paragraph is easy to write; six unapproved case studies can delay an entire launch.

Content ownership should include acceptance criteria. “Marketing writes the services page” is vague. “Marketing provides an approved draft covering audience, problem, approach, evidence, and CTA by the end of week three” can be scheduled and reviewed.

Set a feedback protocol that protects the work

Feedback becomes chaotic when reviewers comment from different assumptions. Give every reviewer the same structure:

1. Which project goal does this feedback support?
2. Is it a factual correction, a legal requirement, a usability concern, or a preference?
3. What user or business risk appears if it is not changed?
4. Is the reviewer asking for a launch requirement or a later improvement?

Collect feedback in one place and one review window. The project owner should resolve contradictions before the design or development partner acts on them. Forwarding two conflicting comments and asking the supplier to “find a compromise” transfers an internal decision problem to the wrong person.

For visual reviews, evaluate hierarchy, comprehension, trust, and task completion before discussing isolated aesthetic preferences. For content reviews, verify accuracy and buyer clarity before polishing individual sentences.

Run a redesign readiness check

Before committing to a launch date, confirm:

• a project owner has protected weekly time;
• final decision-makers are named and available;
• the sitemap has an owner;
• priority-page content has a realistic production plan;
• evidence and assets have been inventoried;
• legal and privacy review has an owner;
• analytics, CRM, forms, and other integrations are documented;
• feedback windows and escalation rules are agreed;
• known holidays, launches, and approval bottlenecks are reflected in the schedule.

If several items are missing, start with a short discovery and content-preparation phase. That is not wasted time. It converts hidden delays into explicit work before designers and developers are waiting on decisions.

Package the result into a small kickoff folder: decision map, current analytics baseline, content and evidence inventory, known technical integrations, brand assets, legal owners, and the approved brief. A partner can begin useful work immediately when these inputs are current and clearly owned.

Preparing your team for a redesign does not require a huge internal project. It requires a few deliberate choices made before you sign contracts.

• Choose a project owner with enough authority and time.
• Assign content ownership for key pages.
• Write down a simple decision framework everyone can reference.
• Be realistic about internal workload and block time accordingly.
• Communicate the plan so people know how and when to contribute.

Combined with a solid brief and realistic external timeline, these steps turn a redesign from a slow-moving internal argument into a focused collaboration. Your external partner can then do what you hired them for: designing and building a site that supports your business, instead of trying to mediate debates that could have been resolved before the project even started.