VANKPA
The useful takeaway
Base the investment on your own funnel and delivery economics, with a range of outcomes and a clear measurement plan.
A website redesign becomes easier to evaluate when the proposed change connects to a business constraint. An outdated visual identity may matter, but the investment decision also needs to explain what the current experience prevents: understanding the offer, judging fit, requesting an estimate, or completing a purchase.
Start by separating necessary repair from a growth hypothesis. Fixing an unusable mobile form restores a basic capability. Rewriting a service page to attract a different customer segment is an experiment. Both can belong in a redesign, but they need different evidence and different expectations.
Use research to frame the question
McKinsey's 2018 design study reported that top-quartile companies achieved revenue growth 32 percentage points above industry counterparts over five years. That finding concerned 300 publicly listed companies and a broad set of design practices. It is a correlation, not a predicted uplift for a small-business website. Its useful implication is that design deserves business measurement. McKinsey research
For your business case, replace a borrowed percentage with a documented baseline. Collect relevant visits, inquiries, qualified opportunities, wins, and contribution per completed engagement. Note missing tracking, seasonal demand, changes in advertising, and the time between inquiry and sale. The accuracy of the assumptions matters more than the polish of the spreadsheet.
Measure qualified demand
An increase in inquiries can create extra work without creating extra value. Define qualification using criteria the team can consistently apply: service fit, geography, timing, budget context, or another relevant requirement. Do not silently change that definition after launch to make the results look stronger.
Then build a range. Show what happens if traffic stays flat, if inquiry completion improves, and if qualification or close rates decline. Keep existing and incremental demand separate. Include delivery capacity: a team unable to accept more work may benefit more from better-fit leads or clearer scheduling than from additional volume.
Published research · 2018
Design has a business context
- Revenue growth versus industry counterparts
- +32 pp
- Public companies studied
- 300
- Observation period
- 5 years
Include the operating costs of the new site
The launch price is only one input. Content preparation, staff review time, hosting, paid integrations, ongoing accessibility work, maintenance, and measurement all belong in the decision. If the site adds booking, payments, or a portal, identify who will resolve failed transactions and keep information current.
Avoid counting the same benefit twice. Time saved handling incomplete inquiries may already be reflected in improved contribution per engagement. Document which benefits are cash effects, which are released capacity, and which are qualitative improvements. A clearer brand experience can be valuable without assigning it an invented dollar amount.
Decide how the result will be evaluated
Google Research's work on user-centered measurement connects product goals with appropriate metrics. Apply that principle by selecting a primary business outcome and a small set of experience checks before release. Google Research research Compare similar periods and traffic sources, and keep a change log so other marketing activity is visible.
Our recommended approval brief includes the constraint, the smallest useful scope, a scenario range, the full cost assumptions, and a review date. It should also explain what would justify stopping or changing direction. This is especially useful when choosing between a focused improvement and a complete redesign.
- Reconcile inquiries with the team's actual sales records.
- Review contribution and capacity assumptions with the business owner.
- Name the person responsible for postlaunch measurement.
- Agree on the evidence needed for the next investment decision.
Can a redesign guarantee a return?
No. Demand, pricing, sales follow-up, market conditions, and delivery quality all influence the outcome. A responsible redesign proposal makes those dependencies explicit and gives the team a workable way to learn whether the investment is helping.
Evidence behind the guidance
Sources & context
Published research informs this article. VanKpa's frameworks and recommendations are practical applications; illustrative data is labeled where used.
- McKinsey — The business value of design ↗2018-10-25
Observational study of 300 publicly listed companies over five years; correlation, not a causal estimate for small-business websites.
- Google Research — User-centered metrics for web applications ↗2010
Introduces HEART and mapping product goals to metrics.
What could this change?
Bring the question, the current workflow, and the result you want to improve. We can help define a useful next step.
A worked scenario
Consider an owner deciding whether to replace a functioning website. The useful outcome is to justify investment using the actual business constraint. This is a planning example, not a reported client result. The team needs a decision that can be checked against real work, rather than a feature list that looks complete during a presentation. The starting question is whether the proposed approach changes that particular task in a way the people doing it can recognize.
In this situation, a modern appearance being treated as proof of financial value is the failure to guard against. Ask the responsible person to demonstrate an ordinary case and one difficult case using current records or safe test data. Record what they expect to happen, what actually happens, and where they need another person to intervene. Those observations establish the scope for this example; they do not justify an assumed improvement percentage or a guaranteed business result.
Decision checkpoints
| Checkpoint | Practical action | Evidence to retain |
|---|---|---|
| Prepare | Describe what the current site prevents or makes expensive. | The approved scope, relevant source records, and unresolved questions. |
| Verify | Compare improvement, partial rebuild, and replacement options. | The test case, expected result, observed result, and correction needed. |
| Operate | State assumptions and the evidence needed to confirm them. | The responsible owner, completion record, and next review trigger. |
Use these checkpoints to justify investment using the actual business constraint; they are a sequence of decisions, not a promise of a particular schedule. A completed document or screen is not enough if the underlying action still fails. Keep unresolved items visible and describe which ones prevent progression. The evidence can be a small test record, an approved mapping, or a reviewed example. It should be understandable to someone who was not present when the work happened.
Measure the useful result
A useful check for this topic is business-case assumptions backed by current evidence divided by material assumptions. The numerator is business-case assumptions backed by current evidence; the denominator is material assumptions. Define the sampling window, exclusions, and source of each count before interpreting the result. If only selected examples can be reviewed, describe them as a sample. Do not present a small reviewed group as a complete picture of the business, and do not assign a target simply because a round number looks persuasive.
The measure helps reveal whether the team can justify investment using the actual business constraint, but it does not explain every cause of success or failure. Inspect the underlying cases alongside the summary. If the count changes after compare improvement, partial rebuild, and replacement options, check whether the operating result changed or the counting method changed. Retain enough context to explain the difference. When records are incomplete, state the limitation and use a direct task review instead of manufacturing a precise-looking estimate.