Frequently asked questions about thinking, epistemology, and cognitive tools. 3617 answers
Capacity changes as you age — working with these changes is better than fighting them.
Capacity changes as you age — working with these changes is better than fighting them.
Capacity changes as you age — working with these changes is better than fighting them.
Capacity changes as you age — working with these changes is better than fighting them.
Capacity changes as you age — working with these changes is better than fighting them.
Capacity changes as you age — working with these changes is better than fighting them.
Capacity changes as you age — working with these changes is better than fighting them.
Map your current capacity profile across six dimensions: processing speed (how fast you can work through novel information), working memory (how many items you can hold in mind simultaneously), pattern recognition (how quickly you see recurring structures across different situations), judgment.
Denial. You pretend your capacity profile has not changed, push yourself to operate the way you did a decade ago, and interpret the gap between expectation and reality as a personal failure rather than a biological transition. This produces burnout at 45 that you never experienced at 30 — not.
Capacity changes as you age — working with these changes is better than fighting them.
Identify a team you currently work with — a project team, a department, a household managing shared responsibilities, or any group that coordinates to produce output. List every person and their estimated individual weekly capacity (use the measurement from L-0962 if available, or a conservative.
Planning team output by summing individual capacities without accounting for coordination costs. This is the most common failure in team capacity planning and it is nearly universal. The math feels correct — four people, forty hours each, 160 hours total. But the math ignores the fact that.
When working with others collective capacity must be managed as carefully as individual capacity.
Pull up your calendar and task list from the past five working days. Categorize every block of time as either maintenance (keeping existing commitments running — client work, email, admin, recurring meetings, routine tasks) or growth (building new capabilities, learning new skills, starting new.
Treating all your time as equally productive and assuming that being busy means you are advancing. The failure is not laziness — it is diligence misdirected. You respond to every email within an hour. You never miss a deadline. You keep all your plates spinning. And you mistake this operational.
You need capacity for both maintaining existing commitments and growing new capabilities.
Count your current active commitments — projects, ongoing responsibilities, side pursuits, anything that occupies recurring mental bandwidth. Write the number down. Now calculate 60% of that number (round down). That is your target. Choose which commitments survive the cut, using one filter: which.
Cutting commitments in name but not in practice. You announce that you are focusing on three projects, but you keep checking in on the archived ones. You respond to messages about deferred work. You attend meetings for projects you supposedly paused. The cognitive load never actually decreases.
Doing fewer things often produces more total output because each thing gets adequate resources.
Build a Capacity Planning Operating System that integrates the full phase into a single, living document. It should contain seven sections: (1) Your measured capacity baseline — daily deep-work hours, weekly sustainable pace, and capacity by pool (creative, analytical, social, administrative),.
Completing this phase as an intellectual exercise and never operationalizing it. You understand the commitment-to-capacity ratio. You can explain Little's Law. You know that buffers prevent cascade failures and that seasonal variation is predictable. You could teach someone else every lesson in.
Aligning commitments with actual capacity is one of the most honest things you can do.
List the nine operational domains from Section 5 in a column: workflow design, time management, information processing, output quality, review systems, tool mastery, environment design, bottleneck analysis, capacity planning. Next to each, write a score from 1 (broken or nonexistent) to 5 (runs.
Confusing operational excellence with operational complexity. You build a seventeen-step morning routine, a color-coded calendar with six time-block categories, a Notion workspace with forty databases, and a weekly review template that takes ninety minutes to complete. The system is elaborate. It.