How to Manage a Website Redesign Project
How to manage a website redesign project from kickoff to launch — timeline, stakeholder communication, review cycles, and risk management.

How to manage a website redesign project is a question most clients underestimate until a milestone is missed. The agency handles the craft.
The client manages the inputs, approvals, and decision-making that determine whether the project reaches launch on time and within budget.
Understanding the client's role in project management changes everything about how you approach the engagement. Most redesign delays are client-side in origin, not agency-side.
This guide gives you the practical management skills to own your side of the project effectively.
Key Takeaways
- The client is a core team member: Project management responsibility is not outsourced to the agency; the client owns content delivery, feedback, and sign-off.
- Proactive management beats reactive firefighting: Identifying risks before they materialize is the most valuable project management skill in any redesign.
- Scope management is continuous: Scope creep accumulates in small additions that each seem reasonable until the budget and timeline are broken.
- Feedback quality matters: Vague feedback generates costly rework; specific, referenced feedback tied to project goals is actionable.
- Projects close at the 90-day review: The manager's job includes post-launch monitoring and the performance review that formally closes the engagement.
The Project Plan as Management Foundation
A project plan for managing redesign is not a calendar the agency maintains. It is the primary management tool both parties use actively throughout the project.
Reading the plan correctly means reading it as a risk document, not just a schedule.
Reading the Project Plan as a Risk Document
A project plan with tight timelines and no buffer between phases is a risk map. Identify which phases have the least buffer and which tasks have the most dependencies.
Those are where problems will emerge first, and those are where the PM's attention belongs before issues arise.
Weekly Plan vs Actuals Review
Every week, compare actual progress against the plan. Tasks slipping by even two days need an immediate response: what's causing the delay, what recovery action is possible, and what adjustment to the timeline is required. Silence and optimism do not close schedule gaps.
Owning the Client-Side Tasks
Content delivery, feedback turnaround, asset provision, and stakeholder sign-off are all client-side tasks. They belong in the project plan with the client's name and a due date attached.
The project manager must track and own these actively. They are not the agency's responsibility to chase.
Managing Each Project Stage
Managing each redesign stage requires a different management focus at each phase. Understanding what the PM's job is in each stage prevents misplaced attention and missed responsibilities.
The nature of the client's role shifts from information provider to decision-maker to reviewer across the project lifecycle.
Managing Discovery: Participation and Decision-Making
In discovery, the project manager ensures all stakeholders are available for interviews, inputs are provided promptly, and the brief is reviewed and approved within the agreed window.
Discovery that drags on delays everything that follows and typically signals that stakeholder alignment was not completed before the project began.
Managing Design Reviews: Consolidated Feedback
During design reviews, the project manager collects feedback from all stakeholders, consolidates it into a single document, and submits it within the agreed feedback window.
Competing feedback routed from multiple sources directly to the designer creates conflicting instructions. All feedback goes through the PM.
Managing Development: Content and Asset Delivery
During development, the project manager tracks content delivery against the content schedule. Content that arrives late directly delays build completion.
This is the most commonly mismanaged timeline variable in any redesign, and it is entirely within the client's control.
Communication Management
A clear communication plan for the project prevents the most common sources of misunderstanding: conflicting instructions, stakeholder surprises, and accountability gaps.
Communication discipline is not about process for its own sake. It is about preventing the friction that costs both time and money.
Enforcing Single Point of Contact
The project manager ensures all client-side communication to the agency routes through them.
Direct access from multiple stakeholders to agency team members creates conflicting instructions and blurs accountability for decisions. One voice from the client side produces cleaner outcomes.
Running Weekly Status Reviews
The project manager reviews the weekly status update from the agency, identifies any risks or slippage, and communicates status to relevant internal stakeholders.
This prevents the "I had no idea we were behind" moments that surface too late for comfortable recovery actions.
Managing Stakeholder Expectations on Timeline
When timeline adjustments are necessary, the project manager communicates the reason, impact, and revised dates to all stakeholders before they learn about the change through indirect channels. Managing the message is part of managing the project.
Managing the Timeline
Keeping the timeline on track requires active intervention, not passive monitoring. Timelines do not self-correct without specific management actions. The most common causes of timeline failure are predictable, and most of them are on the client side.
Identifying and Addressing Slippage Early
When a task is three or more days late, address it immediately. Determine what's blocking it, what resource resolves the block, and what the recovery plan looks like.
Slippage left unaddressed for a week typically requires a full week of timeline extension to absorb.
Managing Content as the Highest-Risk Variable
Content is the project variable most within the client's control and most commonly the cause of delay.
The project manager must treat content deadlines with the same urgency applied to development milestones. Content that arrives on time protects the timeline more than any other single client action.
When to Request a Formal Timeline Revision
If content delay, scope addition, or stakeholder unavailability makes the original launch date unachievable, request a formal timeline revision with a realistic new date.
Maintaining an impossible target and hoping for the best is a management failure, not a project management strategy.
Working With the Agency Team
Working effectively with the agency is a skill that reduces project cost, improves outcomes, and makes the relationship more productive for both sides.
The best client-agency relationships are defined by decisive leadership and clear communication, not by passive approval of whatever the agency produces.
Being Decisive Reduces Project Cost
Every decision requiring multiple rounds of revision or escalation costs project time.
A project manager who arrives at reviews with clear direction and full decision authority saves agency time and the client's own budget. Indecision is expensive, even when it feels cautious.
Trusting the Process Over Personal Preference
The agency's process exists for good reasons. Discovery before design, wireframes before mockups, QA before client preview: each step prevents the problems that arise when it is skipped.
Requesting shortcuts typically produces the exact issues the process was designed to prevent.
Providing Actionable Feedback
"I'm not sure about this" is not feedback. "The headline hierarchy on the service page conflicts with Goal 2 from the brief, which prioritized the enterprise audience" gives the designer a specific problem to solve.
Actionable feedback moves the project forward. Vague reactions generate rework cycles.
Closing the Project
How to close the project properly is a discipline that too many project managers skip in the relief of launch day. Project closure is a structured process, not a passive conclusion.
The formal project close happens at the 90-day review, not on launch day.
Formal Deliverables Sign-Off
Before the project is marked closed, confirm receipt and acceptance of all deliverables: design files, CMS training, redirect documentation, analytics configuration, and any handover reports. Undocumented deliverables become disputes later.
The 90-Day Performance Review as the True Close
The project manager oversees the 90-day review by comparing key metrics against the pre-launch baseline.
If goals have not been met, this review produces a targeted iteration brief. A vague sense of dissatisfaction without specific data is not a useful project output.
Post-Project Retrospective
After the 90-day review, run a brief retrospective. What went well? What caused the most friction? What would you do differently next time?
This learning improves the management of every future project and is worth the 45 minutes it takes.
Conclusion
The client's project management is half the equation in any redesign. Agencies deliver the craft. Clients deliver the decisions, content, and approvals that keep the craft on track. Neither half works without the other.
Review your role in the project plan right now. Identify which tasks belong to you and when they are due.
If those tasks do not have your name and a date attached, they need to be added before the next status call.
LOW/CODE Agency Brings the Project Management, You Bring the Decisions
LOW/CODE Agency provides structured project management on every engagement: a dedicated project manager, weekly status updates, and clearly documented client responsibilities from discovery through post-launch.
LOW/CODE Agency operates as a strategic product team, not a dev shop. We build the process framework, document the decisions, and hold both sides accountable to the plan.
Your role is to show up prepared, review decisively, and deliver content on time.
- Dedicated Project Manager: A single PM owns every engagement, managing timelines, communication, and risk from brief to launch.
- Weekly Status Updates: Structured updates every week covering progress, risks, upcoming milestones, and any client actions required.
- Client Responsibility Documentation: Every client-side task documented in the project plan with names and dates before the project begins.
- Discovery-First Process: Formal discovery phase produces the brief, scope, and project plan before any design work begins.
- Scope Management Protocols: All change requests evaluated against scope before any additional work begins, with change orders for approval.
- Feedback Consolidation: Single consolidated feedback documents from the client at each review stage, preventing conflicting instructions.
- 90-Day Post-Launch Review: Formal performance review comparing metrics against pre-launch baseline with an iteration brief if goals require further work.
Managed redesign with LCA has delivered successful projects for 450+ products, with clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. Start with a scoping call to see how our project management framework applies to your redesign.
Last updated on
July 10, 2026
.










