Technology Can Do Almost Anything

The question that is starting to surface in leadership conversations, sometimes directly and more often hovering just underneath the agenda, is whether senior leaders are still the right people to be making certain calls. It is not a question of confidence in the people. The technology is faster, processes more, and in a growing number of domains, is producing better outputs than the humans who used to own those decisions.

It is a reasonable question. It deserves a serious answer rather than a defensive one.

What technology does exceptionally well is optimise. Given clear parameters, sufficient data, and a well-defined problem, it will find the best available path faster and more reliably than any human. That is not a threat to leadership. It is a clarification of what leadership is actually for. Because the work that precedes optimisation, deciding what the parameters are, which problem is worth solving, and what trade-offs are acceptable in the solving of it, is not a technical problem. It is a human one. And that is where leadership begins.

Clarity of vision

Not inspiring language. Not a strategy slide. A leader who has done the thinking to know what their organisation stands for when the tools around it change significantly.

Here is the practical test: ask whether the people in your organisation can make decisions without you. Not whether they are allowed to. Whether they actually do. If they are regularly waiting for sign-off on things that should sit within their remit, the vision has not yet become a shared mental model. It is still sitting in your head, which means it is not doing the work you need it to do. Vision that lives only with the leader is a bottleneck dressed up as strategy.

Technology will keep changing. The rate is not slowing. Leaders who have grounded their organisations in something more durable than a current process or a current capability give people the orientation to move with confidence when the environment shifts. That orientation cannot be generated by any system. It has to come from a human being who has done the harder, less visible work of knowing what they are actually for.

Clarity of execution

As technology takes on more of the operational load, the questions around authority, accountability, and scope become more consequential, not less. Who decides when the model is wrong? Who carries responsibility when an automated process produces an outcome nobody intended? Where does the technology's remit end and human judgment resume?

These are not configuration questions. They are leadership questions, and the organisations treating them as the former will discover why they were the latter at a moment they would not have chosen.

The practical move here is straightforward, if uncomfortable: name the person who carries the consequence if something goes wrong. Not the team. Not the function. A person. If that question produces a pause, or an answer that begins with "well, it depends," the boundaries have not been set. Accountability without a named human is not accountability. It is optimism with better documentation.

Leaders who define those boundaries clearly, before something forces the conversation, are doing something the technology cannot do for itself. It is not glamorous work. It is the work that makes everything else function.

Being vocally self-critical

This is the obligation that gets the least airtime, and it is the one I find most leaders are privately uncertain about.

The pace of change means leaders are frequently wrong sooner than they expected, and in more visible ways than earlier eras allowed for. The temptation to manage the appearance of certainty is understandable. The cost of it is that the people best positioned to surface what is actually happening learn quickly that honesty is not rewarded and calibrate accordingly. You stop receiving the signal you most need at precisely the moment you most need it.

The practical version of this is not a vulnerability exercise. It is a practice. In your next team setting, name one thing you got wrong and what you changed as a result. Say it plainly, without theatre, and then move on. Do not revisit it. Do not mine it for lessons beyond the one that is actually there. Then watch what happens to the quality and honesty of what comes back to you over the following weeks. Teams do not need leaders who are always right. They need leaders who are honest about when they are not, and who demonstrate that the organisation can tolerate that honesty without consequence.

Learning from others without losing your footing

The leaders most resistant to input are usually operating with the oldest map. They know the territory from when they first learned it, and they have been refining that knowledge ever since, largely from people who report to them. In a period where the territory is changing faster than the map can be updated, that is a structural problem.

Build one formal and one informal mechanism for hearing from people below your direct line. Not a survey. Not a town hall with prepared questions. A conversation where the stakes are low enough that honesty is safe, and where you are listening for what is actually happening rather than confirmation of what you already believe. The leaders navigating this period well are not the ones with the most data. They are the ones with the best signal, and signal comes from people who trust that telling you the truth will not cost them anything.

Technology will take on more. It should. But the question of what matters, who carries responsibility for it, and whether an organisation can learn fast enough to stay oriented in a period of genuine disruption, those are not technical questions. They are human ones. They require human judgment, human accountability, and a human being willing to stand behind the answers.

That has always been the work. The current moment simply removes every excuse for avoiding it.