The practical takeawayCreate a prioritized problem list before choosing a redesign or a series of improvements.
- Find the friction
- Test a small fix
- Decide the scope
A website can feel old without needing a complete rebuild. It can also look current while making everyday work unnecessarily difficult. The decision to redesign should start with the problems your customers and team are experiencing, together with the condition of the technology underneath.
Choosing too quickly creates avoidable work. A visual refresh may leave broken integrations untouched. A full rebuild may replace useful functionality that only needed attention. A short, evidence-based review gives you a better brief and makes the eventual investment easier to explain.
Use the following process to decide what needs to change, what is worth keeping, and how ongoing improvements might fit your plans.
Define the problems before discussing the solution
Collect examples from the people who use and maintain the site. Ask the sales team which questions visitors still have after reading it. Ask staff which content changes require outside help. Ask customers where they struggled to complete a task. Turn broad concerns into specific observations.
“The site feels dated” is a starting point. “The service descriptions no longer match our offer, and mobile visitors struggle to request a quote” gives you something to investigate. Keep aesthetic concerns on the list, but separate them from functional failures, operational effort, and missing business capabilities.
For each problem, record the affected audience, a useful example, and the consequence. A failed donation form may deserve immediate attention. An inconsistent icon set can usually wait. This creates a sequence of work based on importance rather than the order in which someone noticed each issue.
Inspect the foundation you already have
A technical review should look at the CMS, hosting, dependencies, integrations, backups, permissions, and deployment process. Establish whether the platform is supported and whether someone can safely make and test changes. The answer affects the practical cost of improvement.
Performance also deserves a measured diagnosis. A single speed score cannot describe every visitor's experience. Google explains that lab tests use controlled conditions while field data reflects real visits across different devices and networks. Use both appropriately when assessing problems, as outlined in web.dev's guide to lab and field data.
Look for repeat patterns. One large image is different from a site whose core templates repeatedly load unnecessary scripts. An isolated content issue is different from a CMS that staff cannot use. Ask your technical partner to explain which problems are localized and which are consequences of the underlying architecture.
Choose a scope that matches the evidence
Focused improvement is often a reasonable option when the platform is maintainable and the important problems can be addressed independently. You might rewrite the opening pages, repair forms, improve templates, and connect reporting in a planned sequence. Each change should have a purpose and an owner.
A broader rebuild becomes more compelling when the current structure prevents essential work, the technology is difficult to support, or the organization has substantially changed its offer. In that case, keeping the old foundation can mean repeatedly paying to work around it.
- Improve: the foundation is sound and the highest-priority problems are contained.
- Redesign: the experience needs a coherent new structure, while parts of the technology remain useful.
- Rebuild: the platform and architecture need substantial replacement to support the required experience.
These are planning categories, not rigid definitions. A project can combine them. Be precise about which parts will change so that “redesign” does not become shorthand for assumptions that nobody has discussed.
Protect what already works
Before replacing pages, inventory the content, search landing pages, integrations, forms, tracking, and downloads that people currently rely on. Note what must continue to work on launch day. Include quieter operational features, such as notification recipients and where inquiry data is stored.
If URLs change, plan the move deliberately. Google recommends mapping old URLs to their relevant new destinations, updating internal references, and using appropriate permanent redirects. The details are in its site migration guidance. Treat this as part of the project scope rather than a cleanup task after launch.
Write acceptance checks for the important journeys. For an illustrative nonprofit, those might include making a test donation, finding program information, and submitting a volunteer inquiry. For a fleet business, they might include requesting a quote and confirming that the inquiry arrives in the correct system with its source information.
Plan for the month after launch
Decide who will manage updates, monitor problems, and prioritize improvements once the initial work is complete. A new site still needs attention. Content changes, campaign pages, security updates, and integration issues continue after the launch announcement.
Ask for a plan that distinguishes immediate fixes, the main redesign or rebuild scope, and the ongoing work. This helps your team understand the investment and keeps urgent repairs from waiting for a larger project.
Bring your technical partner a list of the five problems that most affect customers or staff, along with examples. TripleSkinny can review the foundation, explain the options, and recommend a manageable sequence of work. The first useful deliverable is a clear decision about what to improve and why.



