Why is work still so hard to do?

The destination only became clear in hindsight. The research started with a question, not an answer. Whatever came after arrived because the listening revealed it. Not because someone went looking for it.

That matters. Someone chose to spend eighteen months and significant personal resources doing nothing but listening — with no guarantee it would lead anywhere.

It led here.

Something kept showing up in these conversations. Not in the answers people rehearsed. Not in the confident descriptions of how their businesses run. It showed up in the pauses. In the half-laugh before an admission. In the moment someone stopped describing what they do and started describing what they actually do.

Every leader carries something. Not a briefcase — though several carry those too, stuffed with notebooks they half-use and diaries they mostly trust. What they carry is less visible. The list in their head that never quite makes it onto paper. The idea that arrived while driving and vanished before the next traffic light. The knowledge about a client, a property, a relationship — knowledge that lives nowhere except inside one person's experience.

The driving question — why is work still hard to do? — finds its first answer here. Work is still hard partly because the most basic act of working — catching a thought and turning it into action — remains unsolved for the people doing the most consequential thinking.

The lens shifted. The question was no longer what one person said, but what everyone said — often in different words, always without coordination, and almost never with any awareness that they were describing the same thing.

When fifty people independently describe the same pattern, it stops being anecdote. It becomes signal.

Somewhere in almost every business represented in this research sat a CRM. Someone had purchased it with good intentions. Someone had introduced it with some fanfare. And in the vast majority of cases, teams used it at a fraction of its capability — if they used it at all. The language changed from person to person but the story did not. A tool arrived. Training was minimal or absent. People used the tool for a fraction of what it could do. Workarounds emerged — spreadsheets, notebooks, memory. The workarounds became the real system. This is not a technology problem. It is a design problem. Tools that ask people to change how they work — without first understanding how they actually work — become furniture.

Underneath the abandoned CRMs sits a deeper pattern: software arrives without teachers. Across the vast majority of conversations, leaders described tools that someone had introduced into their business with little or no formal preparation. One leader described the rollout of an AI copilot into his organisation. Nobody provided formal training. He and his colleagues figured it out alone. Training, where it exists, protects the organisation rather than developing the individual. Someone ticks a box so the business can say it tried. Nobody checks whether the person is competent.

Leaders make consequential decisions — hiring, investment, strategy, client commitments — using information that is incomplete, delayed, or simply absent. They compensate with experience. They compensate well. But they know it is not enough. And nobody has given them anything better. One leader described making half-million-dollar hiring decisions by intuition. Another described deal data arriving three to four weeks after the fact — largely irrelevant by the time it reached him.

A paradox ran through this research that almost nobody named directly, though nearly everyone described it. As businesses adopted more systems and more automation, the people inside those businesses did not get less busy. They got busier. Every new platform comes with its own login, its own workflow, its own reporting rhythm. The work of managing the systems had become work in itself — a tax on the actual job.

This pattern is not historical. AI tools arrived the same way CRMs did. The leader figured it out alone. Nobody discussed training until someone outside the business asked about it. Tools without teachers is not a description of what happened five years ago. It is happening now, in real time, with the most consequential technology shift in a generation.

This was the hardest part of the research to describe, because absence does not announce itself. Nobody can quote silence. But the research made the absence visible in the most direct way possible — it became the thing that was missing. Someone sat across from these leaders, asked questions, and stayed long enough for the real answer to arrive.

What surfaced was not frustration. It was surprise. Surprise that anyone was asking.

Mid-conversation, leaders discovered things they had never examined. One fund manager realised his organisation should have provided training on a tool it had already rolled out. The question itself created the realisation. Another leader stopped mid-answer and wondered aloud for the first time how other people manage their work. He had never considered it — not because he lacked curiosity, but because nobody had ever created the conditions for the question to surface. A third leader described the single most useful piece of data he could imagine — knowing where deals are blocked in his pipeline — and then admitted he had never thought to ask for it.

The consultants sell transformation programs too large for medium-sized businesses and too generic for any. The technology companies sell tools designed for the vendor's workflow, not the user's. The training providers deliver compliance sessions that satisfy legal requirements and teach nothing. Nobody in the market is helping these leaders lead better in a way that fits how they actually work.

The research asked leaders what they would fix if they had a magic wand. The answers clustered around three things: knowledge, visibility, and time. Get what I know into others. Let me see what is actually happening. Give me back the hours the process consumes. Three expressions of the same absence — nobody has built the thing that fits how these leaders actually work.

The absence is not awareness. It is not ambition. It is not intelligence. The absence is someone willing to ask.

The research asked questions about the business and questions about the person. The assumption was that these would produce different kinds of answers. That is not what happened.

When asked about business bottlenecks, leaders answered personally — with their commute, their car park, the micro-logistics of being a person in a body trying to show up in three places at once. When asked which of their own answers drew the most emotional response, leaders answered institutionally — naming their organisation's inability to use its own people well. The personal and the institutional had collapsed into each other so completely that the leaders themselves could not distinguish between them.

This pattern appeared in nearly all fifty conversations. The boundary between person and business had dissolved. Not metaphorically. Structurally.

When the person is the business, the business has a ceiling. Leaders named themselves the main asset and then named themselves the main impediment — in the same conversation. One leader put it in numbers: fifty side projects moving at a snail's pace because he wanted to be wrongly involved in most of them. He said it himself. He knew the involvement was wrong. He knew it was slowing everything down. And the knowing did not change the doing. He built the business around his involvement, and removing it would require rebuilding the business while still running it. That is not ignorance. That is architecture.

The crossover had a new expression. Staff members used personal AI accounts to process company documents. Leases. Contracts. Client-sensitive information. The personal account held the company's confidential data. The boundary between person and business did not just blur. It opened a door that neither party knew was open.

Fifty conversations. Four findings. One picture.

Every conversation included a question about artificial intelligence. The responses told the same story. Most leaders used a personal ChatGPT account. The most common task was writing. The most common depth was surface-level. And the most common feeling, when asked about it, was a mixture of urgency and paralysis.

The second finding was tools without teachers. That pattern is not a description of what happened five years ago. It is happening now, in real time, with a technology that did not exist three years ago. Organisations roll out AI copilots without training. Leaders figure it out alone. Some call themselves dinosaurs and ask for someone to hold their hand. One business had a formal AI strategy with KPIs and training courses — and even there, the deeper conversation about what AI means for the person had not happened.

New tool. Same pattern. No training. No support. No formal approach. The leader carried it alone. The personal and professional were tangled beyond separation. If these conditions were temporary — if they were the growing pains of one generation of software, one period of adjustment — they would not reproduce identically with a technology that did not exist three years ago. But they did. Identically. Across every conversation that touched it.

The conditions the research found are structural. They do not resolve with a better tool or a bigger team. The first step is always the same: someone sits across from you, asks questions, and stays long enough for the real answer to arrive.

That someone delivered this groundbreaking, unfiltered research.

His name is Simon D'Arcy.