| Dimension | Traditional time management | Kruse's 15 secrets |
|---|---|---|
| Core resource | Tasks and available hours | 1,440 minutes per day |
| Priority system | Long to-do lists | One Most Important Task |
| Scheduling | Flexible task lists | Non-negotiable calendar blocks |
| Communication | Continuous email and meetings | Batching and strict limits |
| Focus | Multitasking and responsiveness | Single-task concentration |
| Workday boundary | Finish when tasks are complete | Set a stopping time |
| Energy | Treats hours as interchangeable | Matches demanding work with peak energy |
| Capture | Relies on memory or scattered notes | Physical notebook as an external brain |
The power of 1,440 minutes
Kruse's first principle is built around a simple numerical constraint: every person receives exactly 1,440 minutes each day. The number creates a different mental model for productivity because minutes become a finite daily budget instead of an abstract resource.
The 1,440-minute concept transforms how individuals evaluate priorities. A meeting consumes minutes. An email consumes minutes. A business opportunity consumes minutes. Time spent with family consumes minutes. Sleep consumes minutes. Each decision therefore competes against every other possible use of the same daily budget.
Kruse uses the number "1440" as a physical reminder. He describes placing a large "1440" sign on his office door so that the scarcity of time remains visible during the workday.
The framework also introduces dollar-per-minute analysis. Kevin Harrington, the infomercial inventor and Shark Tank investor described in the book, evaluates opportunities by comparing potential financial upside with the minutes required to pursue them. The calculation forces an opportunity to compete on the value of the time it consumes.
Self-discipline becomes another part of this equation. Groupon co-founder Andrew Mason emphasizes self-discipline as a decisive differentiator between individuals with similar intellectual ability. Kruse's broader argument is that productivity depends heavily on what a person consistently does with limited resources.
The 1,440-minute model can therefore be expressed as a daily allocation problem:
The practical question is not whether every minute can be optimized. Kruse's framework recognizes that people need restful sleep and supportive relationships. The practical question examines which activities claim the limited minutes remaining once people satisfy those essential routines.
How to identify your most important task
The Most Important Task, or MIT, is the single daily priority that creates the greatest progress toward a person's primary goals. Kruse places the MIT above ordinary task lists because a day can contain dozens of completed activities while leaving the most consequential objective untouched.
The distinction becomes especially important when urgent work competes with strategic work. Email can feel productive because every completed message creates visible progress. A product decision, strategic document, sales proposal, or creative project may produce less immediate feedback while carrying greater consequences.
Mark Pincus illustrates the principle through product allocation. The book describes the Zynga co-founder and CEO as devoting more than 50 percent of his work hours directly to product development. The numerical threshold matters because it shows how a strategic priority can dominate the calendar.
Kruse also draws attention to the first two waking hours. Behavioral economist Dan Ariely identifies this early period as the optimal window for peak cognitive output. Kruse's recommendation is to protect the early part of the day for the MIT before reactive communication begins.
A practical priority structure looks like this:
The MIT does not need to be a large project. The chosen daily MIT can represent one concrete action that advances a larger strategic objective. The defining characteristic is use, not size.
The framework also changes how a person evaluates a successful day. Completing 20 low-value tasks does not compensate for repeatedly postponing the activity that drives the primary goal. A day containing one strategically important completed outcome can carry more value than a day containing a long list of minor completions.
Why Kruse replaces to-do lists with the calendar
Kruse argues that traditional to-do lists leave the execution problem unresolved. A list records intentions, but it does not determine when the work will happen.
Time blocking converts an intention into a calendar commitment. Instead of writing "prepare presentation" on a list, the person reserves a defined period for presentation preparation. The calendar therefore becomes an execution architecture.
Jordan Harbinger, co-founder of The Art of Charm, schedules his entire calendar in disciplined 15-minute blocks. Chris Ducker similarly schedules activities ranging from social media and team communication to quiet reflection.
The difference can be represented simply:
| Question | To-do list | Time-blocked calendar |
|---|---|---|
| What needs to happen? | Yes | Yes |
| When will it happen? | Often unclear | Explicit |
| How much time is available? | Unclear | Defined |
| What gets displaced? | Usually unclear | Visible |
| Can competing priorities be detected? | Difficult | Easier |
The following video breakdown examines Kevin E. Kruse's core premise that elite performers abandon open-ended to-do lists in favor of rigorous calendar scheduling and 1,440-minute daily budgeting.
3. focus block execution
- Focus Block Execution provides the decisive implementation mechanism that separates ultra-productive professionals from reactive workers in Kevin E. Kruse's productivity framework. Rather than scanning an open-ended list of forty candidate tasks throughout the day, the practitioner reserves fixed, unmovable calendar slots for high-use priorities. Execution within a dedicated focus block requires silencing digital notifications, closing browser communication tabs, and dedicating working memory exclusively to the designated task until the timer expires.
Routine vs technique
A primary insight from Kruse's research across ultra-productive leaders is the fundamental operational difference between an isolated technique and an integrated daily routine. An isolated technique, such as the Pomodoro rhythm or the touch-it-once guideline, delivers tactical utility only when someone remembers to activate it during work friction. In contrast, an integrated routine hardcodes these behaviors directly into daily habits and calendar architecture, making high output the default baseline rather than an act of fleeting willpower.
How to overcome procrastination
Kruse frames procrastination as a conflict between present intentions and the behavior of a future version of yourself. The person making the plan may genuinely want to complete the task. The person encountering the task several hours or days later may prefer an easier alternative.
A commitment device changes the incentives before that conflict occurs.
Kruse describes using constraints to prepare for a $54,425 keynote. The example illustrates the value of removing attractive escape routes before the work becomes uncomfortable. A future commitment can make avoidance more difficult than execution.
The same principle appears in several everyday forms:
- Create external accountability: Tell another person exactly what will be completed and by when.
- Pre-commit money or time: Pay for a trainer, reserve a workspace, or establish another consequence for cancellation.
- Schedule the work: Put the task on the calendar instead of leaving it as an intention.
- Remove alternatives: Eliminate distracting applications, meetings, or communication channels during the focus period.
- Visualize the future decision: Consider how the future version of yourself is likely to rationalize postponement.
The underlying mechanism is structural. Willpower is not assumed to remain constant throughout a day. A system can therefore make the desired behavior easier to execute when motivation declines.
Kruse's approach treats procrastination as a design problem within the personal operating system. The person who anticipates future temptation can create constraints while decision-making is still easier.
Why successful people leave work unfinished
Kruse makes a difficult observation about knowledge work: there will always be more work than available time. Work has no natural completion point because new incoming emails and operational demands continue to accumulate.
The implication is significant. A person who defines success as completing everything can never reach the finish line.
Sheryl Sandberg provides the book's boundary example. Sandberg leaves the office at 5:30 PM to eat dinner with her children at 6:00 PM. The fixed stopping point establishes a constraint that competing work cannot automatically override.
Former Intel CEO Andy Grove illustrates the same structural dilemma from an executive management perspective. A manager's responsibilities can continue indefinitely, so the manager needs deliberate stopping boundaries.
George W. George W. Bush exemplifies disciplined boundary control by reading two books weekly throughout his presidency.
The principle can be visualized as a boundary:
The boundary does not imply that unfinished work disappears. The realistic practitioner accepts unfinished tasks as a permanent characteristic of the knowledge-work domain.
Kruse's framework therefore separates responsibility from total availability. A person can take work seriously while also assigning explicit value to vital health and family relationships.
Why a notebook becomes an external brain
Richard Branson's notebook is one of the book's simplest productivity tools. Richard Branson carries an analog notebook everywhere and credits that habit with expanding the Virgin Group.
The logic is straightforward. Working memory has strict cognitive limits, causing unrecorded ideas to vanish rapidly. A physical notebook provides a portable external storage system.
Kruse also describes a shorthand notation system. Open squares identify to-do items, circles can represent calendar events, and question marks can mark questions. The symbols create a quick classification layer before captured information enters the broader productivity system.
The workflow is:
The important distinction is between capture and storage. Writing something down does not complete the productivity process. A captured item must eventually become a calendar commitment, delegated action, discarded item, or another defined outcome.
Aristotle Onassis is also presented as recommending the notebook habit to young entrepreneurs. The recurring theme is that valuable information should be captured at the moment it appears.
The notebook fuels Kruse's E-3C operating framework: capture gathers information, calendar blocks guarantee execution, and concentration shields working attention.
How to control email with 321Zero
Email becomes problematic when other people's priorities enter the calendar without deliberate filtering. Kruse's 321Zero system attempts to reverse that relationship by limiting email processing to three sessions per day, with each session capped at 21 minutes.
The numerical structure is explicit:
The 4 D's provide the decision mechanism for individual messages:
| Decision | Action |
|---|---|
| Do | Complete the task when it takes less than 5 minutes |
| Delegate | Transfer the responsibility |
| Defer | Put the required action on the calendar |
| Delete/Archive | Remove information that requires no further action |
The five-sentence email rule adds another constraint. HootSuite founder Ryan Holmes restricts every outbound email to three concise sentences.
International Power verified this principle when executive communication guidelines reduced corporate email traffic by 54 percent.
The combined system attacks email from two directions. Batch processing limits how often the inbox interrupts work. Short responses limit how much time individual messages consume.
The core framework establishes strictly controlled communication. Email remains available as an asynchronous communication channel, but the inbox does not automatically become the day's priority engine.
How to reduce unnecessary meetings
Kruse treats meetings as another potential source of fragmented attention. A meeting imposes an unyielding interruption, consuming calendar bandwidth while shattering deep concentration across fragmented workdays.
The book describes several mechanisms for reducing this cost.
Daily huddles can be capped at 15 minutes. Author Verne Harnish champions this concise daily huddle format. The purpose is to review metrics and remove roadblocks without allowing discussion to expand indefinitely.
Asana co-founder Dustin Moskovitz implemented No Meeting Wednesdays to guarantee uninterrupted technical focus. The rule creates one recurring day without internal meetings, giving employees a protected block for concentrated work.
Gumroad leader Ryan Delk enforced 20-minute default calendar invitations. Shorter defaults change the starting assumption from 30 or 60 minutes to a smaller unit.
Mark Cuban provides an even stricter example. The book describes him as avoiding meetings unless someone is actively writing a check.
The underlying structure is:
Meetings remain useful for situations where synchronous discussion has a clear advantage. The productivity principle is to make that need explicit before occupying multiple people's calendars.
Why saying no protects the calendar
Every professional agreement an individual makes consumes unrecoverable future minutes and blocks calendar bandwidth. The problem with distant commitments is that their cost can appear small when the commitment is made months before the work occurs.
Kruse calls these future obligations "distant elephants." A speaking invitation six months away may look harmless at the time of acceptance. When the date arrives, travel expenses and opportunity costs become immediate calendar liabilities.
Steve Jobs demonstrated strategic refusal by focusing Apple on very few flagship products. His approach to focus involved rejecting good ideas so resources could remain concentrated on higher-priority objectives.
Author James Altucher applies an explicit standard: commitments that do not produce a strong affirmative response should become candidates for refusal.
The calendar makes the opportunity cost visible. Saying yes to a meeting means allocating minutes to that meeting. Saying yes to a project means allocating future execution capacity. Saying yes to an invitation can consume preparation and travel time beyond the visible event.
Strategic refusal therefore protects the MIT and the broader goal hierarchy.
A useful decision sequence is:
- Identify the request: Clarify the exact scope of the incoming demand.
- Identify the time cost: How many minutes or hours will the commitment consume?
- Identify the strategic connection: Which current goal does it advance?
- Identify the displaced activity: Determine which high-value calendar block will suffer if someone accepts the demand.
- Make the decision: Accept, delegate, defer, redesign, or refuse.
The point is not to reject every external request. The point is to treat acceptance as an allocation decision.
How the pareto principle changes task selection
The Pareto principle, commonly expressed as the 80/20 rule, proposes that a relatively small portion of causes can generate a disproportionately large share of outcomes. Kruse applies this idea to personal and business productivity.
Vilfredo Pareto's original observations involved uneven distributions of wealth and agricultural output. Kruse extends the principle into task selection by asking which activities create the largest results.
The framework can be represented as:
Entrepreneur Yaro Starak combines the 80/20 principle with the Theory of Constraints to concentrate effort on high-leverage business activities.
Customer pruning is another application. Kruse describes eliminating high-hassle, low-margin customers in an early technology business. The decision frees capacity for customers who generate greater value relative to the resources required to serve them.
The 80/20 rule does not mean every situation produces an exact mathematical 80/20 distribution. Its practical value in the book is as a filter for identifying uneven contribution.
A person can apply the filter to projects, customers, meetings, marketing channels, products, or recurring responsibilities. The central question becomes: which small set of activities creates the largest share of the desired result?
How Drop, Delegate, or redesign frees time
The three Harvard questions provide a systematic way to audit recurring work:
- Can the activity be dropped?
- Can the activity be delegated?
- Can the activity be redesigned?
The book associates this framework with a reported saving of up to 8 hours per week among London knowledge workers. The numerical claim gives the framework a concrete productivity target, although the source material provided for this article does not include the underlying research details.
The first question removes unnecessary work. The second transfers appropriate work to someone else. The third changes the process itself.
Venture capitalist Mark Suster warns founders against slipping into administrative maintenance. Suster articulates his guideline clearly: "If you don't have an admin, you are an admin."
The book also gives a more controversial example involving a Verizon software engineer identified as Bob, who reportedly outsourced his own job to a developer firm in China. The example illustrates the extreme possibility of separating a person's formal responsibility from the activities that actually require that person's direct involvement.
A practical audit can use a weekly table:
| Activity | Current time | Decision |
|---|---|---|
| Recurring report | 90 min | Redesign |
| Calendar administration | 120 min | Delegate |
| Low-value meeting | 60 min | Drop |
| Customer follow-up | 180 min | Keep |
| Manual data entry | 150 min | Redesign |
The value of the framework comes from forcing every recurring activity to justify its continued presence.
Why Jack Dorsey themes his days
Day theming groups similar cognitive and operational activities into defined days. Kruse uses Jack Dorsey as the principal case, describing how Dorsey managed Twitter and Square by assigning themes to different weekdays.
The approach reduces context switching. A person who moves repeatedly between management, product development and administrative operations has to repeatedly change the mental frame used for decision-making.
A themed week can look like this:
The exact themes can vary according to the person's responsibilities. The underlying principle is to batch related work.
Dan Sullivan's Focus Days, Buffer Days, and Free Days provide another model. The book also describes Kruse's use of buffer days around vacations. A day before and after a vacation can provide space for preparation and catch-up.
The approach is particularly relevant to people managing multiple roles. Jack Dorsey's example demonstrates how a recurring structure can divide attention across two major organizations without requiring every responsibility to compete for attention every day.
Day theming therefore extends time blocking from individual calendar blocks to a weekly architecture.
Why "Touch it Once" reduces hidden work
Repeatedly reopening the same email, document, or task creates additional cognitive and administrative work. The first interaction does not resolve the item, so the item returns to the person's attention later.
The "Touch It Once" mentality changes the default. The professional resolves each inbound item upon first opening it.
The decision tree is simple:
The book recommends immediately completing tasks that require less than 5 minutes. My Smart Hands president Laura Berg eliminated hours of administrative drag by refusing to reread messages without taking immediate action.
The principle is particularly relevant to digital work because modern inboxes and document systems make postponement nearly frictionless. A message can be opened, partially read and postponed repeatedly.
Each repetition consumes attention.
"Touch It Once" therefore complements the 4 D's. Both systems attempt to force a decision at the point of contact rather than allowing unresolved inputs to accumulate.
The distinction between immediate execution and scheduled execution is also important. A task that takes less than 5 minutes can be completed immediately. A longer task should receive a defined next step, usually through delegation or a calendar block.
How a structured morning changes the day
Kruse recommends protecting the first 60 minutes of the day for activities that strengthen physical wellness and mental resilience. The "Sacred 60" creates a buffer before digital communication and external demands begin.
The routine can contain hydration, exercise, reading, reflection, planning, meditation, or other personally useful practices. The important structural feature is the protected hour.
Hal Elrod's Life S.A.V.E.R.S. framework provides another version:
| Letter | Practice |
|---|---|
| S | Silence |
| A | Affirmations |
| V | Visualization |
| E | Exercise |
| R | Reading |
| S | Scribing |
Arnold Schwarzenegger is also presented as maintaining early-morning exercise and reading as recurring activities.
The morning routine connects to the MIT principle. Opening an inbox first surrenders peak morning cognitive capacity directly to other people's agendas. If the first hour is deliberately structured, the person begins with activities selected in advance.
A simple morning architecture is:
Kruse's broader thesis demonstrates that high productivity begins long before someone opens an email client. The first hour establishes the conditions under which the remaining hours will operate.
Why energy matters as much as time
Kruse distinguishes between the fixed quantity of time and the variable quantity of human energy. Every person receives 1,440 minutes, but the quality of work produced during those minutes can differ substantially.
Energy pulsing alternates concentrated work with deliberate recovery. The book cites Draugiem Group research in which productivity tracking showed that top performers took regular short breaks rather than maintaining uninterrupted work for long periods.
The Pomodoro technique provides one concrete implementation: 25 minutes of focused work followed by a 5-minute restorative break.
The structure is:
Author Monica Leonelle utilized rigorous Pomodoro blocks to increase her creative publishing velocity sixfold.
Mohammed Dewji provides another energy-management example through a midday workout ritual intended to reset energy for afternoon work.
The implication is that a calendar should account for energy cycles, not simply availability. A 90-minute block placed during a person's strongest cognitive period can have a different output profile from the same 90 minutes placed during fatigue.
Energy management also includes sleep hygiene and deliberate daytime recovery. Restorative practices consume scheduled minutes while directly upgrading the cognitive yield of active work hours.
The book's productivity model therefore becomes multidimensional:
15 Secrets Successful People Know About Time Management Framework Explained
The 15 Secrets Successful People Know About Time Management Framework Explained provides an integrated architecture that synthesizes Kevin E. Kruse's productivity research into actionable daily protocols.
Kevin E. Kruse Habit Framework
The Kevin E. Kruse Habit Framework links individual behavioral triggers to calendar execution and energy recovery, ensuring that daily output scales predictably.
The E-3C system consolidates Kruse's productivity ideas into three core components: energy management, physical capture, and calendar execution.
Each component solves a different failure mode.
Energy: Physical and mental preparation determines the capacity available for focused work.
Capture: A notebook externalizes ideas, urgent commitments and creative observations.
Calendar: Time blocking converts priorities into specific periods of execution.
Concentrate: Single-task focus protects the scheduled work from interruption.
The complete operating system looks like this:
Fizzle founder Corbett Barr runs his organization through a structured personal operating system. The example reflects Kruse's larger argument that productivity stabilizes once individuals systematize their daily operating decisions.
The four components also connect directly to the earlier secrets. The Sacred 60 supports Energy. The notebook supports Capture. MITs and time blocking support Calendar. Focus blocks and single-task execution support Concentrate.
The system reduces dependence on moment-to-moment willpower because many decisions are made before execution begins.
How to Apply 15 Secrets Successful People Know about Time Management routine in daily life
Applying the key concepts of 15 Secrets Successful People Know About Time Management in daily life requires treating time as an irreversible 1,440-minute daily budget, scheduling one Most Important Task directly onto calendar blocks before opening communications, and eliminating multitasking through single-task concentration, physical capture notebooks, and proactive energy recovery.
Kevin E. Kruse's framework can be converted into a daily operating sequence that combines the individual techniques without requiring every technique to become a separate habit.
1. Start with the 1,440-minute budget. Treat the day as a fixed allocation of minutes. Identify the non-negotiable requirements for physical health and vocational priorities.
2. Choose one MIT. Select the single task that creates the greatest progress toward the current strategic objective.
3. Protect the first productive hours. Reserve the strongest cognitive period for the MIT before opening communication channels.
4. Put the MIT on the calendar. Assign a specific start time and duration instead of recording the task on a general list.
5. Capture new inputs immediately. Keep a notebook available for actionable commitments and fresh insights.
6. Apply Drop, Delegate, or Redesign. Review recurring activities and remove work that does not deserve personal attention.
7. Batch email. Use the 321Zero structure of three sessions with a maximum of 21 minutes each.
8. Process each email through the 4 D's. Do short tasks, delegate appropriate tasks, defer longer tasks to the calendar, and delete or archive irrelevant messages.
9. Reduce meeting time. Use asynchronous communication where possible, shorten default durations, and create protected no-meeting periods.
10. Say no to low-value commitments. Evaluate future requests against current goals before accepting them.
11. Find the high-impact 20 percent. Identify the activities, customers, projects, or decisions responsible for the largest share of desired outcomes.
12. Theme recurring work. Group similar responsibilities into days or blocks to reduce context switching.
13. Touch each input once. Resolve, delegate, schedule, or discard items when they are first processed.
14. Protect the first 60 minutes. Use a morning routine that supports physical wellness and mental preparation.
15. Manage energy and recovery. Alternate concentrated work with deliberate breaks and use physical exercise and restorative sleep to sustain cognitive capacity.
The unified daily sequence converts Kruse's fifteen standalone tactics into an integrated operating loop:
What the framework gets right and where it requires judgment
The strongest idea in Kruse's system is the connection between priority and calendar capacity. A goal has little practical value if every available period is already consumed by lower-value commitments.
The 1,440-minute model creates a clear scarcity constraint. The MIT creates a hierarchy within that constraint. Time blocking creates an execution mechanism. Capture prevents ideas and obligations from remaining in biological memory. Email and meeting rules protect the resulting calendar. Energy management addresses the human limitations of sustained attention.
The framework also contains several techniques that require adaptation. A 21-minute email session may not fit every role. A no-meeting day may be difficult for a customer-support organization. A themed weekday structure may be impractical when responsibilities change hourly. A strict 5:00 PM boundary may conflict with a particular job's operating requirements.
Individual organizational variations do not diminish Kruse's underlying mechanisms. Variations instead demonstrate how practitioners must calibrate core principles to specific vocational constraints.
The numerical claims in the supplied source material also vary in type. Certain figures denote structural framework metrics, such as 1,440 minutes, 21-minute email sprints, 15-minute daily standups, and 25-minute Pomodoro intervals. Other figures describe reported cases, such as a 54 percent email reduction, up to 8 hours saved per week, or a 6x publishing increase. The supplied NotebookLM material does not provide the underlying research details for those claims, so those figures should be treated as book-reported examples rather than independently verified measurements.
Daily execution checklist
- [ ] Protect the 1,440-minute daily budget upon waking.
- [ ] Execute one Most Important Task before checking incoming communications.
- [ ] Schedule focus blocks on the calendar without multitasking.
- [ ] Clear processing queues via the 321Zero sprint protocol.
What are the key takeaways from 15 Secrets Successful People Know about Time Management by Kevin e. Kruse?
The key takeaways from 15 Secrets Successful People Know About Time Management by Kevin E. Kruse center on eliminating to-do lists in favor of calendar time blocking, dedicating early morning peak cognitive energy to a single Most Important Task, batching email into 21-minute windows, enforcing strict meeting boundaries, and managing physiological recovery.
Kruse synthesizes these takeaways from surveying over 200 billionaires, Olympic athletes, and successful entrepreneurs. The resulting practices demonstrate that peak productivity emerges from ruthless protection of finite daily minutes rather than attempting to perform an infinite quantity of low-use tasks.
What is the main summary of 15 Secrets Successful People Know about Time Management?
The main summary of 15 Secrets Successful People Know About Time Management by Kevin E. Kruse is that sustainable productivity requires replacing unconstrained task lists with an integrated operating system: allocating 1,440 daily minutes intentionally, capturing commitments externally, anchoring priorities directly onto a calendar, focusing on one objective without distraction, and recharging mental energy.
15 Secrets Successful People Know About Time Management presents productivity as a system of disciplined allocation and protected execution. The fixed 1,440-minute budget establishes scarcity. The MIT establishes priority. The calendar establishes commitment. The notebook establishes capture. Email and meeting limits protect attention. The E-3C system integrates energy, external capture, calendar allocation, and focused concentration.
The framework's practical question is simple: where are today's minutes going?
A person who can answer that question precisely can also see which activities compete with the day's most important objective. The resulting system does not require every minute to become productive. The framework demands that professionals ruthlessly shield the precious hours reserved for strategic focus.
The book therefore moves time management away from the idea of completing everything. Its operating logic is to decide what deserves time, assign that time in advance, protect the resulting commitment, and preserve enough energy to execute it well.
Related book summaries
Productivity systems expand substantially when readers integrate Kevin E. Kruse's time management architecture with complementary operational frameworks across our summary library:
- Great at Work by Morten T. Hansen : Explores the discipline of doing less to achieve exceptional professional output.
- atomic habits by James Clear: Provides the cognitive habit loop architecture to make daily time blocking and calendar execution effortless.
- deep work by Cal Newport: Establishes rigorous distraction-free focus protocols for executing high-cognitive-demand tasks during protected calendar blocks.
- Getting Things Done by David Allen : Outlines universal external capture and inbox processing workflows that keep cognitive working memory clean.