Ideas To Thrive 22 Productivity Frameworks

Last updated: 17 August 2026

Apply a specific, structured productivity framework (or combination of frameworks) to any work situation to eliminate wasted effort, finish what matters, and stop mistaking busyness for progress.

// TL;DR

The Ideas To Thrive 22 Productivity Frameworks skill is a diagnostic toolkit that matches specific productivity frameworks — like Eat the Frog, the Ivy Lee Method, Work in Progress Limits, and the Eisenhower Square — to your exact bottleneck instead of dumping all 22 on you at once. Use it whenever you feel overwhelmed, scattered, stuck, or busy-but-unproductive, or when you need to prioritise a task list, break procrastination, design a daily or weekly work system, or audit where your time actually goes. It starts by diagnosing whether your problem is starting, finishing, focusing, deciding, or drifting, then prescribes the minimum effective framework cluster.

Framework

// When should you use the 22 productivity frameworks?

Use this skill whenever a user feels overwhelmed, stuck, scattered, or unproductive — or when they need to design a daily/weekly work system, prioritise a task list, break procrastination, or audit how their time is actually being spent.

// What do you need to provide before applying these frameworks?

Current situationrequired
A plain-language description of the user's work context: what they do, what their current pain point is (e.g. too many open projects, can't start tasks, distracted all day, feel busy but produce nothing).
Task list or project inventory
A raw dump of everything the user is currently working on, needs to do, or is avoiding — as unfiltered as possible.
Time horizon
Are we solving for today, this week, or designing an ongoing system? This determines which frameworks to prioritise.
Biggest bottleneck
If the user can name it: starting tasks, finishing tasks, deciding what matters, staying focused, recovering at end of day, etc.

// What core principles power every one of these frameworks?

The Loud vs. The Important Distinction

Urgent things buzz, ping, and fight for attention. Important things sit quietly and wait years if you let them. The entire productivity problem is that loud masquerades as important. Every framework here is, in some form, a mechanism to give the important a fighting chance against the loud.

Decide With Your Strong Self, Execute With Your Weak Self

Willpower is weakest exactly when you need it most — tired, bored, tempted. The fix is never to rely on the weak version to make decisions. Make the decision once, in advance, with the calm strong version of yourself, and structure the environment so the weak version never gets a vote.

Progress Over Motion

Eight things stalled at 80% produce exactly zero real value. One thing pushed all the way across the line produces all of it. Progress was never about how many things are moving at once — it's about how many things actually finish.

Vagueness Is the Enemy of Starting

Your brain cannot act on a label. It can only act on a verb — something with a hand attached to it. Any task that doesn't specify the very next physical action is not a task; it's a cluster of decisions wearing a single label.

The Restart Tax

Every switch between different kinds of work carries a cognitive reload cost — the same as closing one program and opening another, except the software is your own brain. Batching, day theming, and single-tasking all exist to pay this cost as few times as possible.

Attention Residue

Every time you jump from one task to another, a sticky piece of your attention stays behind on the last thing. You are never fully present on whatever you switch to — not partly distracted, but structurally unable to be fully there.

Parkinson's Law

Work expands to fill exactly the time you give it, no more and no less. The extra time is never spent improving the work — it is spent second-guessing decisions already made. Anxiety is a terrible editor.

Memory Edits Itself to Match Outcomes

The moment you learn how something turned out, your brain rewrites the original decision to match. If it worked, you remember being confident. If it flopped, you remember having had a bad feeling the whole time. Neither is true. Without a written record made before the ending is known, you are not learning from decisions — you are just watching memory flatter you in real time.

The System Must Signal Done

Without a clear finish line defined in advance, every task becomes about avoiding the discomfort of stopping. Without a shutdown ritual, every unfinished item stays open in the background of the mind, still running, still pulling attention — paying the full mental cost of working all evening while producing none of the output.

The List Shape Enforces Honest Ranking

A flat to-do list lets you hide the one big thing behind eleven easy ones. A shaped list — one big task, three medium, five small — makes that dishonesty structurally impossible. You cannot pretend every task deserves equal space when the format only has room for one big thing, full stop.

// How do you apply the 22 productivity frameworks step by step?

