S · Recipe collection

Quick Recipes

Short methods that combine cognitive moves. Explore situations, examples, and related possibilities.

Choose a recipe in the practical Guide →

Explore this branch in the Atlas →

Choose a Quick Recipe

One Home for StateYou can remember seeing the answer, but nobody knows which message contains the current version. Give the information one dependable home, an owner and a date so people can act without another round of asking.
Capture at the TransitionYou reopen the work and spend the first ten minutes remembering where you were. Leave a tiny restart note exactly when you stop, switch places or pass the work to someone else.
Cue in ContextYou remember the intended action at every time except the useful one. Move one precise reminder to the place where you can actually do something, and remove reminders that have become background noise.
Retire the StaleAn old instruction keeps winning because it is easier to find than its replacement. Name the current version, remove obsolete copies from everyday use, and preserve only the history that still has a purpose.
Checklist the RepeatYou know how to do the job, yet a small omission keeps spoiling the result. Turn the few easy-to-miss essentials into a short check at the moment they matter, leaving judgment and exceptions visible.
Sharp HandoffYou explain the task, yet the receiver returns something different or keeps asking for missing pieces. Package the transfer so they can start, understand their authority, recognize completion and handle exceptions without guessing.
One Owner per OutcomeSeveral people are helping, but the result still waits for someone to finish it. Name one reachable owner, give them enough authority and resources to coordinate, and keep contributors, reviewers and approvers distinct.
Count the HandoffsThe work itself is quick, but it spends days moving between people. Trace the transfers, find where waiting or re-explaining accumulates, and remove or redesign one costly handoff while preserving useful independent review.
Machine the MechanicalYou are spending careful human attention on sorting, matching or arithmetic a tool could perform consistently. Give the stable operation to a suitable tool, expose its rules and exceptions, and keep interpretation with a responsible person.
Pilot Before PlumbingYou can picture an elegant app or automation, but you have not yet seen how the work varies. Run a small manual version first, then build only the part that stays stable and earns its upkeep.
Exception BasketThe routine works until an unusual case arrives, then somebody guesses or the case disappears. Define the ordinary limits and give everything outside them a visible review queue with a responsible human and response expectation.
Offline FallbackThe plan works only while one app, person or connection is available. Choose the small part that must still work when that dependency fails, prepare another route and rehearse it once.
Automate the Chore, Keep the ChoicePreparing for a decision takes so much effort that the tool starts making the decision too. Separate gathering, formatting and calculation from the choice itself, so support frees attention while the person still understands and owns the result.
Ask the Missing ExpertThe team keeps circling a question nobody present is equipped to answer. Name the missing competence, choose a qualified source and ask one bounded question, while keeping the final decision with the person who owns it.
Two Independent EyesOne confident assessment may carry a blind spot nobody has challenged. Get two assessments separately, using meaningfully different perspectives or methods, then examine their disagreements before a responsible person decides what to accept.
Warm Work Stays HumanThe words are polished, but the person who matters is missing from the exchange. Keep presence, apology, consent and commitment with the human whose act they are, using tools only for preparation that supports real listening.
Teach-Back Before TrustThe receiver says they understand, yet their next action reveals a different plan. Invite them to explain the result, assumptions, exceptions and next step in their own words so misunderstandings surface while correction is still easy.
Escalate the Red FlagA routine helper encounters something outside its authority, and continuing would make the problem worse. Define the signal, the authorized destination, the immediate safe action and the expected response before that situation occurs.
Make Right Easy, Wrong HardYour chosen action loses to the option that is easiest to reach. Remove one obstacle from the preferred path and add one reversible obstacle to the familiar failure path, keeping the arrangement transparent and voluntary.
Precommit in the Calm TimeYou know a pressured moment will make a familiar decision harder. Choose a voluntary boundary, its trigger, an escape clause and a review time beforehand, so the arrangement can support you without trapping you.
Rearrange Before ResolveThe intended action requires searching, clearing space or borrowing tools every time. Change layout, proximity or availability first, so the environment carries some of the setup burden instead of repeatedly demanding more motivation.
Minimum Necessary ContextThe helper asks for the whole folder, but the task needs only a few facts. Build a smaller packet that preserves what the work requires while removing unrelated identifiers, history, raw material and access.
Scaffold, Then FadeHelp gets the task finished, but you want the person to become able to do it independently. Move from demonstration to guided attempts, then reduce prompts only when unaided work, later retention and a new context support that change.
Total-System ReceiptThe new arrangement saves one person time, but someone else is entering data, fixing errors or maintaining it later. Write down the burdens removed and created for every affected actor before deciding whether the whole system improved.