Frequently Asked Questions About Ideas To Thrive 22 Productivity Frameworks
22 answers covering everything from basics to advanced usage.
// Basics
What is the Eat the Frog technique?
Eat the Frog means doing the one task you most want to avoid — your honest A, the Frog — first thing before anything loud gets a vote. The Frog is rarely hard; it's avoided because thinking about doing it feels worse than the task itself. It's not costing you the 10 minutes it takes — it's costing your entire day as a low background hum while you pretend to be busy.
What is the Ivy Lee Method and why does the timing matter?
Each evening you write the six most important things for tomorrow in strict priority order, then work top to bottom one at a time. The value isn't the list — it's which version of you makes it. At 9pm, calm and slightly tired, you decide honestly. At 8am, rushed and half-caffeinated, you decide based on what's loudest. Writing it the night before removes the worst version from the decision.
What is a Ulysses Pact in productivity?
A Ulysses Pact is a structural commitment made in advance with your calm, strong self that removes your tired, tempted self from the decision entirely. Set the app blocker and leave your phone in another room before the session starts — not face down on the desk. Willpower is weakest exactly when you need it most, so the constraint must be environmental, not willpower-dependent.
What inputs help most when applying these frameworks?
At minimum, a plain-language description of your work context and current pain point. It helps enormously to also provide a raw unfiltered dump of everything you're working on or avoiding, a time horizon (today, this week, or ongoing system), and your named bottleneck if you can identify it. The more honest and unfiltered the task dump, the better the diagnosis.
// How To
How do I turn a vague task into something I can actually start?
Ask: 'What is the very next physical action?' Not the project, not the outcome — the specific thing your 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.' A brain cannot act on a label; it can only act on a verb with a hand attached.
How do I stop starting new projects before finishing old ones?
Apply Work in Progress Limits. Count everything currently in progress, set a hard ceiling of three to five, and start nothing new — no matter how exciting — until something ships and comes off the list. Use a three-column board (To Do / Doing / Done) with a strict limit on the Doing column that is never allowed to break. Eight things at 80% produce exactly zero real value.
How do I protect time for deep, focused work?
Apply the Maker's Schedule: pile all meetings, calls, and quick favours into one block, ideally the afternoon, and protect the rest of the day as one unbroken stretch. Then schedule Deep Work Blocks on the calendar exactly like a meeting with your boss — one you genuinely cannot casually cancel. The meeting is not the cost; the hours circling it where no deep work is possible are.
How do I know when a task is actually finished?
Write a Definition of Done in plain words before starting: a specific, checkable line like 'Three short paragraphs and a clear ask.' Not perfect — done. The moment you hit the line you wrote, you stop. Without a defined finish line, every task becomes about avoiding the discomfort of stopping, and you tweak endlessly. Stopping on the line isn't a failure of discipline — it's the plan working.
Is the 5-Second Rule really enough to break procrastination?
Alone it closes only the action gap — the two-to-three second window where your brain floods in with reasonable-sounding excuses like 'just check one thing first.' The countdown is too small for the brain to bother arguing with. But for a genuinely daunting task, pair it with the Two-Minute Version and a Next Action so there's a tiny, specific first move to launch into on '1.'
// Troubleshooting
Why do I still feel behind even on my most productive days?
Because your to-do list only ever shows the gap remaining, and your brain is wired to notice what's missing far more readily than what's covered. The fix is a Done List — a running list that grows instead of shrinks as you finish things. It costs ten seconds per task and gives your brain the visible progress signal it's been starving for.
Why can't I switch off work in the evenings?
Because your brain doesn't know work has ended unless explicitly told. Build a Shutdown Ritual: review the list, tick what's done, note where you left off on anything unfinished, close the laptop, and say 'Done' out loud. Without this signal, every unfinished item stays open in the background — you pay the full mental cost of working all evening while producing none of the output.
I keep running out of time even after cutting tasks — what's wrong?
You're probably treating time estimates as fixed. Apply Parkinson's Law: take your honest estimate and cut it in half, then set a real timer for the shorter number. What gets stripped under that pressure isn't quality — it's the second-guessing you've been mistaking for quality. Work expands to fill exactly the time you give it, and the extra time reopens decisions already made.
I applied several frameworks and now feel more overwhelmed, not less — why?
You almost certainly applied too many at once, which is the exact trap the system warns against. Stop, diagnose your single biggest bottleneck — starting, finishing, focusing, deciding, or drifting — and keep only the two to four frameworks matched to it. A can't-start person needs Next Action, Two-Minute Version, and the 5-Second Rule. A scattered person needs WIP Limits, 1-3-5, and Eat the Frog.
What's the single most common mistake people make with these frameworks?
Confusing urgent with important. Urgent is loud and rewards you with a relief hit the instant you deal with it, so a day full of urgent tasks feels productive. Important never fights — it just waits patiently for years. The Eisenhower Square exists to give the quiet important tasks a fighting chance against the loud urgent ones that keep winning your attention.
// Comparisons
How does the 1-3-5 Rule compare to a normal flat to-do list?
A flat list lets you hide the one big thing behind eleven easy ones and pretend every task deserves equal space. The 1-3-5 Rule — one big, three medium, five small — makes that dishonesty structurally impossible because the format only has room for one big thing, full stop. The list is deliberately shorter so you can't lie to yourself about what you actually did with your day.
How does Eat the Frog compare to just working through your list in order?
Working in order lets loud, urgent, easy tasks win the morning while the important A-task keeps sliding under the pile. Eat the Frog forces your honest A to go first, before anything loud gets a vote. The difference is decisive: with list-order, the Frog haunts your whole day as background hum; with Eat the Frog, the hardest thing is done before excuses have time to accumulate.
How is a Decision Journal different from just reflecting on past decisions?
Reflection lets memory edit itself to match outcomes — if it worked you 'remember' being confident, if it flopped you 'remember' having a bad feeling. A Decision Journal captures what you honestly expected and why, in your own handwriting, timestamped before you knew the result. Without that written record you're not learning from decisions — you're just watching memory flatter you in real time.
How does batching compare to multitasking?
Multitasking pays the Restart Tax on every switch and leaves Attention Residue on the previous task, so you're structurally unable to be fully present. Batching gathers same-type work into a single pass — all emails in one sitting, all calls back-to-back — paying the cognitive reload cost once instead of ten times. Ten emails answered together cost a fraction of the energy of the same ten scattered.
// Advanced
What is Attention Residue and why does it matter?
Attention Residue is the sticky piece of attention that stays behind on your previous task after you switch to a new one, making you structurally unable to be fully present on whatever you switch to. It's the named cost of multitasking and task-switching — not merely partly distracted, but unable to be fully there. It's why single-tasking, batching, and day theming exist.
What is Day Theming and when should I use it?
Day Theming points an entire day at one type of work — a writing day, a calls day, an admin day — so you pay the costume-change tax between cognitive modes once instead of six times. Use it when your work naturally clusters into distinct types and your week is fragmented across all of them daily. It's the recurring-structure version of batching, scaled to whole days.
How do I run a Weekly Review properly?
Block 30 minutes once a week. Empty the inbox to zero, look honestly at what actually got done versus what didn't, and set the small handful of things that matter most before the week starts pulling in six directions. Crucially, run it from the actual record, not memory — memory edits itself. There's no alarm that fires when priorities drift; this is the only moment you deliberately check.
How do I choose the right framework cluster for my situation?
Diagnose your bottleneck first, then match. Can't decide what matters? ABCDE plus Eisenhower Square plus 1-3-5. Can't start? Next Action plus Two-Minute Version plus 5-Second Rule. Scattered across projects? WIP Limits plus 1-3-5 plus Eat the Frog. Busy but no progress? Time Audit plus Done List plus Shutdown Ritual. The skill's whole job is prescribing the minimum effective set.