1
Diagnose the bottleneck before selecting frameworks
Ask: Is the problem (a) deciding what to work on, (b) actually starting work, (c) staying focused once started, (d) finishing things rather than accumulating half-done work, (e) recovering and switching off, or (f) systemic drift over weeks? Match the framework cluster to the diagnosis. Do not apply all 22 at once — that is itself a productivity trap.
2
Grade and shape the task list before touching any task
Run the ABCDE Method across every item: A = must do, real consequence if skipped; B = should do, mild consequence; C = nice to do, zero consequence if it never happens; D = delegate it; E = eliminate it, it should not exist on the list. Then apply the 1-3-5 Rule to shape the day: one big task (your honest A), three medium, five small. Nothing else competes for a slot. Find the two real A's hiding in the list — most lists of ten contain exactly two.
3
Identify the Frog and schedule it first
The Frog is the honest A task the user keeps sliding under a pile of C's. It is rarely hard — it is avoided because thinking about doing it feels worse than the task itself. It goes first, before anything loud gets a vote. The Frog is not costing 10 minutes — it is costing the entire day as a low background hum while the user pretends to be busy with something else.
4
Convert every stuck or vague task into its Next Action
For every item on the list that feels stuck, ask: 'What is the very next physical action?' Not the project, not the outcome — the next specific thing actual hands would do right now. 'Plan the holiday' becomes 'Text Sarah to ask which weekends she's free.' 'Sort the finances' becomes 'Open the banking app and screenshot this month's balance.' Rewrite every stuck item this way. Watch how many stop being stuck the moment they stop being vague.
5
Apply a Work in Progress limit to open projects
Count everything currently in progress. Set a hard ceiling of three to five items. Nothing new starts — no matter how exciting — until something on the list ships and comes off it. Use a simple three-column board (To Do / Doing / Done) with a strict limit on the Doing column that is never allowed to break.
6
Design the calendar using the Maker's Schedule principle
Pile all meetings, calls, quick favours, and interruptions into one block (ideally afternoon). Protect the remainder of the day as one long, unbroken stretch. A calendar with five interruptions spread across the day looks lighter than one with five stacked together — it never is. The meeting is not the cost; the 3 hours circling it are. Apply Day Theming for recurring structure: point an entire day at one type of work (writing day, calls day, admin day) to pay the costume-change tax once instead of six times.
7
Set up Ulysses Pact constraints before sitting down to work
The Ulysses Pact means making the decision once with the strong, calm self so the tired, tempted self never gets a vote. Set the app blocker before the session starts. Leave the phone in another room — not face down on the desk. The constraint must be structural, not willpower-dependent. Willpower is weakest exactly at the moment it is needed most.
8
Schedule Deep Work Blocks on the calendar as non-negotiable
Put deep work on the calendar exactly as you would a meeting with your boss — something you genuinely cannot casually cancel. The problem is never a shortage of hours; it is the shredding of existing hours by micro-interruptions. One uninterrupted stretch is worth more than the equivalent time scattered across the day.
9
Define Done before starting any significant task
Write in plain words exactly what done means for this task before starting it. Not perfect — done. A specific, checkable line. Example: 'Three short paragraphs and a clear ask.' Without a defined finish line, every task becomes about avoiding the discomfort of stopping. The moment you hit the line you wrote, you stop — and stopping is not a failure of discipline, it is the plan working exactly as built.
10
Use the 5-Second Rule to close the action gap
The moment the user feels the urge to start something they have been avoiding, count backwards: 5-4-3-2-1, then move. On 1, no exceptions. The countdown fills the two-to-three second gap between wanting to act and acting — exactly where the brain floods in with reasonable-sounding excuses ('just check one thing first,' 'start properly tomorrow'). The countdown is too small for the brain to bother arguing with.
11
Apply the Two-Minute Version to break procrastination on any mountain task
Shrink the very first move until refusing it feels genuinely ridiculous. Not 'write the report' — 'open the document and type the title.' Not 'go to the gym' — 'put your shoes on and stand by the front door.' Starting is the entire battle. Once inside the task, staying in is easy compared to getting in. Make the entry two minutes small — small enough that saying no to it would be a little embarrassing.
12
Apply Parkinson's Law by cutting time estimates in half
Take the user's honest time estimate for any task and cut it in half. Set a real timer for the shorter number. What gets stripped under that pressure is not quality — it is the second-guessing the user has been mistaking for quality. The extra time was never improving the work; it was anxiety reopening decisions already made and fussing over details nobody but the user would notice.
13
Batch same-type work into single passes
Group all emails together (one sitting, one time of day). Group all calls back-to-back. Group all errands in one loop. Every switch between different kinds of work carries a restart tax. Ten emails answered together cost a fraction of the energy of the same ten emails scattered across the day. The content never changed — you just paid the loading cost once instead of ten times.
14
Run the Ivy Lee Method every evening for tomorrow
Each evening, write the six most important things for tomorrow in strict priority order — no more than six. The next morning, work top to bottom, one at a time. The value is not the list; it is which version of you is making it. At 9pm, calm and slightly tired, you make honest decisions. At 8am, rushed and half-caffeinated, you make decisions based on what is loudest. Writing it the night before takes the worst version out of the decision entirely. Six lines, ranked, tonight. Tomorrow: open the laptop and go straight to line one before anything loud gets a vote. The word 'before' is the whole system.
15
Run a one-week Time Audit to see the actual schedule
Log what is actually happening in rough 30-minute chunks for one full week. Write as it happens, not from memory hours later. The result is almost never what people expect — not laziness, but busyness in places never previously suspected (recurring meetings that have not produced anything useful in months). You cannot fix a schedule you have never honestly looked at, the same way you cannot fix a budget you have never tracked. The audit reveals the leak before you try to plug it.
16
Build a Shutdown Ritual to signal end of work
At the same time each day: review the list, tick what is actually done, note exactly where you left off on anything unfinished (so tomorrow's self does not reconstruct from scratch), close the laptop, and say one word out loud: 'Done.' The phrase matters more than it should. The brain does not know work has ended unless told explicitly. Without this signal, every unfinished item stays open in the background, still running, still pulling attention — paying the full mental cost of working all evening while producing none of the output.
17
Keep a Done List alongside the to-do list
Every time something is finished, write it on a separate running Done Today list that grows instead of shrinks. The to-do list only ever shows the gap remaining. The brain is wired to notice what is missing far more readily than what is covered — which is exactly why the to-do list alone leaves a person feeling behind even on their best days. The Done List gives the brain the visible progress signal it has been starving for. It costs ten seconds a task to maintain.
18
Run the Weekly Review to prevent systemic drift
Block 30 minutes once a week. Empty the inbox to zero. Look honestly at what actually got done and what genuinely did not. Set the small handful of things that matter most for the week ahead before the week starts pulling in six directions. This is the Next Action question run at week-scale. There is no alarm that fires when priorities have drifted — no red flag in the calendar. This half hour is the only moment in the week where you deliberately check whether the system is still pointed at what you actually care about or just running on its own momentum.
19
Use the Eisenhower Square to triage anything that competes for attention
Draw four boxes. Urgent + Important: do it now, no debate. Important but not urgent: schedule it deliberately before the noise of the day eats it (planning, deep work, health). Urgent but not important: do it fast or delegate it entirely. Neither urgent nor important: delete it without guilt. Urgent feels like productivity because it fights for attention and delivers a small relief hit every time you deal with it. Important never fights — it just waits patiently for years while you stay busy doing everything except it.
20
Start a Decision Journal for any decision with real weight
Before knowing the outcome of a significant decision, write down what you honestly expect to happen and why, in your own words, with a date stamp. Weeks or months later, read it against what actually happened — no hindsight allowed to sneak in because the sentence is sitting in your own handwriting, timestamped before you knew. Without the written record, you are not getting better at deciding; you are just getting better at telling yourself a story about how good you already were.
21
Synthesise: select the minimum effective framework cluster for this user's situation
Present the user with a specific, named combination of two to four frameworks that directly address their diagnosed bottleneck. Explain why each was selected using the creator's language. Do not prescribe all 22 — prescribe the right ones. A user who can't start tasks needs the Next Action + Two-Minute Version + 5-Second Rule cluster. A user who is scattered across too many projects needs Work in Progress Limits + 1-3-5 Rule + Eat the Frog. A user who feels busy but makes no progress needs the Time Audit + Done List + Shutdown Ritual.

// What do these frameworks look like in real work situations?

A freelance designer has 12 active client projects, works long hours, ends every day feeling behind, and cannot figure out where the time goes.

Run the Time Audit for one week (30-minute chunks, written as it happens). Apply Work in Progress Limits — cap active projects at five, nothing new starts until one ships. Apply the 1-3-5 Rule daily so the most important client deliverable has a named slot. Use Day Theming (Monday = creative production, Tuesday = client calls and admin) to eliminate the Restart Tax. Build a Shutdown Ritual so the brain stops running open project loops all evening.

A knowledge worker has a long to-do list, avoids the hardest item on it every day, and fills time with small easy tasks that feel productive but don't move the needle.

Run the ABCDE Method on the full list — surface the two real A's hiding under the C's. Identify the Frog (the honest A that keeps getting avoided). Apply Eat the Frog: Frog goes first, before anything loud. Apply the Two-Minute Version to break the starting barrier on the Frog. Use the 1-3-5 Rule to shape the day so the Frog cannot be buried under eleven easy checkmarks.

A manager trying to do focused writing work keeps losing hours to messages and meetings scattered across the day and cannot complete a coherent piece of work.

Apply the Maker's Schedule: all meetings and calls are piled into one afternoon block; the morning is a protected unbroken stretch. Set up a Ulysses Pact — app blocker and phone in another room before sitting down, decided once with the strong self. Schedule Deep Work Blocks on the calendar as non-negotiable. Apply the Definition of Done before each writing session so there is a clear stopping point.

A founder keeps starting new initiatives before finishing existing ones, has many things at 60-80% complete, and nothing shipping.

Apply Work in Progress Limits immediately: count everything in progress, hard ceiling of three, nothing new starts until something ships. Apply the Next Action question to every stalled item to surface exactly what physical step is missing. Use the Eisenhower Square to triage whether each open item is genuinely Important or just loud. Apply Parkinson's Law — cut the time estimate for each remaining item in half and set a real timer.

// What mistakes should you avoid when using these frameworks?

Applying all 22 frameworks at once — this is itself the productivity trap the frameworks are designed to solve. Select two to four matched to your specific bottleneck.
Treating the to-do list as the system — the to-do list only shows the gap remaining, never the ground covered. Without a Done List alongside it, it will make even your best days feel like failure.
Letting the 'loud' win the morning — if the Ivy Lee Method is not run the night before, the rushed, half-caffeinated morning self makes decisions based on what is loudest, not what matters.
Relying on willpower at the moment of temptation — the Ulysses Pact only works if the structural constraint (app blocker, phone in another room) is set before the session, not after the temptation arrives.
Keeping vague tasks on the list — 'plan the holiday' is not a task, it is a cluster of decisions. A brain cannot act on a label. Any item that has no Next Action attached will stay stuck no matter how many times it is reread.
Measuring momentum by how many things are in motion — eight things at 80% produce exactly zero real value. In-progress is not a metric of success; shipped is.
Skipping the Definition of Done — without a finish line defined in advance, every task becomes about avoiding the discomfort of stopping, leading to endless tweaking and reopening of completed work.
Confusing urgent with important — urgent is loud and rewards you with a relief hit the instant you deal with it. Important is quiet and will wait years. A day full of urgent tasks feels productive and produces nothing that matters.
Treating time estimates as fixed — without applying Parkinson's Law and cutting estimates in half, the extra time is spent in anxiety, second-guessing decisions already made, not improving the work.
Running the Weekly Review from memory — the review must surface what actually happened, not what felt like it happened. Memory edits itself to match your preferred narrative. The review requires honest inspection of the actual record.
Scattering interruptions across the day — a calendar with five interruptions spread across the day looks lighter than one with five stacked together. It never is. The invisible cost is the hours circling each interruption where no deep work is possible.

// What do the key productivity framework terms mean?

Ivy Lee Method: Each evening, write the six most important things for tomorrow in strict priority order. The next morning, work top to bottom, one at a time. The value is not the list — it is which version of you is making it. The night-before version is calm and honest; the morning version is rushed and loud-biased.
Decision Journal: A written record made before you know the outcome of a significant decision: what you honestly expect to happen and why, in your own words, with a date stamp. Read back against what actually happened to prevent memory from editing itself to match the outcome.
Ulysses Pact: A structural commitment made in advance — with the calm, strong self — that removes the weak, tempted self from the decision entirely. The constraint is environmental (app blocker, phone in another room), not willpower-dependent. You make the decision exactly once; your tired tempted self never gets a vote.
Maker's Schedule: A calendar architecture that piles all interruptions (meetings, calls, quick favours) into one block, leaving the remainder as a single long unbroken stretch. The invisible cost of a scattered calendar is not the meetings themselves — it is the hours circling each one where deep work is impossible.
Work in Progress Limits: A hard ceiling (three to five items) on how many things are allowed to be actively in progress at once. Nothing new starts until something already on the list ships and comes off it. Enforced with a three-column board (To Do / Doing / Done) where the Doing column limit is never broken.
Next Action: The very next specific physical action — something with a hand attached to it — required to move a task forward. Not the project, not the outcome. 'Plan the holiday' is not a Next Action. 'Text Sarah to ask which weekends she's free' is. A brain cannot act on a label; it can only act on a verb.
ABCDE Method: A grading system applied to every task before touching any of them. A = must do, real consequence if skipped. B = should do, mild consequence. C = nice to do, zero consequence if never done. D = delegate. E = eliminate. Most lists of ten contain two real A's — the rest are C's wearing A's clothing.
Definition of Done: A specific, plain-language, checkable description of exactly what finished looks like for a task, written before starting it. Not perfect — done. Prevents the endless reopening of completed work that happens when there is no official permission to stop.
Day Theming: Pointing an entire day at one type of work (e.g. writing day, calls day, admin day) so the costume-change tax between different cognitive modes is paid once instead of multiple times across the day.
Batching: Gathering the same kind of work together and running it in a single pass instead of letting it interrupt across the day. All emails in one sitting. All calls back-to-back. All errands in one loop. Pays the restart tax once instead of once per item.
Restart Tax: The cognitive reload cost paid every time you switch between different kinds of work — equivalent to closing one program and opening another, except the program is your own brain reloading an entirely different mode of thinking.
Attention Residue: The sticky piece of attention that stays behind on a previous task after you switch to a new one, making you structurally unable to be fully present on whatever you switch to. The named cost of multitasking and task-switching.
Done List: A running list maintained alongside the to-do list where completed items are recorded throughout the day. Grows instead of shrinks. Provides the visible progress signal the brain is wired to need but that the to-do list alone never supplies.
Time Audit: A one-week exercise of logging actual activity in rough 30-minute chunks as it happens, not from memory. Reveals where time is actually going versus where you believe it is going. The prerequisite to fixing any schedule: you cannot fix a leak you have never seen.
Shutdown Ritual: A fixed, repeatable end-of-work sequence: review the list, tick what is done, note where you left off on unfinished work, close the laptop, say 'Done' aloud. Signals to the brain that work has ended so unfinished items stop running in the background, consuming attention without producing output.
5-Second Rule: The moment you feel the urge to act on something you have been avoiding, count backwards 5-4-3-2-1 and move. On 1, no exceptions. The countdown fills the two-to-three second window where the brain loads its reasonable-sounding excuses before they have time to take hold.
Two-Minute Version: Shrinking the very first move on a mountain task until refusing it feels genuinely ridiculous. Not 'write the report' — 'open the document and type the title.' Makes the entry point small enough to walk through rather than standing outside a mountain wondering why you cannot start.
Weekly Review: A 30-minute weekly block to get fully current: empty the inbox to zero, review what actually got done, and set the handful of things that matter most for the week ahead before the week starts pulling in six directions. The only moment in the week where you check whether the system is still pointed at what you actually care about.
Eat the Frog: The practice of doing the one task you most want to avoid — your honest A, the Frog — first thing in the morning before anything else. The Frog is not costing you the 10 minutes it would take to finish; it is costing you the entire day as a low background hum while you pretend to be busy with something else.
Eisenhower Square: A four-box triage matrix. Urgent + Important: do now. Important, not urgent: schedule deliberately. Urgent, not important: do fast or delegate. Neither: delete without guilt. The core insight: urgent feels like productivity because it fights for your attention and rewards you instantly. Important never fights — it just waits patiently for years.
Parkinson's Law: Work expands to fill exactly the time you give it, no more and no less. The fix: cut your honest time estimate in half and set a real timer for the shorter number. What gets stripped under deadline pressure is not quality — it is the second-guessing you have been mistaking for quality.
1-3-5 Rule: A daily task list shaped as: one big task, three medium tasks, five small tasks — and nothing else competes for a slot. Forces an honest ranking by making it structurally impossible to hide the one big thing behind eleven easy checkmarks. The list is shorter specifically so you cannot lie to yourself about what you actually did with it.

// FREQUENTLY ASKED QUESTIONS

What are the 22 productivity frameworks?

They're a curated set of decision-making and work-structuring tools including Eat the Frog, the Ivy Lee Method, the 1-3-5 Rule, ABCDE Method, Eisenhower Square, Work in Progress Limits, Deep Work Blocks, the Maker's Schedule, Ulysses Pact, Two-Minute Version, 5-Second Rule, Parkinson's Law, Batching, Day Theming, Time Audit, Done List, Shutdown Ritual, Weekly Review, Decision Journal, Next Action, and Definition of Done.

What does this productivity skill actually do?

It diagnoses your specific bottleneck — deciding, starting, focusing, finishing, recovering, or systemic drift — then prescribes a matched cluster of two to four frameworks rather than all 22. The core insight is that applying every framework at once is itself the productivity trap. You get the minimum effective set aimed precisely at what's actually broken.

How do I use these frameworks to stop procrastinating?

Combine three frameworks: convert the task into its Next Action (a physical verb, not a label), shrink it with the Two-Minute Version until refusing feels ridiculous, then use the 5-Second Rule to count 5-4-3-2-1 and move before your brain loads excuses. Starting is the entire battle — once inside the task, staying in is easy.

How do I prioritise a long to-do list?

Run the ABCDE Method first: A = must do with real consequences, B = should do, C = nice to do with zero consequences, D = delegate, E = eliminate. Most lists of ten hold only two real A's. Then shape the day with the 1-3-5 Rule — one big task, three medium, five small — so you can't hide the big thing behind eleven easy checkmarks.

How does this compare to just using a to-do list app?

A to-do list only ever shows the gap remaining, never the ground covered, so it makes even good days feel like failure. These frameworks add a Done List for progress signal, a Definition of Done for stopping, a Shutdown Ritual to close loops, and diagnosis to match tools to problems. A raw list is storage; this is a system.

When should I use these frameworks?

Use them whenever you feel overwhelmed, scattered, stuck, or busy-but-unproductive — or when designing a daily or weekly system, prioritising tasks, breaking procrastination, or auditing your time. The trigger is any gap between how busy you feel and how much genuinely matters actually gets finished.

What results can I expect from applying these frameworks?

Expect more things finished rather than more things in motion, a clearer sense of where your time actually goes, and less end-of-day dread. You'll ship the one thing that matters instead of accumulating eight items stalled at 80%. The frameworks won't add hours — they stop existing hours being shredded by interruptions and second-guessing.

Why shouldn't I use all 22 frameworks at once?

Because trying to run all 22 is itself the productivity trap these frameworks are built to solve. Overwhelm is the disease, not the cure. The skill deliberately diagnoses your one real bottleneck and prescribes only the two to four frameworks that address it — a scattered-across-projects person needs different tools than a can't-start person.

What is the difference between urgent and important tasks?

Urgent things buzz, ping, and reward you with a relief hit the instant you deal with them, so they feel productive. Important things sit quietly and wait years while you stay busy doing everything except them. The Eisenhower Square exists precisely because loud masquerades as important — the entire productivity problem in one sentence.

How do I figure out where my time is actually going?

Run a one-week Time Audit: log what you actually do in rough 30-minute chunks, written as it happens, not from memory hours later. The result is almost never laziness — it's busyness in places you never suspected, like recurring meetings that haven't produced anything useful in months. You cannot fix a leak you have never seen.

// GET THIS SKILL — FREE