What is a problem-solving playbook?
A problem-solving playbook is a short record of how you approached a recurring situation, what seemed helpful, and what you would change next time. It is a starting point for judgment, not a script you must obey. The most useful version tells your future self when to use it, which steps to consider, and when those steps no longer fit.
You do not need a dramatic success story. Perhaps a difficult week became slightly more manageable after you clarified a deadline. That is worth recording. Equally, a completed task that made no difference should not become a recommended step simply because you finished it.
This guide is about choosing and writing useful lessons. For the product workflow, see how playbooks work in Worress.
Start with a situation, not a personality judgment
“I'm bad at handling work” is too broad to help you later. “Two people gave me urgent tasks with conflicting deadlines” is specific enough to recognize. Describe the conditions rather than blaming yourself or someone else.
Choose one situation that might recur. Write down what mattered: the deadline, your available time, who could make a decision, and any constraints. Leave out private details you do not need. A playbook should help you remember the approach without becoming a permanent record of another person's sensitive information.
Then ask what a reasonable improvement looked like. It might have been getting a priority decision, protecting one evening, or finishing the essential part of a project. “Never feel stressed again” is not a useful success condition.
Use five small sections
1. When this fits. Name the trigger and relevant conditions. For example: “Use when new work arrives before existing commitments can be completed, and my manager can adjust priorities.”
2. What I tried. List actions in ordinary language. Start each with a verb: list, ask, compare, schedule, check. Keep steps small enough that you can tell whether you did them.
3. What seemed to help. Separate observation from interpretation. “My manager postponed one task after seeing the workload list” is an observation. “Clear information helped the decision” is a plausible lesson, not proof that the same result will happen again.
4. What to change or avoid. Record failed assumptions and costs. Perhaps evening work helped meet the deadline but left you exhausted. Do not quietly turn that emergency measure into your standard plan.
5. A review point. Decide when to ask whether the approach still fits. This can be after one conversation or at the end of a week, rather than after an arbitrary number of completed tasks.
Worked example: competing deadlines
This is an illustrative example, not a customer result. Maya receives two requests due Friday while already working on a report. Her first instinct is to accept everything and work late. Instead, she writes down the work, estimates the remaining effort, and asks her manager which outcome matters most.
The manager moves one request to the following week. Maya completes the report, but an afternoon focus session is repeatedly interrupted. At Friday's review, she records both observations rather than calling the entire plan a success.
Her playbook becomes:
- Use when: several commitments exceed the time available and someone can authorize a trade-off.
- Prepare: list deliverables, actual deadlines, and rough effort estimates. Mark estimates as estimates.
- Ask: “I can complete the report and one request by Friday. Which should take priority?”
- Confirm: write down the agreed change so everyone has the same understanding.
- Protect: choose a realistic work period and tell relevant colleagues when you will be available.
- Review: check whether the workload is achievable after the priority decision. Escalate again if it is not.
- Adaptation: afternoon focus time did not work in this setting; try a quieter period or a different location.
Notice what she does not save: “Always say no,” “Work two extra hours,” or “This fixes work stress.” The lesson depends on context, authority, and resources.
Try a ten-minute playbook exercise
Pick one recent situation that is finished enough to reflect on. Spend two minutes describing it and two minutes listing what you actually did. Next, circle one or two actions you believe helped. Add the evidence for each, even if the evidence is simply your own observation.
Use the remaining time to write a warning and a next-use trigger. A warning could be, “This assumes I can negotiate the deadline.” A trigger could be, “Open this when I have more than one genuinely competing commitment.” These details often make a short note more useful than a long checklist.
If you cannot identify anything helpful yet, save the unanswered question rather than inventing a lesson. “Next time, ask for advice earlier” may be more honest than claiming that your original plan worked.
Reuse means adapt, not repeat automatically
Before following a saved step, ask: Is this actually the same kind of problem? Do I have the same options? Has the risk changed? A conversation plan for a cooperative colleague may be unsuitable when there is harassment, retaliation, or a serious power imbalance.
Try one appropriate step and observe what happens. Update the playbook when new experience contradicts it. Keep older context if it explains the change, but remove instructions you would no longer recommend. A small, accurate collection is more useful than a large library of confident guesses.
The NHS problem-solving guide recommends identifying solvable problems, considering options, and making a specific plan. A personal playbook is one way to record your use of that general process; the NHS guidance does not validate Worress or guarantee results from saved plans.
Keep the tool in its place
A playbook cannot remove financial constraints, make another person cooperate, or replace medical, legal, or mental health advice. If distress is persistent or affecting daily life, consider qualified support. Immediate danger needs urgent local help, not a checklist.
If you already use Worress, review a completed problem and consider saving the lessons you want to keep. Beri's suggestions are AI-generated and may be incomplete or wrong; you decide what belongs in your playbook. You can also begin on paper. The useful first step is the same: write one thing you learned, with enough context to use it wisely.