The Productivity Lie We've All Believed
Series: Nowhere & Everywhere — What context switching is costing your mind, your body, your relationships, and your life
If you’re just joining this series: Post 1 — “I’m Everywhere and Nowhere” | Post 2 — “The Fragmented Mind” | Post 3 — “Your Body Is Keeping Score” | Post 4 — “The People Who Pay the Price”
Someone asked me to build a roadmap.
This is a reasonable thing to ask a technical product manager. Roadmaps are part of the job — they’re how teams align on what’s being built, in what order, and why. They provide direction. They reduce confusion. They’re the kind of artifact that makes a complex operation feel manageable.
So I started building one.
And then my developers told me, with the patient honesty of people who had already learned something I hadn’t yet, that it was probably a waste of time.
Not because they didn’t want structure. Not because they were resistant to planning. But because priorities in our environment shift sometimes every day. They had watched enough roadmaps become irrelevant before they were ever used to stop investing belief in the exercise. They weren’t cynical. They were just accurate.
That conversation stopped me in a way I hadn’t expected. Because in the same moment I was absorbing what they’d said, I also became aware of something else: leadership had been making decisions around me, not through me. I couldn’t own what I hadn’t been included in. And the developers burning out in front of me — frustrated, depleted, increasingly disengaged — were not struggling because of a lack of effort or capability.
They were struggling because the system around them had made sustained, meaningful progress nearly impossible.
I had been trying to build a roadmap inside a building that had no fixed walls.
Here’s the productivity lie at the center of modern work: being busy feels like making progress.
It doesn’t feel like a lie in the moment. When the calendar is full and the Slack is moving and the decisions are being made, there’s a sensation that resembles productivity. The day has weight to it. Things are happening. You are clearly needed.
But at the end of a week with twelve hours of standing meetings across three teams — each one operating in a completely different domain, each one requiring a fully present, fully informed version of you — I started asking myself a quiet question on Friday afternoons: what actually moved?
Not what was discussed. Not what was decided in principle. Not what was added to a backlog or assigned to a follow-up. What actually finished? What crossed from one state to another in a way that couldn’t be undone?
Most weeks, the honest answer was: very little.
And this is the mechanism that Gloria Mark’s research begins to illuminate. When the average worker switches tasks every ten minutes, and it takes over twenty-three minutes to fully refocus after an interruption, the math doesn’t work. A meeting-heavy, notification-flooded, always-switching day cannot produce the kind of deep, sustained output that meaningful work requires. Not because the people in it aren’t capable. Because the structure itself is consuming the capacity it needs to produce results.
Busyness and productivity are not the same thing. We have built systems that are extraordinarily good at generating the former while quietly starving the latter.
The roadmap wasn’t failing because of poor planning. It was failing because the system it was supposed to sit inside had no stable ground to build on.
Consider the forces at play simultaneously. Leadership is mandating the implementation of AI across all practices — an initiative that sounds like forward momentum but arrives without guardrails, without agreed-upon tools, without clarity on what’s permitted. Security is pushing back on what can be used. Other leaders are pushing forward regardless. Nobody has written the rules yet, which means every team is navigating a different interpretation of the same directive, and none of those interpretations are stable enough to plan around.
Meanwhile, decisions are being made above and around — rather than through — the people responsible for executing them. When leadership bypasses the chain of command, it doesn’t just create confusion. It creates orphaned work. Effort that gets expended on one direction before a quiet decision above has already changed it. Tasks completed in good faith that become irrelevant before they’re ever used.
This is the structure inside which my developers were being asked to build things. And they were burning out — not quietly, not privately, but visibly. Frustration visible in meetings. Disengagement creeping into conversations. Not because they lacked capability or commitment, but because they had learned through repeated experience that in this environment, effort and outcome were no longer reliably connected.
That is a system problem. And no individual productivity practice — no time-blocking, no morning routine, no focus app — can fix a system problem from the inside.
That roadmap conversation did something unexpected: it gave me a clear view of what I had been trying to do for months.
I had been attempting to impose productivity onto a system that wasn’t structured to support it. Working harder inside a framework that was quietly working against me. Planning carefully inside an environment where the ground moved faster than any plan could account for. And absorbing — personally — the cost of a structure that was producing confusion, bottlenecks, and burnout not because the people inside it weren’t capable, but because the system itself had gaps that no individual effort could bridge.
That’s the productivity lie. Not that you aren’t working hard enough. You are. The lie is that working harder is the answer when the problem is structural. The lie is that a better morning routine, a tighter task list, or a more disciplined approach to your calendar will fix something that exists several layers above your personal behavior.
You are not failing at productivity. You are succeeding at surviving a system that was never designed to let you produce at the level you’re capable of.
And here’s what that system costs beyond the work itself — beyond the roadmaps that become irrelevant and the developers burning out and the to-do lists that grow faster than you can clear them. It costs you something more personal. Something you carry home every night without meaning to.
Because when you’ve spent all day being a technical product manager, a team lead, an AI implementation strategist, a political navigator, and a buffer between leadership and the people who actually build things — by the time you walk through the door, which version of you is left?
That’s where we go next.