Productivity Is Not About Doing More — It's About Designing Better Work

Productivity gets reduced, most of the time, to a list of apps, a time-blocking method, and a personal willingness to say no to distractions. All of that has some value. None of it addresses the actual thing that determines how much gets done: the design of the work itself.

A stronger view is that productivity isn’t primarily a personal discipline problem. It’s a systems problem, at a smaller scale than an organization but with the same underlying logic — clarity, priority, and a repeatable way of executing, reviewing, and improving how the work happens.

01 — The Productivity Trap

Doing more does not automatically mean being more productive. It’s possible to close a day having answered forty messages, attended four meetings, and still not have moved the one thing that actually mattered. That’s not a discipline failure — it’s a sign that “productive” was quietly redefined as “busy,” and busy is easy to manufacture without producing much of value.

The trap is that busy feels like progress. It has motion, urgency, a full calendar. Real progress is quieter and harder to notice in the moment, which is exactly why it’s the one that gets crowded out.

There’s also a subtler version of the same trap: optimizing the wrong unit. Getting faster at answering messages doesn’t help if most of the messages shouldn’t have needed to exist in the first place. Getting better at running meetings doesn’t help if half the meetings were a substitute for a decision nobody wanted to make in writing. Speeding up the wrong activity just produces more of it, faster.

02 — Productivity Has a System

The same five-part structure that applies to organizational operations applies here, just at individual or team scale: clarity, priority, execution, review, and improvement.

Clarity — knowing specifically what needs to happen, not a vague sense that “there’s a lot going on.”

Priority — knowing which of those things actually matters most right now, as opposed to which one is loudest or most recent.

Execution — the actual doing, which should be the simplest part once the first two are genuinely in place.

Review — an honest look afterward at what happened, what worked, and what didn’t — not a ritual, an actual check.

Improvement — adjusting the system based on that review, rather than repeating the same approach regardless of whether it worked.

Most personal productivity advice lives entirely inside “execution” — better habits, better focus techniques — while skipping the clarity and priority stages that determine whether the execution was even pointed at the right thing.

That’s a bit like optimizing how fast you drive without first checking you’ve got the right destination. A faster car doesn’t help if the address was wrong. Better focus techniques don’t help much if what you’re focusing on was never actually the priority.

03 — The Hidden Cost of Poor Systems

Weak systems around work carry a real, often invisible cost: constant context switching between unrelated tasks, the same decision getting re-made from scratch because nothing captured it the first time, priorities that shift so often that effort gets abandoned halfway through, communication that exists only to compensate for information nobody wrote down anywhere durable, follow-up that wouldn’t be necessary if status were actually visible, and rework caused by requirements that were never fully clear the first time.

None of these show up as a single dramatic loss. They accumulate quietly, the same way the hidden operations problem does at the organizational level — and for the same underlying reason: the system isn’t carrying enough of the weight, so the person has to.

Context switching in particular is easy to underestimate, because it doesn’t look like a cost — it looks like flexibility, like being responsive. But every switch has a re-entry price: a few minutes of reloading where you were and what you were about to do next, paid every single time. Ten switches a day isn’t ten small interruptions. It’s a meaningful fraction of the day spent reloading context that a clearer system would have preserved for you.

04 — Personal Productivity vs Organizational Productivity

Here’s the part that’s easy to miss: a productive person inside a broken system is still constrained by that system.

Someone can have excellent personal habits — a clean calendar, a disciplined to-do list, real focus — and still be limited by unclear priorities coming from above them, information they don’t have access to, or a process that requires three approvals for something that should need one. Personal productivity systems can make someone more effective within the constraints they’re given. They can’t remove constraints that were never theirs to fix. That’s an organizational design question, not a personal one — which is why “just be more disciplined” advice runs out of usefulness fast in a genuinely disorganized environment.

05 — Design the Work Before Managing the Time

The more useful question usually isn’t “how can I manage my time better.” It’s “why does this work require so much time in the first place.”

Time management assumes the work itself is fixed and the only variable is how carefully you allocate hours to it. But often the real lever is upstream of that: the task exists because a process is unclear, the approval takes three days because nobody defined who’s actually authorized to say yes, the meeting is an hour because there’s no shared document that would have made it fifteen minutes. Redesigning the work removes the need to manage time around it in the first place. That’s a more durable fix than getting better at fitting a bloated task into a smaller box.

This reframe changes what “getting better at productivity” actually means. It stops being about squeezing more into the same hours and becomes about removing the reasons the work was bloated to begin with — a clearer request, a defined owner, a shared reference instead of a re-explained one. Time management, at that point, becomes a much smaller problem than it looked like at the start.

06 — A Practical Productivity System

At a practical level, five steps: capture, clarify, prioritize, execute, review.

Capture everything that has your attention out of your head and into one place you actually trust — not five half-remembered mental notes.

Clarify what each item actually requires: is it one action, several, or does it need more thinking before it’s even actionable yet.

Prioritize honestly, based on what actually matters, not on what arrived most recently or loudest.

Execute the highest-priority, clearest item — protected from the pull of whatever feels urgent but isn’t.

Review on a regular rhythm, not only when something goes wrong — check what’s working, what isn’t, and adjust before the gap gets expensive.

I wrote about a version of this years ago, in a book focused specifically on time and personal systems — the underlying argument hasn’t changed since: the constraint was rarely time itself, it was almost always the lack of a system around how time got used.

07 — Productivity as Organizational Design

The two levels connect directly. A person with a strong personal system, inside an organization with strong operational structure, isn’t fighting the environment to get things done — the environment and the personal system are pointed the same direction.

That’s why I don’t treat personal productivity and organizational operations as separate topics. They’re the same underlying design question — clarity, priority, visibility, and a way to improve — applied at different scales. Fix it at one level and the other becomes noticeably easier; neglect it at either level and the other one absorbs the cost.

It also means the most productive intervention available to a manager is rarely a productivity tip for their team. It’s removing the ambiguity, the unclear ownership, or the unnecessary approval step that was quietly forcing everyone downstream to compensate for it with more personal effort. Fix the design of the work, and the personal-productivity conversation gets a lot shorter.

Where this leaves the work

Productivity isn’t a personality trait, and it isn’t solved by a better app. It’s the outcome of how clearly the work itself is defined, prioritized, and structured — for one person or for an entire organization. Design that well, and doing the work stops requiring so much effort to manage in the first place.