Learn before you redesign.

Collect observations before solutions

Early conversations often contain proposed features alongside real experiences: a customer could not find proof, an operator rebuilt the same record, or a decision-maker lacked confidence in the available measure. Preserve the observation before translating it into a requirement.

Observations can come from interviews, analytics, support patterns, workflow review, accessibility testing, competitive context, and direct use. No single source needs to carry more certainty than it deserves.

Evidence narrows the space responsibly; it does not remove the need for judgment.

Separate facts from assumptions

A useful synthesis shows what was directly observed, how the team interprets it, and what remains an assumption. Combining those layers too early makes a plausible story look like a verified conclusion.

The distinction is especially important when records are incomplete, participants are few, or the operating environment has recently changed. Visible limitations help stakeholders decide what to act on and what to test next.

• Observation: what the source actually shows
• Interpretation: what the pattern may mean
• Assumption: what still needs validation
• Constraint: what shapes the available response

Translate evidence into interface decisions

Research becomes useful when it changes priority. A repeated trust question may move proof closer to a claim. An operational handoff may require a visible state and owner. A mobile observation may reduce the amount of information requested at the first step.

Each important interface decision should be traceable to the evidence or constraint that shaped it. That does not make the design mechanically determined; it makes the reasoning reviewable.

Preserve traceability after launch

A design rationale should not disappear when implementation begins. Requirements, components, analytics events, and acceptance criteria can retain the original question so the team knows what a later change is meant to improve.

Post-launch evidence can then challenge the original assumption without erasing history. Teams learn faster when they can see what they believed, what they changed, and what happened next.

• Link decisions to their source context
• Record unresolved questions
• Define what evidence would change the direction
• Review outcomes against the original problem

A worked scenario

Consider a team preparing a redesign around internal opinions. The useful outcome is to learn which problems the interface must solve. 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 favored visual concept determining the problem statement 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

Use these checkpoints to learn which problems the interface must solve; 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 priority design decisions grounded in evidence divided by priority decisions. The numerator is priority design decisions grounded in evidence; the denominator is priority decisions. 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 learn which problems the interface must solve, but it does not explain every cause of success or failure. Inspect the underlying cases alongside the summary. If the count changes after separate observed barriers from preferences, 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 collect task evidence from customers and staff. 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: learn which problems the interface must solve.

For a team preparing a redesign around internal opinions, 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 separate observed barriers from preferences. Compare expected behavior with observed behavior in the same test, rather than comparing two descriptions written at different times. Pay particular attention to a favored visual concept determining the problem statement. 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 the proposed design cannot address the observed task barrier, 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 turn findings into prioritized design acceptance checks. 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: learn which problems the interface must solve.

Give the operator a short record of what healthy work looks like and what requires intervention. Include the warning case of a favored visual concept determining the problem statement, 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.