Goal is state recovery first, not productivity optimization.
ScenarioOverloadRecovery
Overload Recovery
A recovery pattern that restores executable state within 24 hours when plan trust has collapsed.
Governing Message
On overload day one, recovery starts with reduction, not additional planning.
How This Scenario Is Different
Day one prioritizes task reduction and block reservation over precision.
Settings optimization is postponed to day two.
Recovery Scenes
Only the decisions that matter during overload are kept in these visual cards.
Acknowledge overload
On recovery day one, stop adding plans and reduce active tasks first.
24-hour recovery routine
Two 30-60 minute recovery blocks restore executable state quickly.
Day-two reordering
From day two, tune folders, recurring rules, and notifications in order.
24-Hour Recovery Flow
Simple on day one, precise on day two is the most stable pattern.
- STEP 1
Keep only 1-3 active tasks
Leave only must-do tasks today and move the rest to carry-over/hold.
- STEP 2
Reserve two recovery blocks
Reserve two 30-60 minute blocks in Time View to restore execution base.
- STEP 3
Re-design priorities on day two
From day two, rebalance priorities again from weekly perspective.
Mistakes That Delay Recovery
Introducing new system on day one
More rules during overload usually increases complexity.
Editing every setting before recovery
Changing notifications/recurring/folders together slows recovery.
Recovery Rules
Day one: reduce and reserve only
Focus on reduction and time reservation only on recovery start day.
Day two: tune sequentially
Adjust one layer at a time: folders -> recurring -> notifications.