Don't copy the message. Understand the derivation.
These six examples are the completed V1 audit cases. Each one starts with a real communication situation, identifies what must happen, diagnoses the Primary Friction, loads a Base Stack, and shows why the final message uses ENTRY → FRAME → LEVERAGE → CLOSE.
An important handoff update is getting lost in the group.
Everyday communication · read the updateThe colleague knows what the handoff notes are, knows where to find them, and reading one update is not inherently difficult. The problem is that the message looks less important than the other things competing for attention.
No substitution. The ATTENTION default already contains mechanisms that fit the diagnosed Priority friction.
I updated tomorrow's handoff notes. Please take a look when you get a chance.
One item in tomorrow's handoff note changed after today's call. It's the only step that now has a different owner. It affects the handoff you're leading at 9:00. The rest is unchanged — read the highlighted line and you're caught up.
One changed item stands out from a generic document update.
The changed owner creates a small, legitimate information gap worth resolving.
The change is connected to the handoff the recipient personally leads at 9:00.
Only one highlighted line remains between the recipient and being fully caught up.
You corrected an error. Now the correction itself must be trusted.
Everyday communication · believe the corrected fileThe team understands the claim that the spreadsheet was corrected. The blocker is belief: after one version was wrong, why should the revised version now be considered reliable?
No substitution. The TRUST default already addresses Doubt directly.
I found an error in the spreadsheet and fixed it. The new version is correct. Please use this one.
I found an error in the spreadsheet I sent this morning. Rows 42–68 were still using last month's rate, which affected the final total. I've corrected that formula and checked the revised totals against the source file; the validation tab now matches line by line. I've left the validation tab visible so you can verify any number yourself before using the file.
Admit the relevant error instead of minimizing or hiding it.
Define exactly where the error occurred and what it affected.
Support the correction with a concrete validation against the source file.
Give the recipient agency to verify the result rather than demanding blind trust.
The information is present. The rule is still too easy to misread.
Everyday communication · understand the entry ruleThe actual procedure is easy. The problem is that the threshold, the two conditions and the corresponding entrances are buried inside one long explanation.
No substitution. The default already makes the rule easier to process, interpret, differentiate and verify.
Tomorrow the main entrance will only be available during the initial arrival period because security needs to close it before the event starts, so if you arrive later you'll need to use the other entrance by the parking area. Please keep that in mind.
Tomorrow's entry rule is simple: arrival time decides which door you use. Before 8:30 = Main Entrance. After 8:30 = Side Entrance by the parking area. Quick check: if you arrive at 8:45, which entrance do you use?
Reduce the rule to one governing variable: arrival time.
Define the issue as one threshold decision rather than several new procedures.
Put the two conditions side by side so the difference becomes obvious.
A small comprehension check makes understanding observable instead of asking “Got it?”
The habit is understandable. It still does not feel worth doing.
Everyday communication · want the three-bullet handoff habitThe colleague understands the idea and can perform it. The missing condition is perceived value: leaving a handoff note does not yet feel important enough to compete with simply ending the workday.
No situational substitution. This audit is the case that led v1.7 to freeze Contrast, rather than Anticipated Regret, as the general DESIRE LEVERAGE default.
You should start leaving a short handoff note at the end of the day. It would make things easier for everyone.
You mentioned that the first 20 minutes of some mornings disappear just figuring out where yesterday left off. Imagine starting the morning already knowing what was finished, what is still open, and what needs attention first. Right now the morning starts with reconstruction. With a handoff, it starts with the next decision. It only takes three bullets: done, open, next.
Connect the habit to a problem the person already experiences.
Make the improved morning concrete enough to imagine and value.
Make current-state reconstruction and future-state forward movement easy to compare.
Reduce the habit to three simple bullets: done, open, next.
The team understands the proposed format. One person sees only more work.
Everyday communication · agree to test a handoff formatThe colleague understands the format. The blocker is the expectation that adopting it will create another administrative process and more recurring work.
One substitution. Consensus does not solve the diagnosed Effort. Ease does.
I think we should use a standard format for every handoff: owner, next step, and due date. It will help us stay organized. Can we start using it?
We're losing time after handoffs because the next owner and next step are often buried in the conversation. This isn't about adding another reporting process. It's just a three-part closing line: Owner → Next Step → Due Date. It takes one line at the end of the message — no form, spreadsheet, or extra update. Can we test it on this week's handoffs and see whether it removes the back-and-forth?
Give the proposed change a concrete rationale before asking for agreement.
Reframe the idea from “new reporting process” to one structured closing line.
Directly address the Effort friction by showing there is no new form, spreadsheet or update.
Ask for a bounded one-week test rather than permanent policy adoption.
The person can reply. The message makes them generate the answer from scratch.
Professional communication · schedule a 15-minute reviewThe request is understandable and not meaningfully risky. The friction is open-ended work: the recipient must check a calendar, generate possible times, and compose the answer.
No situational substitution. This audit is the case that led v1.7 to freeze Choice Reduction, rather than Risk Reversal, as the general ACTION LEVERAGE default.
Hi Mark, Just checking if you had a chance to see my last message. Let me know when you're available.
I'm scheduling next week's review today. I just need to lock one 15-minute slot before I send the calendar. Would Tuesday at 3:00 or Thursday at 10:00 work better? Just reply Tuesday or Thursday.
Give the follow-up a legitimate contextual reason to matter now.
Explain exactly why the reply is needed and what it enables.
Remove the need to generate meeting times from an open calendar.
Reduce execution to a two-word choice instead of an open-ended scheduling task.
The Trigger can change. The position job stays stable.
Across six different Desired Responses, the same four structural questions remain.
- ENTRY Why should this person engage with this message in this context?
- FRAME How should the situation, choice or meaning be understood?
- LEVERAGE What legitimate mechanism changes the decision balance?
- CLOSE What clear next movement converts readiness into action?
A canonical example is evidence for the method. It is not a script library.
Do not copy wording because it “sounds persuasive.” Start with the real Situation, Observable Outcome, Desired Response and Primary Friction. The Base Stack is a default. A substitution is justified only when the diagnosed Friction shows that another canonical Trigger performs that position job better.
The method structures legitimate information. It does not authorize fake scarcity, fabricated proof, false authority, deception, coercion, invented urgency or invented social evidence.
Examples show the reasoning. The Map starts with your situation.
Use the free Interactive Map to start with a real communication problem. See a useful Stack before the email gate, then unlock the complete Map PDF and resources.
No payment required. The useful Stack reveal comes before First Name + Email.
Use the Interactive MapDon't memorize the example. Learn how to derive the message.
Start with the free Interactive Map, or read the Trigger Stack Method to understand the complete architecture.