There are periods at work when everything feels like a time-management problem. Too many meetings, too many messages, too many decisions and too many things waiting for you. The natural response is to optimise ourselves. Wake up earlier, block the calendar, decline meetings, make better lists, prioritise harder, find another productivity system. Sometimes that works.
But I think we occasionally diagnose the wrong problem. You may not have too much work. You may have too much work that requires you. That is an infrastructure problem.
I have become increasingly interested in this distinction because senior roles create an interesting trap. As you become more capable, more things naturally find their way to you. You can make the decision faster. You know the context. You can fix the presentation. You know what the CEO meant. You can connect two departments. You can spot the problem in the numbers. So you do it.
And because you are good at doing it, the organisation keeps routing more things towards you. Eventually, you become extremely efficient at carrying a system that was never designed properly in the first place. Your calendar becomes the integration layer. Your memory becomes the database. Your follow-ups become the project-management system. Your judgement becomes the process. Your anxiety becomes the notification system. And then you wonder why there aren’t enough hours in the day.
This is why I think productivity advice has diminishing returns for senior people. At some point, you cannot organise your way out of structural dependency. You have to redesign it.
When I find myself repeatedly chasing something, I now try to resist immediately concluding that I need to become more disciplined. Instead, I ask a different set of questions. Why does this need chasing? Why don’t I already have visibility? Why does this decision need to reach me? Why does this information live with one person? Why are we discussing the same issue again? Why does this process require someone to remember the next step? And perhaps the most useful one: if the volume of this work doubled tomorrow, what would break?
That question exposes infrastructure remarkably quickly.
Good infrastructure is not necessarily sophisticated. Sometimes it is a clear owner. Sometimes it is one dashboard everyone trusts. Sometimes it is a recurring operating cadence. Sometimes it is a documented process. Sometimes it is automation. Sometimes it is simply deciding that a category of decisions no longer requires your approval.
The point is not to build systems for the sake of building systems. The point is to remove unnecessary human effort from work that will continue to happen.
I think this matters particularly for ambitious people because our instinct is often to increase our personal capacity. We become faster, more organised, more resilient and better at holding complexity. There is pride in being able to carry a lot. But there is a ceiling to that strategy.
At some point, the next level of performance doesn’t come from becoming a more efficient person. It comes from creating an environment that requires less efficiency from you.
This is also one of the differences between operating and scaling. Operating asks: how do I get all of this done? Scaling asks: why does all of this need to be done this way? One improves the person inside the machine. The other improves the machine.
Both matter. But if you have reorganised your calendar ten times and still feel permanently behind, perhaps the next productivity tool you need isn’t another productivity tool.
Perhaps you need infrastructure.