In between two demanding work blocks, several legitimate demands compete at once. The useful question is which demand must be protected first and which can wait. The purpose here is protecting the capacity needed for reliable performance. Sustainable performance depends on managing load and recovery as part of the work system, not as an afterthought.
A simple decision tree
If the first signal is small tasks filling every open minute: use reduce unnecessary context switching. If the issue is missing information: use match high-focus work to your better energy window. If the problem is pressure rather than information: use review workload capacity weekly. The point is to match the tool to the constraint instead of using the same response every time.
Decision 1: what are you protecting?
Name the outcome in one line. For between two demanding work blocks, ask whether the priority is speed, quality, trust, learning, ownership or another constraint. When two priorities conflict, decide which one wins for this attempt and why.
Decision 2: what will make you pause?
Use irritability increasing late in the day as an early warning. A pause is not inactivity; it is a chance to prevent waiting until exhaustion to reduce load. The pause can be one breath, one written note or one clarifying question.
Decision 3: when do you switch plans?
Plan B begins when the original approach no longer protects the objective. Switch from reduce unnecessary context switching to schedule recovery before exhaustion if the first tool is no longer producing useful information or if the cost of continuing rises.
Language for the decision point
This can wait because it does not change today’s critical outcome.
I need to renegotiate load rather than hide the capacity problem.
Review the branch you actually used
| Attempt | Decision point | Branch used | Evidence | Next rule |
|---|---|---|---|---|
| 1 | small tasks filling every open minute | reduce unnecessary context switching | number of heavy context switches | Change one variable |
| 2 | irritability increasing late in the day | match high-focus work to your better energy window | days with a deliberate shutdown | Keep what helped |
| 3 | What became predictable? | Repeat the reliable move | number of protected recovery breaks | Increase difficulty only if stable |
A before–during–after protocol
Before: use match high-focus work to your better energy window and decide what would count as a satisfactory response. During: watch for irritability increasing late in the day and using caffeine or urgency to override fatigue; when either appears, use use short movement or outdoor breaks and the short cue “I need to renegotiate load rather than hide the capacity problem.”. After: capture one piece of evidence about subjective energy at start and end of key blocks and one adjustment for next time. The protocol is deliberately short so it remains usable when between two demanding work blocks becomes demanding.
How to keep the protocol honest
Do not judge the attempt only by the final result. A good outcome can hide a poor process, and a difficult outcome can still contain a better decision. Review whether the chosen behavior supported protecting the capacity needed for reliable performance. If you notice filling recovery time with low-priority work, treat that as information about the design of the routine, not as proof that you lack the skill.
Use a smaller unit of improvement
Do not try to improve the whole situation at once. Choose one decision point, one sentence, one handoff, one pause, or one review habit. A small unit is easier to rehearse and easier to measure. Once it is reliable, connect it to the next part of the situation. This is slower than collecting many techniques, but it usually produces clearer learning because you can tell which change affected the result. Applied to between two demanding work blocks, keep the review tied to recovery & energy rather than turning it into a broad judgment about ability. Write one observation from the attempt, one decision you would repeat, and one change for the next comparable situation. If you cannot name those three items, the review is probably still too general. The purpose is to leave the situation with a usable next experiment, not a longer explanation of why it was difficult.
Questions people ask
What if I forget the technique in the moment?
Shorten it. Put reduce unnecessary context switching into the environment before the event and use one sentence such as “This can wait because it does not change today’s critical outcome.” rather than trying to remember a full framework.
What if another person makes the situation harder?
Keep the boundary between influence and control clear. You can use match high-focus work to your better energy window, state the relevant constraint, and decide whether to continue, pause, renegotiate or escalate.
How long should I practice before changing the plan?
Run several comparable attempts unless the approach creates a clear problem. Look for a trend in number of protected recovery breaks, not a perfect first performance.