Two people can receive the same message, understand every word, and still reach different conclusions.
An executive sees a warning in a dashboard and interprets it as operational risk. An engineer sees the same warning and treats it as a monitoring defect. A customer reads a recommendation and sees an unnecessary upsell. Another sees a useful shortcut.
The usual explanation is that one person misunderstood. Sometimes that is true. But it misses a more important possibility:
The message did not enter an empty mind. It entered a receiver who was already attending, predicting, remembering, and deciding.
That receiver brought a role, an active job, prior experience, expectations, trust, knowledge, emotional state, and limited attention. Those conditions influenced what became important before the message had a chance to “speak for itself.”
This is the communication problem Violet is built to examine.
Why the sender-only model fails
Most communication is designed from the sender’s side.
The sender asks:
- Is the information correct?
- Is the wording clear?
- Is the design attractive?
- Is the call to action visible?
- Have we supplied enough evidence?
Those are necessary questions, but they are incomplete. They treat meaning as though it can be packaged by the sender and transferred intact to the receiver.
In practice, the receiver helps construct the meaning.
A hiring manager does not read a résumé simply to learn a candidate’s history. They read it while deciding whether the candidate is worth advancing, often under time pressure and in comparison with other applicants.
A patient does not read an appointment reminder as neutral scheduling information. They may read it while worried about cost, diagnosis, inconvenience, or what the visit could reveal.
A product user does not encounter a new feature as an isolated interface element. They approach it with an existing task, a mental model of the product, and an expectation about what will happen next.
The same information can therefore produce different attention, interpretation, and action because it enters different receiver states.
When the receiver is a market or institution
Receiver-aware analysis is not limited to individual readers. A consequential public announcement can be processed simultaneously by market participants, households, voters, regulators, and political institutions—each using different evidence and protecting a different stake.
The United Kingdom’s September 2022 Growth Plan is a useful example. The government intended to signal growth, but market participants evaluated fiscal credibility, households attended to financial security, the public judged fairness and competence, and governing MPs assessed political survival. The resulting reaction cannot be reduced to wording: policy substance, evidence, sequence, source credibility, and market conditions all mattered. Read the living case study, One Growth Plan, Four Receivers.
Ask what became important to this receiver
When a message fails, teams often add more content: another explanation, benefit, chart, notification, or stronger call to action.
That can help. It can also make the failure worse.
Attention is limited. Increasing the prominence of one element can reduce the attention available to another. Adding information can increase strain, activate an unintended interpretation, or bury the evidence that actually matters.
Violet begins with a different set of questions:
- What is the receiver trying to get done?
- What are they likely to notice first?
- What will that first cue cause them to expect?
- Which prior belief, memory, or role may become relevant?
- What will they trust, question, or ignore?
- Where could the communication path become difficult?
- What legitimate next transition should the experience support?
This changes the unit of analysis. We are no longer evaluating only the message. We are evaluating the relationship among the receiver, the message, and the situation.
Use the Violet 5S™ method as connected design levers
Violet organizes this diagnosis around five connected levers.
| Lever | Practical question |
|---|---|
| Spotlite | What is likely to receive attention first—and is it the right thing? |
| Substance | What evidence helps the receiver form an accurate interpretation? |
| Source | Why should the receiver trust the message, evidence, or recommendation here? |
| Strain | How difficult is it for this receiver to process the information and reach the next useful state? |
| Stake | Why is continued attention or action worthwhile to the receiver? |
These are not five independent boxes to tick.
A powerful source can increase trust, but it can also trigger resistance in someone who distrusts that institution. A vivid Spotlite can attract attention while pulling attention away from qualifying evidence. A strong Stake can motivate action, but it can become coercive when urgency is used to suppress meaningful choice.
The useful configuration depends on the receiver, context, and target transition. The white paper explains the framework and its limits in more depth.
Separate information from a usable path
Imagine a digital health service encouraging a patient to book a follow-up appointment.
The message may contain everything the patient technically needs:
- The clinician’s recommendation
- The reason for follow-up
- A scheduling link
- Available dates
- Contact information
Yet the patient still does not book.
It is tempting to label the patient “unengaged” and send another reminder. But the same observed result can come from several different failures:
- The recommendation was not noticed.
- It was noticed but did not appear personally relevant.
- The patient understood it but did not trust the source.
- The likely cost or inconvenience remained unclear.
- The patient wanted to book but could not identify the correct next step.
- The patient understood everything and made an informed decision not to proceed.
These are not the same problem, and they should not receive the same intervention.
A more prominent cue might address the first. A concise explanation may address the second. Transparent cost information may address the fourth. A simpler booking flow may address the fifth. The sixth may not be a communication failure at all.
Published appointment and vaccine-reminder studies illustrate why an outcome can change without proving which psychological mechanism changed. See the pharmacy vaccine-reminder case for Violet’s interpretation and the underlying source.
“Clear” is receiver-relative
A sentence can be grammatically simple and still require a difficult cognitive jump.
An expert may connect a term to the correct concept, implication, and action immediately. A novice may need an intermediate example. A person who has encountered the issue before may recognize the pattern automatically. Someone seeing it for the first time may not know which knowledge to retrieve.
Strain is therefore not merely a property of sentence length or vocabulary. It is an interaction among:
- The structure of the information
- The demands of the task
- The receiver’s available knowledge and attention
- The distance between the current state and the next required state
This is why simplifying every sentence does not guarantee understanding. The words can be easy while the transitions between ideas remain unsupported.
The deeper product guide, Design the Path, Not Just the Message, shows how to find that unsupported jump across a product or service journey.
Diagnose before you rewrite
Before changing an important message, interface, or communication campaign, answer five diagnostic questions.
1. What observable transition should occur?
Avoid “make the receiver engage.” Name something measurable and legitimate: identify the relevant risk, understand the available options, complete a required step, or make an informed choice.
2. What state is the receiver likely to begin in?
Consider the active task, prior knowledge, trust, expectations, previous exposure, and practical constraints. Treat these as hypotheses, not facts about the person.
3. What will they attend to and predict first?
The opening cue shapes what follows. It can activate a useful way of reading the situation or send attention toward an unintended interpretation.
4. Where is the first likely breakdown?
Separate attention, understanding, trust, capability, product friction, external constraints, and genuine rejection.
5. What is the smallest responsible intervention?
Reorder existing information, add evidence, clarify the source, reduce an unsupported jump, or make the next step explicit. Then test whether the predicted bottleneck actually changes.
This produces more useful experiments. Instead of asking whether “the new message performed better,” a team can ask whether a specific change improved the transition it was designed to support.
Good communication preserves choice
Communication is not only what the sender says. It also includes:
- The state in which the receiver encounters it
- The order in which cues appear
- The expectations those cues activate
- The effort required to connect one idea to the next
- The reasons the receiver has to continue
- The alternatives and freedom the receiver retains
This does not mean every experience should be personalized or optimized for compliance. Responsible communication preserves accuracy, meaningful alternatives, and informed refusal.
It means organizations should stop treating sent information as proof of received understanding.
The receiver is not the final stop in a delivery pipeline. The receiver is part of the system that produces the outcome.
Apply the idea to your material
Violet analyzes communication as a receiver-conditioned sequence:
Receiver situation + information path → attention → interpretation → possible next transition
Sometimes the answer is stronger evidence. Sometimes it is a different sequence, less information, or a clearer next step. Sometimes the communication is working and the product, policy, or offer is what the receiver is rejecting.
Knowing the difference is the beginning of better design.
Send one message for a free attention audit, or discuss a larger transition when the problem spans a product, service, or organizational journey.