Explore a topic
Focus and execution
Protect your attention, recover from interruptions and plan work you can finish.
Start with a practical guide
Resume after an interruption
A meeting interrupts a failing test. Leave five short lines, then check whether the same failure still applies before you continue.
Read the story LongreadResume work after an interruption
To recover focus after an interruption, start with a place to resume. Leave a short checkpoint before a planned break, then check what changed before continuing.
Read the storyStart with a collection
Compare all collections on this topic
Protect attention while using external memory on purpose
Reduce interruption costs and memory failures by batching low-urgency signals, designing explicit reminders and using cognitive offloading without accidentally outsourcing knowledge that still needs to be learned.
Batch repeated work without turning batching into a rule
Reduce avoidable setup and switching while preserving responsiveness where delay is costly. The pack separates batchable communication and maintenance from urgent channels, uses capture queues to protect focus, and gives batching an explicit stop condition.
Design the task around cognitive limits instead of fighting them
Use external memory, switch-cost awareness, sleep-sensitive task routing, short movement and transfer skepticism to protect task quality without turning cognitive science into a set of universal productivity hacks.
Resume the right task and remember the future action
Protect task quality across interruptions and delayed intentions by encoding resumption cues, avoiding nested goal stacks, designing reminders that bind cue to action, and separating execution support from internal-memory practice.
Turn goals into work that finishes and stays finished after hours
Use current goal-setting, weekly planning, reminder, unfinished-task and if-then evidence to create a practical execution rhythm for knowledge work.
Choose, adjust and finish goals without turning life into a busier calendar
Improve personal and work productivity at the level above task execution: decide which goals still deserve capacity, stop obsolete goals cleanly, redirect freed capacity, diagnose persistent procrastination and judge a productivity system by outcomes rather than visible busyness.
Make follow-through easier without a discipline contest
Choose practical supports for starting, repeating and returning to useful actions while protecting essential responsibilities.
Build habits for real time scales, stable cues and automatic starts
Replace 21-day myths and streak worship with evidence-aware expectations about repetition, context, self-selection, preparation and automaticity.
Keep useful work flowing when demand exceeds capacity
Apply queue, capacity, fairness and overload-control ideas to software, agent fleets and operational workflows so backlog, retries and one noisy workload do not turn pressure into collapse.
84 ideas
Pair a dull task with a compatible pleasure
Make the task less barren, not more complicated.
Read the idea ProtocolContrast the wish with the obstacle before making the plan
Imagine the useful result, then let reality into the room.
Read the idea ProtocolChoose a useful method you do not dread repeating
An impressive plan that you keep avoiding has a hidden cost.
Read the idea ProtocolUse a fresh-start date as a launch point, not a waiting room
The calendar can open a door. It cannot walk through it.
Read the idea ProtocolKeep the cue steady while the action becomes familiar
Automatic does not mean instant.
Read the idea ProtocolResume after a missed habit without inventing a debt
A broken streak is not an erased skill.
Read the idea ProtocolMake the early checkpoint return useful feedback
An earlier date helps only when something useful happens there.
Read the idea ProtocolRemove the alert, not only the urge to answer it
An ignored notification can still be an interruption.
Read the idea ProtocolTry less mobile internet without making yourself unreachable
Keep the useful phone. Experiment with the endless doorway.
Read the idea ProtocolPut a distinctive reminder where action becomes possible
A reminder at the wrong moment is often just another thought.
Read the idea ProtocolBatch low-urgency notifications into predictable windows
A notification can be cheap to read and expensive to recover from.
Read the idea ChecklistKeep an explicit bypass for truly urgent signals
Focus works better when your emergency door is narrow and visible.
Read the idea HeuristicOffload the intention when forgetting is the main risk
A reminder is useful when the problem is remembering to act, not understanding the action.
Read the idea PrinciplePut the action inside the reminder
'Remember this' is weaker than 'do this when this happens.'
Read the idea PrincipleOffload logistics, not the knowledge you need to own
A checklist can carry the groceries; it should not carry the skill you are trying to learn.
Read the idea ChecklistGive important external memory a fallback path
Offloading turns memory risk into access risk.
Read the idea ProtocolCheckpoint the task before a planned interruption
The cheapest resumption work is done before you leave.
Read the idea HeuristicResume from the saved state before rereading everything
Resumption can quietly become a second first reading.
Read the idea PrincipleMake interruption policy stricter as cognitive load rises
An interruption that costs ten seconds in email can cost much more inside a fragile mental model.
Read the idea ProtocolTurn communication checking into a scheduled task
Removing the ping does not help if you become the ping.
Read the idea ProtocolGive postponed intentions a trigger before they fade
Later is not a time cue.
Read the idea ProtocolPeriodically prove you can work without the external aid
A useful tool can become a hidden single point of cognitive failure.
Read the idea ProtocolFind the breaking point before production finds it for you
Capacity is a fact you discover by pressure, not a number you inherit from last year's diagram.
Read the idea PrincipleKeep headroom for variability and recovery
Slack looks inefficient until the first spike, outage or slow task arrives.
Read the ideaExplore another topic
Learning and skill building
Practice a skill, check what you remember and use feedback for the next attempt.
90 ideasProject delivery
Estimate the work, agree on what counts as finished and check risky changes before you make them.
96 ideasCareer and assessment
Prepare for assessments, build skills for your next role and show your progress with examples of your work.
96 ideas