Design the Path, Not Just the Message

Product teams are very good at improving things they can see.

They can shorten a form, change a button, rewrite a headline, add a tooltip, move a recommendation, or reduce the number of screens in a flow.

But when people fail to adopt a feature, complete onboarding, or follow a recommendation, the visible interface may not be where the failure occurred.

The receiver may have stopped one cognitive step earlier. They may not recognize that the feature applies to their task. They may predict the wrong outcome. They may distrust the recommendation or understand the words without seeing a bridge to the next action.

This leads to a practical design principle:

Do not design only the final message or screen. Design the sequence of receiver states required to use it.

Violet calls this cognitive path smoothing.

Every visible journey contains an invisible journey

Consider a patient who encounters a recommendation to book a dermatology appointment.

The visible journey appears simple:

1. Read the recommendation.
2. Select a clinic.
3. Choose a time.
4. Confirm the booking.

The receiver’s journey is more demanding:

1. Notice the recommendation.
2. Recognize that it applies personally.
3. Understand why the appointment is recommended.
4. Decide whether the recommendation is credible.
5. Estimate the likely cost, effort, and benefit.
6. Determine whether action is needed now.
7. Understand what will happen after clicking.
8. Begin the booking process.

If the receiver stalls at step three, optimizing the calendar at step eight will not solve the problem.

The organization sees “no booking,” but the same outcome can be produced by very different mechanisms. That is why engagement is often a symptom rather than a diagnosis.

Find the first broken transition

A useful journey can be represented as a sequence:

Current state → useful next state → useful next state → appropriate action

At each point, the receiver must select something for attention, connect it to an expectation or mental model, and cross a local transition.

The design problem is rarely that every transition is equally difficult. More often, one transition is unsupported:

• The receiver sees the feature but cannot map it to the current goal.
• They understand the benefit but cannot predict what clicking will do.
• They trust the product but not the data behind a recommendation.
• They understand the recommendation but cannot determine which option is appropriate.
• They reach the form but encounter a question requiring information they do not have.

One severe jump can break an otherwise usable path.

This gives product teams a better question than “How do we improve conversion?”

What is the first useful state the receiver fails to reach?

Strain changes with the receiver

The effort required to move from one state to the next depends on who is making the transition.

An experienced investor may immediately understand the consequence of an options-expiry notice. A first-time investor may recognize every word while missing the required action.

A clinician may connect a laboratory value to the appropriate follow-up. A patient may need a plain-language bridge before the value becomes meaningful.

An engineer may interpret an infrastructure warning as a familiar failure pattern. An executive may need the operational consequence before the warning becomes actionable.

Product Strain cannot therefore be measured only by counting steps, words, or clicks.

A short journey can contain a large unsupported inference. A longer journey can feel easier when each step prepares the receiver for the next. Removing screens helps when those screens are unnecessary. It harms when the removed screen supplied the bridge that made the rest of the journey understandable.

Apply the Violet 5S™ method at each transition

The method becomes particularly useful when it is applied locally rather than only to an experience as a whole.

Lever	Transition-level question
Spotlite	What should the receiver notice now, and what might compete with it?
Substance	What evidence enables the next useful state?
Source	What makes this recommendation or instruction credible here?
Strain	What knowledge, memory, or effort does the next transition require?
Stake	Why continue instead of postponing or stopping?

Return to the dermatology example.

If the transition is recommendation seen → personal relevance understood, the design may need:

• Spotlite: a visible connection to the receiver’s reported concern
• Substance: a concise explanation of why follow-up is appropriate
• Source: the clinician, guideline, or assessment behind the recommendation
• Strain: plain language and one explicit inference
• Stake: the practical value of timely evaluation without artificial alarm

If the transition is intent to book → completed booking, the intervention may be entirely different:

• Show available appointment types.
• Explain cost or coverage.
• Make location and timing constraints visible.
• Preserve progress.
• Provide an alternative route when the receiver is unsure.

The 5S do not prescribe one universal message. They organize the diagnosis.

Run a path audit before a broad redesign

Product and service teams can use the following sequence to make the problem testable.

1. Define the legitimate outcome

Specify what the receiver should be able to understand or do.

