The short answer
Worress playbooks let you save a reusable approach from your experience. After a problem is completed, you can review what happened, choose the actions or lessons worth keeping, edit a draft, and explicitly save it. Participation is optional. Completing a problem makes it eligible for a review; it does not prove that every action helped or that the result was a success.
The important distinction is between a suggestion, an action you took, and a lesson you endorse. A good playbook keeps those distinctions clear. This guide explains the product workflow. For advice on writing a useful strategy, see build a problem-solving playbook.
1. Record the problem and what you actually tried
Start with a problem you want to work through in Worress. Describe the situation in enough detail to make the actions understandable, without adding private information that is unnecessary. Review any AI-generated breakdown before using it. A suggestion may be impractical, inaccurate, or outside your control.
As you work, keep action statuses honest. An action you completed is different from one you postponed, abandoned, or found irrelevant. Notes about what happened can be especially useful later: “I sent the request but received no answer” says more than a checked box alone.
You do not need to make your history look tidy for a future playbook. Incomplete attempts and unexpected obstacles are part of learning. They may explain why you would change the approach next time, even when they do not belong in the reusable action list.
2. Complete the problem when that status fits
When the problem is completed, Worress can offer a playbook review if one has not already been created for it. You can dismiss the invitation for that problem. Manual creation remains an option; the invitation is not a required final task.
Completion is the relevant eligibility condition. You do not have to report that events turned out better than expected or that the issue was not worth worrying about. Those would be poor substitutes for asking what you actually learned. A difficult outcome can still leave you with a useful lesson, and a good outcome can happen for reasons unrelated to your actions.
Do not close an unresolved problem merely to reach a playbook prompt. Keep the record faithful to your situation. If you are unsure whether you have anything to preserve, it is reasonable to wait.
3. Choose the evidence you want to keep
The review starts from completed actions rather than treating unfinished or not-relevant suggestions as proven steps. You decide which completed actions helped. A completed action should not be promoted to a recommendation automatically.
Recorded lessons can also provide useful material when there are no completed actions to select. When neither actions nor lessons provide enough information, the review can ask what helped. The purpose is to ground the draft in your experience, not fill a template with invented successes.
Read selected material carefully. You might keep “asked for a written deadline” and leave out “worked through lunch,” even though you did both. You might also preserve a warning: “Confirm the decision-maker before requesting approval.” A warning can be more reusable than a long list of tasks.
4. Review the draft before saving
AI-assisted generation and saving are separate steps. Beri can help organize selected material, but an AI draft may omit context, overstate an outcome, or make wording sound more certain than your evidence supports. Review it before deciding to save.
Give the playbook a title that names the situation. “Clarify priorities when deadlines conflict” is easier to recognize than “My successful week.” Check each step for feasibility, consent, and context. Replace claims such as “This prevents conflict” with instructions you can actually carry out, such as “Confirm the agreed priority in writing.”
You can revise or remove draft content. Preserve the meaning of your experience rather than accepting the first wording offered. Explicit saving is your decision that this version is worth keeping, not certification that it will work in every future situation.
Worked example: learning from a mixed outcome
Here is an illustrative workflow. Sam has completed a problem about preparing a presentation. Sam finished three actions: asked who the audience would be, rehearsed the opening, and stayed up late redesigning slides. The presentation happened, but Sam felt exhausted and the redesign added little.
At review, Sam chooses the audience question and rehearsal as helpful. Sam excludes the late-night redesign from reusable steps and adds a lesson about deciding the essential message before polishing the layout.
A draft might suggest “Research audience, rehearse, perfect slides.” Sam corrects the last step to “Check that each slide supports the main message; stop polishing when it is clear enough.” Sam also adds a limit: this approach needs adapting for presentations with formal technical or accessibility requirements.
After saving, Sam has a starting point for another presentation—not a guarantee of confidence or a record pretending every action was beneficial. The next time, Sam checks the audience, available preparation time, and requirements before reusing it.
A two-pass review exercise
On the first pass, check accuracy: Did I actually do this? Did I choose it as helpful? Does the wording distinguish an observation from a guess? Remove anything that invents motives, outcomes, or evidence.
On the second pass, check usefulness: When would I open this again? What would make it unsafe or unsuitable? Can I understand the first step without reconstructing the whole original problem? Add one review point so you know when to reconsider the approach.
If you want background on making practical plans, the NHS problem-solving guide explains considering options and specifying what, when, and whose support is needed. It is general guidance, not an endorsement of this product.
Reuse with judgment
Open a relevant playbook when a similar situation arises, then adapt it to current circumstances. A saved approach cannot replace professional advice or make decisions for another person. Worress and Beri are not a therapist, diagnosis, or emergency service.
If you already have a completed problem in Worress, start by asking one question: “What, if anything, would I want to remember next time?” That is enough to begin a review. Saving nothing is a valid outcome when the draft does not yet deserve your confidence.