VANKPA
The decision
A redesign baseline should capture the business outcomes and journey conditions the project aims to improve. Record current definitions and measurement gaps before changing the site. Otherwise the team may be unable to judge whether the release addressed the original problem.
In practice
A service business may care about inquiry quality and staff handling time more than total page views. Review current inquiries and the contact journey. Note seasonality, campaigns, and operational changes that could affect later comparisons.
- Choose a small set of measures, verify collection, and preserve the relevant period's context.
- Document technical and content issues alongside the numbers.
- Agree what a useful post-launch review can reasonably conclude without promising causal proof from a simple before-and-after comparison.
When to take the next step
Capture the baseline before tracking or customer journeys change. Choose the measures tied to the redesign's purpose and preserve the operating context behind them.
Questions clients ask
How long should the baseline period be?
Choose a period that reflects the business's volume and variation, and state its limitations.
Can a redesign be judged by traffic alone?
No. Include the customer actions and operational outcomes that motivated the project.
A worked scenario
Consider a business replacing a website before a busy season. The useful outcome is to preserve evidence for a fair comparison. 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 launch comparison attributing all change to the redesign 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 | Record the current journey, inquiry quality, and collection rules. | The approved scope, relevant source records, and unresolved questions. |
| Verify | Note seasonal changes and other business initiatives. | The test case, expected result, observed result, and correction needed. |
| Operate | Retain comparable definitions after launch. | The responsible owner, completion record, and next review trigger. |
Use these checkpoints to preserve evidence for a fair comparison; 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 postlaunch measures comparable to their baselines divided by planned measures. The numerator is postlaunch measures comparable to their baselines; the denominator is planned measures. 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 preserve evidence for a fair comparison, but it does not explain every cause of success or failure. Inspect the underlying cases alongside the summary. If the count changes after note seasonal changes and other business initiatives, 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.
Step 1: Prepare the evidence
The first practical move is to record the current journey, inquiry quality, and collection rules. Start with the smallest set of examples that covers the important variation in this scenario. Include an ordinary case, a case with missing information, and a case that requires intervention. Describe the intended result before reviewing the current behavior. This keeps the preparation focused on the outcome: preserve evidence for a fair comparison.
For a business replacing a website before a busy season, the person responsible for the source information should take part in preparation. Ask that person to confirm which information is authoritative and which points still need a decision. Record those uncertainties beside the scope instead of hiding them in a general assumption. Preparation is complete when another team member can follow the agreed example and explain what evidence would allow the work to continue.
Step 2: Test the difficult case
The next move is to note seasonal changes and other business initiatives. Compare expected behavior with observed behavior in the same test, rather than comparing two descriptions written at different times. Pay particular attention to a launch comparison attributing all change to the redesign. A demonstration that works only for its author does not establish that the intended user can complete the task. Let the reviewer attempt the work with the instructions they would normally receive.
For this check, retain the input, the relevant condition, and the final disposition. A screenshot can illustrate the state, but the record also needs to explain what the team expected and why the result matters. If tracking definitions change at the same time as the website, hold the decision open and send it to someone with the authority to resolve it. Retest the changed case after correction; an agreement to fix something is different from evidence that the correction works.
Step 3: Assign operating ownership
The operating move is to retain comparable definitions after launch. A successful initial test should lead to a repeatable responsibility, not a permanent dependency on the person who built the solution. Name the person who reviews the result, the person who can change the rule, and the person who responds when the task fails. In this scenario, each responsibility contributes to the same outcome: preserve evidence for a fair comparison.
Give the operator a short record of what healthy work looks like and what requires intervention. Include the warning case of a launch comparison attributing all change to the redesign, together with the relevant records and support route. The procedure should be usable during normal work, not only during a formal review meeting. Check that an authorized backup person can follow it before treating the approach as ready for broader use.
Handle exceptions deliberately
The specific pause condition is that tracking definitions change at the same time as the website. Make the pause visible to the person doing the work and to the person responsible for resolving it. Preserve the relevant context so investigation does not depend on memory. A stopped case is still part of the process; it needs a status, an owner, and a safe route back into ordinary work after the uncertainty is resolved.
Before restarting, establish whether a launch comparison attributing all change to the redesign affected only this case or indicates a wider rule problem. Correcting one record may be appropriate for an isolated exception. A recurring pattern may require changing the definition, interface, routing, or review procedure. Test the restart against the original case and one related variation. Record the reason for the change so later reviewers can distinguish a deliberate decision from an unexplained workaround.