Avoid defining success as agreement at any cost. A receiver who understands the offer and declines it may represent successful communication and genuine product rejection.

2. Map plausible starting states

New users, experienced users, skeptical users, and users arriving from different channels may begin with different knowledge, trust, and expectations.

Treat these states as competing hypotheses, not permanent personality labels.

3. Map the required transitions

Write the invisible journey between exposure and action. For each transition, identify:

• What the receiver must notice
• What they must infer or retrieve
• What expectation guides the next step
• What could create conflict or ambiguity
• What would count as a successful local transition

Include what happened immediately before the journey. An earlier cue, error, email, or support interaction can change how the next screen is interpreted.

4. Locate the bottleneck

Use behavioral and qualitative evidence:

• Where do people pause, regress, or abandon?
• What questions do they ask?
• Which incorrect expectations recur?
• What do support conversations reveal?
• Does confidence match actual understanding?
• Do people reach the next screen while remaining unable to act?

Time alone is not enough. A careful expert can be slower than a guessing novice. Pair timing with accuracy, behavior, and explanation.

5. Generate competing explanations

Do not assume every failure is a copy problem. Plausible explanations may include:

• Attention failure
• Relevance failure
• Missing knowledge
• Low trust
• Unresolved ambiguity
• Product friction
• An external constraint
• Informed rejection

The intervention should help distinguish among these explanations.

6. Add the smallest useful bridge

A bridge might:

• Reorder existing information.
• Activate the relevant concept before introducing terminology.
• Add a worked example.
• Make an implicit inference explicit.
• Show what will happen next.
• Remove a competing interpretation.
• Break one unfamiliar operation into familiar steps.
• Introduce surprise and immediately supply a route to resolve it.

The objective is not to eliminate all effort. Some decisions deserve careful thought. Remove unnecessary Strain while preserving the reasoning needed for accurate understanding.

7. Measure the predicted transition

If the intervention is supposed to increase trust, measure more than clicks.

If it is supposed to improve understanding, test whether people can explain the choice or select an appropriate next step.

If it is supposed to reduce uncertainty, examine calibrated confidence, help-seeking, and backtracking.

Downstream conversion matters, but it should be connected to the mechanism the team intended to change.

Make the experiment bottleneck-specific

Suppose research suggests that new users abandon an investment feature because they do not understand the consequence of the first decision.

The team could test:

• Variant A: the existing journey
• Variant B: a short explanation at the predicted bottleneck
• Variant C: the same amount of additional information placed elsewhere

If Variant B improves understanding and appropriate continuation more than Variant C, the result supports the transition diagnosis.

If both perform equally, the benefit may come from general reassurance or added attention rather than the proposed bridge. If neither helps, the assumed bottleneck may be wrong.

This is more informative than comparing two large redesigns with dozens of uncontrolled differences.

Path smoothing is not frictionless steering

The easiest path is not always the best path.

A financial disclosure should not become so fluent that a real risk disappears. A medical recommendation should not use fear to prevent deliberation. An onboarding flow should not hide meaningful alternatives because they reduce completion.

Responsible path smoothing should:

• Preserve important evidence and uncertainty
• Make alternatives understandable
• Support informed refusal
• Avoid exploiting inferred vulnerabilities
• Distinguish communication failure from genuine disagreement
• Retain productive friction when careful consideration is necessary

The goal is not to move every receiver to the designer’s preferred destination. It is to make the path to accurate understanding navigable.

Change the product operating question

Traditional optimization asks:

Which version produces more action?

Violet adds:

For which receivers, through which transition, and with what evidence that the action was informed?

That question produces better product learning. It tells a team not only whether a change worked, but why, where, and for whom it worked.

When teams design the path—not only the final screen—they can stop treating every abandoned journey as the same problem. They can find the first unsupported jump, build the appropriate bridge, and test the transition that actually matters.

For the next layer, read Building Receiver-Aware AI to see how bounded AI systems can apply this reasoning without pretending to know the receiver with certainty.

Examine a journey with Violet

Have a screen, onboarding flow, form, or service journey that is not producing the expected next step?

Send one message for a free attention audit, or request a consultation when the problem spans multiple teams, channels, or operational systems.