Frequently asked questions about thinking, epistemology, and cognitive tools. 200 answers
Measuring everything except the constraint. You install a time tracker, a habit tracker, a mood tracker, and an energy tracker. You have dashboards. You have spreadsheets. You have more data than you know what to do with. But none of the metrics are directly connected to the specific constraint.
The most common failure is skipping exploitation entirely and jumping straight to elevation — buying a new tool, adding hours, hiring help, taking a course. Elevation feels proactive and clean. Exploitation feels like admitting you have been wasting your own constraint. The discomfort of that.
The most common failure is treating subordination as a permanent reduction rather than a strategic alignment. You cut your information inputs, cancel meetings, and restrict communication channels — and your colleagues think you have checked out. Subordination is not withdrawal. It is.
Elevating before exploiting. This is the most expensive mistake in the entire Theory of Constraints sequence. You hire a second person before you have ensured the first person is fully utilized. You buy a faster tool before you have removed the interruptions that prevent you from using the current.
Inertia — continuing to optimize a constraint that is no longer binding. You built systems, habits, routines, and mental models around the old bottleneck. You invested effort. You are proud of the improvement. And now you keep tuning, refining, and protecting those systems even though the.
Assuming that fixing the primary bottleneck will solve the system. You invest weeks addressing the most visible constraint, succeed, and expect throughput to leap to your target. When it barely improves, you conclude that the intervention failed or that bottleneck analysis does not work. Neither.
Treating the human bottleneck as a performance problem rather than a structural problem. When someone is the constraint, the instinct is to push them to work faster, work longer, or multitask harder. This backfires. You burn out the constrained person, degrade the quality of their output under.
Upgrading tools that are not the binding constraint. You buy a faster laptop, a better monitor, a premium subscription to your project management app, and a new mechanical keyboard. You spend $3,000 and a weekend configuring everything. Your throughput does not change because the actual bottleneck.
Automating a bad process instead of eliminating it. You notice that the seven-step report takes too long, so you write a script to auto-pull the dashboard data and auto-format the template. Now the waste is faster, but it is still waste. The review step still adds zero value. The formatting.
Treating all information delays as someone else's fault. When you cannot get the information you need, the instinct is to blame the person who did not reply, the system that was poorly designed, or the organization that does not share data. Sometimes that blame is warranted. But blame does not.
Treating every decision as if it were irreversible. Perfectionism disguises itself as rigor — you tell yourself you need more data, more options, more consultation, when the real function of the delay is avoiding the discomfort of commitment. The result is that two-way-door decisions receive.
The most common failure mode is treating energy as a character issue rather than a system variable. When your throughput collapses at 2 PM, you blame yourself for lacking discipline, willpower, or mental toughness. You push through with caffeine and self-criticism, producing low-quality work that.
Building elaborate dashboards instead of making the one thing that matters impossible to ignore. You spend a weekend configuring a Notion database with twelve metrics, color-coded status indicators, and automated rollups. It looks beautiful. You check it once on Monday, forget about it by.
Building buffers everywhere instead of at the constraint. You add slack to your morning routine, your email processing, your commute, your lunch break, your evening wind-down — and now your entire day is 40% buffer with no productive density. The system feels spacious but produces nothing. Buffers.
Journaling without reviewing. You dutifully record your constraint every day for three weeks, then stop because nothing seems to be happening. The entries pile up unread. The problem is not the journaling — it is the absence of the review cycle. A journal entry is raw material. A weekly review is.
Learning the framework without operating it. You read all twenty lessons. You can explain the Five Focusing Steps. You know the six bottleneck types. You could teach this material to someone else. And you never once measured your own constraint, never ran a single exploitation experiment, never.
Treating capacity as a character trait rather than a physical constraint. When you fail to complete everything on your list, you conclude that you lacked discipline, focus, or grit — that a better version of you could have done it all. This frames capacity violation as a moral failure rather than.
Confusing time at your desk with focused output time. Most people measure capacity by how many hours they "worked," which includes meetings, email, Slack, context switching, recovery breaks, and staring at a document without producing anything. This inflated number becomes the basis for planning,.
Glorifying the sprint. Hero culture tells you that the person who works eighty hours in a crunch week is more dedicated, more valuable, more serious than the person who goes home at five-thirty every day. This narrative is reinforced by managers who celebrate heroic efforts, by peers who compete.
Treating the morning capacity rating as a ceiling rather than a starting condition. You rate yourself a 2, choose the low-capacity plan, and then discover that a brisk walk, a good conversation, or a small win at 10 a.m. lifted you to a 4 — but you already committed to an admin day and missed the.
Calculating the ratio once, feeling alarmed, and then continuing to say yes to new commitments without updating the number. The ratio is not a one-time diagnostic — it is a running metric. Every new commitment changes the numerator. Every illness, life event, or seasonal shift changes the.
Treating load balancing as a one-time reorganization rather than a weekly practice. You redistribute your tasks once, feel satisfied, and then allow new commitments to cluster again around the same pressure points — Friday deadlines, end-of-month reporting, quarterly reviews. Without a recurring.
Treating buffer time as available time. The moment you see empty space on your calendar and fill it with a low-priority task or an optional meeting, the buffer ceases to exist. The point of a buffer is that it looks unproductive. It looks like slack. And the temptation — especially for.
Treating overcommitment as a badge of honor rather than a systems failure. You interpret the exhaustion as evidence of your dedication. You compare yourself to others who seem to handle similar loads without noticing that they are either doing less than you think, doing it worse than you realize,.