A typical to-do list is a warehouse of anxiety: taxes, launch, health, kitchen, learn Spanish. Everything is safely written down and still requires a fresh planning session before you can touch it.
Russian productivity author Maxim Dorofeev built Jedi Techniques around a useful premise: do the difficult thinking before the moment of action. Externalize intentions, process inboxes, write tasks as visible steps, reduce unnecessary switching, and review the system often enough to trust it.
The book’s memorable metaphor is thought fuel. The brain has limited capacity for effortful decisions, so a good system should spend less of it on repeatedly reconstructing the same work.
The system in five moves
| Move | Purpose |
|---|---|
| Capture | Stop holding delayed intentions in working memory |
| Process | Decide what every incoming item means |
| Define the next action | Remove ambiguity before execution |
| Store externally | Keep actions, projects, calendar items, and reference material in reliable places |
| Review | Keep the system aligned with reality |
Recovery and fewer context switches support the whole cycle. They are not prizes for finishing all work, because work has declined to provide a finish line.
The publisher’s official book page emphasizes actionable task wording, emptying inboxes, regular review, and preserving “thought fuel.” These are the author’s practical mechanics, not a clinically validated package.
Thought fuel is a metaphor, not neuroscience
Dorofeev uses thought fuel to explain why difficult decisions feel harder after a day of meetings and interruptions.
There is no thought-fuel gauge in the brain. Simple “willpower as a battery” claims have a much messier research history than productivity books suggest.
The metaphor is still useful if it prompts concrete questions:
- What am I trying to remember?
- Which decision am I making repeatedly?
- Which task has no obvious start?
- How often am I switching context?
- Did I leave difficult work for my least capable hour?
You do not need to believe in a literal tank to stop driving with the handbrake on.
Use the metaphor to schedule rather than moralize. Put high-uncertainty work into a period with enough capacity, reduce repeated decisions, and leave mechanical actions for lower-capacity windows. Do not infer that a difficult afternoon reveals a fixed personal resource level.
Sleep, health, mood, workload, and environment all affect available capacity. Persistent impairment deserves an appropriate response beyond list design.
External memory works—if you maintain it
Research on intention offloading finds that calendars, reminders, and lists can improve prospective memory: remembering to perform an intended action later.
A review of intention offloading describes how reminders, calendars, and lists support delayed intentions by transferring part of the work into the environment.
Offloading can create dependence. A 2026 experimental study found that external reminders improved performance while available, but after removal participants remembered previously offloaded intentions less well than those who had relied on memory.
The practical answer is not to avoid tools. It is to maintain them, protect critical information, and avoid placing an important commitment in a system you never review.
The catch is dependence. If the reminder disappears, the intention may disappear with it. A captured task is useful only when it lands somewhere you review.
That means:
- fewer trusted inboxes;
- reminders attached to the right context;
- backups for important information;
- regular reviews;
- no fantasy that “saved” means “handled.”
A note in an app you never open is not a system. It is a digital burial site.
Write the action, not the problem
| Problem label | Actionable step |
|---|---|
| Portfolio | Pick three projects for the home page |
| Taxes | Download the income statement |
| Dentist | Call the clinic and book a check-up |
| Launch | Ask Priya to confirm the release date |
A useful task says what to do and what “done” looks like.
This does not make every task pleasant. It makes resistance more honest. You are avoiding a phone call, not an existential cloud called “health admin.”
A verb alone is insufficient. “Prepare launch” begins with a verb and remains vague. Include the object and finish line: “Write three release-date options and send them to Priya for a decision.”
Concrete plans may reduce interference from unfinished goals. In experiments by Masicampo and Baumeister, unfinished goals produced more intrusive thoughts and harmed performance on another task; forming a specific plan reduced the effect. See the Journal of Personality and Social Psychology study.
Implementation intentions add a cue: “After the 10 a.m. meeting, I will write the three options before opening email.” A classic meta-analysis of 94 tests reported a medium-to-large overall effect, with results depending on domain, study quality, and motivation. A newer meta-analysis of mental contrasting with implementation intentions found a smaller effect around g = 0.336.
Context switching is expensive, but not exactly 23 minutes
Task-switching research consistently finds costs in speed and accuracy. Unfinished work can also leave attention residue after you move to something else.
The cost varies. The internet’s favorite claim that every interruption costs exactly 23 minutes is not a universal law.
A review of task-switching experiments shows reliable costs in response time and error, with preparation reducing but not eliminating them.
Sophie Leroy’s experiments describe attention residue: when people switched away from unfinished work, part of attention remained with it and performance on the next task suffered.
These findings do not mean all switching is avoidable. Customer support, care work, and management may require responsiveness. Use re-entry notes, role rotation, staffing, and bounded communication windows where the environment allows.
Practical measures:
- turn off nonessential notifications;
- batch small similar tasks;
- leave a written re-entry point before switching;
- protect short blocks for demanding work;
- separate managing several projects from doing several tasks at once.
Jedi Techniques versus GTD
The family resemblance is obvious. Both use capture, clarification, external storage, next actions, and reviews.
GTD emphasizes a complete workflow for commitments. Jedi Techniques emphasizes the cognitive price of maintaining that workflow: procrastination, unclear tasks, switching, recovery, and excessive system complexity.
If you already use GTD, you do not need to migrate. Use Dorofeev’s questions to simplify it.
GTD offers a broad commitment workflow; Jedi Techniques foregrounds the cognitive cost of maintaining and using it. The useful hybrid is small: a few capture points, clarified actions, current project outcomes, real calendar entries, and a review short enough to survive.
Do not keep parallel GTD and Jedi databases. A migration that reproduces every stale item is exactly the kind of repeated decision the systems are meant to remove.
A seven-day trial
- Capture loose commitments for 20 minutes.
- Process one current inbox.
- Rewrite ten vague tasks as actions.
- separate calendar items from flexible actions.
- remove one frequent interruption.
- leave a re-entry note before stopping difficult work.
- run a short review and delete what no longer matters.
Do not build a cockpit. Build enough trust that tomorrow’s list makes sense.
Where the Jedi system breaks
- every captured item becomes an active commitment;
- the review becomes a weekly inventory ceremony;
- completed task count replaces important outcomes;
- someone else’s requests silently occupy the whole list;
- rewriting tasks becomes safer than producing the artifact;
- recovery is postponed until the system is empty.
Repair these failures by archiving, limiting active projects, reviewing outcomes beside actions, and leaving the tool to do one real step.
A concrete example
The input “website launch” becomes a project outcome: “Pricing page published with approved copy and analytics.” The next action becomes: “Send Legal the three claims requiring approval.” The waiting item records Legal and the follow-up date. The calendar contains only the true review deadline.
Before switching away, leave a re-entry note: “Next: incorporate Legal comments into section two.” Tomorrow’s start no longer requires reconstructing the project.
Using the system in Flammy
Flammy should not become the universal inbox for email, links, and every work request.
Use it for selected actions:
- repeatable practices as tasks;
- meaningful multi-step outcomes as quests;
- a minimum acceptable version for difficult days;
- a personal reward for sustained effort.
XP makes action visible. It does not decide whether the action matters.
The verdict
Jedi Techniques is valuable because it moves productivity out of the moral category. If someone avoids “sort out the paperwork,” they may not need stronger character. They may need a task that explains what to do.
The best system is boring: you open it, understand the next move, and close it to do the work.
Related reading
- Continue with a simple weekly planning ritual.
Turn one intimidating project into a manageable quest. Name the result, add the first visible action in Flammy, and make the minimum version easy enough to start.
Break a project into quests in Flammy