Worksheet & Workbook · Learning

Your Best People Already Anticipate What Customers Need. They Just Never Wrote It Down.

Anticipation is not a personality trait. It is pattern recognition, built through repetition, feedback, and explicit instruction, and most teams never document what their best employees already know how to do. Start with the free Anticipation Pattern Map to get it out of their heads and onto paper, then use The Named Feedback Playbook to keep it alive week over week.

Download the Free Worksheet See The Named Feedback Playbook

Built from the article Exceeding, Not Just Meeting, Customer Expectations.

The Worksheet

Four Steps, One Touchpoint, One Quarter

Seven pages. No theory to sit through first. Pick one customer-facing touchpoint, interview the people who already read it well, and document what they do without being told to.

What You Download

Pick one touchpoint. Not every customer interaction. One: the front desk, the phone queue, checkout, the first client call.
Run the interview, then document the patterns. Sit down with two to three experienced staff at that touchpoint, one on one, and work through the five-question interview script now built into Step 2, about twenty minutes each. Pull three to four patterns from what they actually did, not what you imagine they do, written as Signal, Likely Need, and Approved Action in a table built for the page.
Set the authority boundary. A plain number for what staff can do without asking first. No number means no real authority, just a suggestion.
Write the feedback language. Named, specific recognition for when someone runs the pattern well, not generic praise that fades after a week.

Get the worksheet on Gumroad →

The biggest failure mode is scripting it. Forced personalization, delivered the same way to every customer, reads as fake and undoes the trust it was meant to build. The worksheet documents judgment, not a script.

Run it for one quarter on one touchpoint before you decide whether it worked.

Paid Workbook · Learning

The Named Feedback Playbook

The pattern map gets your best people's judgment onto a page once. This is the ten-page editable workbook that keeps a manager naming the behavior out loud every week for a full quarter, which is the part that actually keeps a pattern alive.

What's Inside

Why Documentation Alone Fails. The two specific ways a manager kills a pattern map without meaning to: punishing an honest miss, and turning an approved action into a required line.
What Named Feedback Actually Is. The three-part sentence that makes a behavior repeatable, with worked examples from two different touchpoints so you can hear the difference between this and generic praise.
The Weekly Cadence. Six moves, about twenty minutes a week, run on the same touchpoint from your pattern map: pick your observation windows, watch, capture, deliver the feedback same-shift, decide private or public, log it.
Handling a Miss Without Killing the Behavior. A four-part correction that fixes a wrong read without teaching the whole floor to retreat to the safe standard.
Training the Pattern Without Scripting It. How to teach the judgment, the timing, and when to hold back, without freezing the approved action into a line every customer hears identically.
The Quarter Tracker. A thirteen-week manual log, one line per named instance, plus the three questions that carry the ninety-day review of what fired and what didn't.
Where This Leaves You. The four things that make anticipation trainable, and why the weekly cadence is the only one of the four that decays the moment you stop running it.

Get the Playbook on Gumroad →

The worksheet gave you the rows. The Playbook gives you the habit that keeps the rows worth having.

How They Fit Together

One Document, One Habit

The dependency runs one direction. You cannot name a behavior nobody wrote down, and you cannot keep a written behavior alive without naming it out loud every week.

The free worksheet gets the patterns documented, once. You pick one touchpoint, interview the people who already handle it well, and put their judgment into a table a new hire can read.
The paid Playbook is the weekly habit that keeps them alive. A pattern map with nobody naming the behavior out loud goes in a drawer by week three. The Playbook is the twenty-minutes-a-week cadence that stops that from happening.
Start with the worksheet. A filled-in pattern map is what the Playbook's weekly cadence runs against. Buy the Playbook first and you have a habit with nothing documented to reinforce.

Fit

Who This Worksheet Is Built For

Who This Is For

Managers with at least one experienced employee who already reads customers well, even if they cannot explain how they do it yet.
Teams with one high-frequency touchpoint worth documenting first, a front desk, a phone queue, a checkout counter, a first client call.
Anyone who has tried to script empathy, watched it fall flat, and wants a different approach.
Managers willing to run the Playbook's weekly cadence, not just fill in a worksheet once and file it. The pattern map only stays alive if someone keeps naming the behavior out loud.

Skip This If

You want a company-wide culture document. This worksheet documents one touchpoint, not your whole operation.
You want scripts your team can read off a card. Scripting anticipation is the exact failure mode the source article names.
You cannot grant real authority. A boundary nobody has permission to act on is a wish list, not a policy.
You're not willing to spend twenty minutes a week watching one touchpoint for a full quarter. Without that habit, the worksheet is a document, not a system.