The Hidden Cost of Productivity Creep: Why Your Lists Feel Too Long

Most people treat list length as a volume problem, but the conversation between John Forrester and Ana Maria Gonzalez shows it is actually a structural failure. When your lists feel overwhelming, you do not have too much to do; you lack rigorous categorization. The consequence of mixing project outcomes, next actions, and waiting-for items is that your brain cannot distinguish between a commitment and a placeholder. This creates a tax on your cognitive bandwidth, forcing you to re-process the same information every time you look at your list. The advantage goes to those who treat their system with mechanical separation, not because it feels productive in the moment, but because it buys back the mental clarity required to execute.

The Architecture of Cognitive Load

The most common mistake in personal productivity is the mixed list. When you combine a project, which is a multi-step outcome, with a next action, which is a single-step task, you force your brain to switch gears constantly. Forrester and Gonzalez argue that this friction is the primary driver of list fatigue.

The bottom line if you are needing a refresher if you want to share with someone else best practices that you want to at the very least separate actionable inventory from non-actionable and never have those mixed up.

-- Ana Maria Gonzalez

When you mix these categories, you create a system that requires constant translation. You are not just doing work; you are constantly deciding what the work is. By separating your project index, the what, from your next actions, the how, you reduce the cognitive load of your weekly review. The benefit is a system that feels manageable because it only presents you with choices you are prepared to make in the moment.

Why Small Projects Are Your Biggest Trap

Conventional wisdom suggests that if a task is small or short-term, you do not need to track it with the same rigor as a real project. Forrester and Gonzalez dismantle this, noting that the size of the project is irrelevant to the system integrity.

Do yourself the favor of being really clean about what is a project and what is in next action.

-- John Forrester

The consequence of treating small projects as too simple to list is that they eventually morph, expand, or stall. When you fail to define the outcome, you lose the ability to review it. The system responds by creating anxiety because you know you have loose ends that are not being tracked. By applying the same rigor to a one-week project as a one-year project, you create a predictable, stress-free environment. The extra time spent defining a small project saves you from the chaos of a project that unexpectedly balloons in complexity.

The Systemic Role of Incubation

The most sophisticated part of this framework is the distinction between someday/maybe lists and incubation via a tickler file. Many people treat these as dumping grounds for things they do not want to deal with, but they serve different systemic functions.

A someday/maybe list is a recurring commitment to review potential future actions. It is an active part of your weekly cycle. In contrast, a tickler file is a way to route around your own attention. You are telling your future self that you do not need to think about this until a specific date. This is a systems-thinking move: you are offloading the burden of memory to the system itself. If you do not use these tools, your brain remains in a constant state of low-level monitoring, which compounds over time and leads to the overwhelm that makes people want to abandon their lists entirely.

Key Action Items

• Audit Your Lists (Immediate): Spend your next session separating every item into distinct categories: Projects, Next Actions, Waiting-For, and Someday/Maybe. If an item does not fit, it is likely non-actionable. Trash it, file it, or incubate it.
• Enforce Project Rigor (Ongoing): Stop defining a project by its duration. If an outcome requires more than one step to complete, it belongs on your project list. This pays off in 12 to 18 months by preventing the small task creep that causes hidden project failure.
• Optimize for the Weekly Review (Weekly): View your project list through the lens of your weekly review. If you do not need to see an outcome to feel confident about your progress, it does not belong on the list. Move it to your calendar or a tickler file.
• Leverage Context (Next Quarter): Once your lists are clean, categorize next actions by context, such as where you are or what tools you have. This reduces the mental effort of scanning your entire inventory when you only have 15 minutes to work.
• Adopt the Incubation Mindset (Immediate): Stop keeping maybe ideas in your active project list. Move them to a dedicated someday/maybe list or a calendar-based tickler. This creates separation between what you are committed to doing now and what you are merely keeping in view.