The job
A sales process gets handed from the founder to a new sales manager. The founder ran it intuitively. The new manager needs steps. The founder hands off verbally. The manager nods. For two weeks, deals stall because the manager wasn’t running the same process. The founder has to intervene. Frustration.
The dish reads the handoff document (the founder’s notes on the sales process). It knows the incoming recipient is a manager seeing the workflow for the first time. It translates: these are the implicit steps you need to know. Here’s why we do it this way. Here’s what matters. Here are the decision points. The new manager reads it. Day one they run the process the same way the founder did.
Plated well, this looks like: handoffs don’t break. New people step in and run the workflow without friction. The process is the same but the written version matches where the recipient sits. Implicit knowledge becomes explicit. The founder doesn’t have to reteach.
The recipe
All seven ingredients still apply. The leverage is Context (Ingredient #2). The station needs to know the recipient’s role, experience level, and what they need to understand to execute. A new manager handoff is different from a peer handoff is different from a vendor handoff.
Training (Ingredient #1) is the second lever. Your house standard is how handoffs are written. You always include context. You always name the dependencies. You always flag the edge cases. The station learns the standard.
Examples (Ingredient #4) are critical. Three handoffs you’ve written in the past. To different people. For different processes. The station learns how you adapt the tone and detail for different recipients. Output Over Process (Ingredient #5) is clear. The destination is a readable, executable handoff document in the recipient’s language.
How to build it
-
Identify the workflow to hand off. A repeatable process someone owns. A sales workflow. A hiring process. Client onboarding. Something you can document and someone else can run.
-
Know your recipient. Are they new to the business. Are they an expert in a related area. Are they an external vendor or an internal peer. Their context shapes what they need to know.
-
Write the workflow in its raw form. All the steps. The messy parts. The decisions. Not polished. Not translated yet. Just the process as you know it.
-
Pull three past handoffs you wrote. To different recipients. A handoff to a new team member. A handoff to a peer in a different department. A handoff to a vendor. These are the training set.
-
Show the station the raw workflow and the recipient type. “This is a sales process. The recipient is a new manager. They’ve never done this before. Write the handoff they need.”
-
The station translates. It reads the raw process. It identifies what a new manager needs to understand. It reorders the steps for learning, not execution. It calls out dependencies and gotchas.
-
Review the translation. Does it match how you’d write it. Are the key decision points clear. Are the implicit steps now explicit. Would the new manager understand it.
-
Sharpen if needed. If the translation missed a key dependency, show the station where it matters and why. If the tone doesn’t match how you talk to new managers, provide a corrected version.
What breaks it
-
Context about the recipient is missing. The station doesn’t know if the handoff is for a new manager or a peer. It defaults to either over-explaining or under-explaining.
-
The raw workflow is too implicit. You write “do the thing,” meaning the five-step process only you know. The station can’t translate what it can’t see. It just mirrors your notes.
-
Examples are too similar. You give three handoffs to managers for similar processes. The station learns “handoffs to managers look like this.” When a peer handoff arrives, it doesn’t know what to change.
-
No feedback loop on recipient success. The handoff lands. The new manager gets confused on day one. Nobody tells the station the translation missed something. Next handoff is still incomplete.
When it’s working
By week one, the station translates a workflow. The new recipient reads it and understands eighty percent without questions. Twenty percent needs a clarification conversation. By week two, the clarity is solid. Questions drop to ten percent. By week three, new people are executing workflows on day one because the handoff is written for them. By week four, handoff friction disappears. The only conversations are about business decisions, not process confusion.
The signal that the recipe is sharp: a new team member runs a handed-off workflow and does it exactly the way you would have, without ever shadowing you, because the translation was that clear.
Monday Move
Write the raw workflow for a process you run. Every step. No translation. Show it to the station. Tell it “the recipient is a new manager who’s never done this before.” Have the station translate while you watch. Where does the translation nail it. Where’s it missing context. That gap is what needs sharpening in the translation logic.
Dish 8 of 10 on the Operations Station. Build-note leverage: Context (Ingredient #2).