Productivity

Productivity is the ratio of useful output to whatever input actually constrains it. For most knowledge work that input is not hours. It is undivided attention, which exists in far smaller supply than time and cannot be borrowed against. A productivity method is worth exactly as much as its answer to two questions: what is the binding constraint, and what does this practice do to that constraint. Most methods never ask the first question, so their answer to the second is unknowable.

The constraint sets the rate

Goldratt's Theory of Constraints came out of manufacturing and transfers without much loss. Throughput of a system is set by its slowest stage. Improvement anywhere else is invisible in the output and often makes things worse, because faster upstream stages just pile up work in front of the bottleneck.

In individual work the constraint is usually one of three things: available deep attention, decision latency (work sitting in someone else's queue), or clarity about what finished means. Each has a different fix, and the fixes do not substitute for each other. Answering email faster when the real constraint is three uninterrupted hours produces a clean inbox and no finished work. Diagnose the constraint before choosing a technique, or you are optimizing a stage that does not set the rate.

Attention reloads, it does not resume

Switching tasks is not a pause. It is unloading one working state and loading another, and the reload is not free. This has a practical consequence that most scheduling ignores: four separate one-hour blocks are worth considerably less than one four-hour block, because each block spends its opening minutes rebuilding context that the previous block already had.

This is the useful part of Cal Newport's deep work argument. Not that concentration is virtuous, but that certain work has a minimum viable block size below which the output is near zero no matter how many total hours you spend. Fragmenting a day into thirty-minute pieces does not slow that work down. It prevents it.

Where the common understanding is wrong

Productivity gets treated as a personal virtue, which makes it a character judgment instead of a diagnosis. Most of a person's output is set by the system they work inside: how many people can interrupt them, how long approvals take, how clearly work is specified. Those are structural conditions. Trying harder inside a broken structure is the least effective available move.

The second error is measuring activity because activity is easy to count. Tasks closed, messages sent, meetings attended. All of these can rise while output falls, and in an environment where they are watched, they will.

The third is the system itself becoming the work. Capture is a sound idea and David Allen was right that an unwritten commitment consumes attention until it is written down. The failure mode is capture without disposal. A list that only grows is not a system for getting things done. It is a debt ledger you have agreed never to settle, and every glance at it charges interest.