Every reorganization produces a diagram, and every diagram carries the same quiet lie: that knowing where people sit tells you how work gets done. It does not. Kason Morris, who has spent nearly two decades across learning, skills, talent mobility, and workforce transformation, watched that gap open in real time during a redesign at a large organization. The structure was taking shape, boxes drawn, reporting lines agreed, and then someone in the room asked the only question that mattered. When a request comes in, who receives it? Who decides where it goes next? And what happens when it crosses two teams? The chart had answers for none of it. Morris built a practice around the problem, which he calls execution visibility, and the premise is simple enough to be uncomfortable: leaders should be able to explain how the work creates value, and most cannot.
The Question Behind The Diagram
The failure here is not that org charts are wrong. They are accurate about what they describe, which is ownership and hierarchy. The trouble starts when leaders treat a map of reporting relationships as a map of work, because the two almost never match. Value does not move down reporting lines. It moves sideways, across teams, through handoffs that nobody formally owns, carried by people improvising when the documented process fails to fit the situation in front of them. None of that appears in a box.
Morris frames the remedy as an act of following rather than reading. “To answer it, you have to follow the work,” he says. “Look at the decisions people make, the handoffs between teams, and the judgment they use when the process on paper doesn’t fit the situation in front of them. That view can change what leaders choose to do.” That last clause is the whole argument. Visibility is not a documentation exercise or a slide for the operating review. It is a decision input, and leaders who skip it are choosing between options they have never seen.
Misdiagnosis Is The Default
Consider what happens when a leader works only from structure. A delay surfaces in the monthly numbers. The chart points to a team, the team owns the step, and the conclusion writes itself: a performance problem, fixable with pressure, headcount, or a new manager. Morris argues that the real cause is often something the chart cannot show. “A delay that looks like a team performance issue may be a handoff no one clearly owns,” he says. That is a structural gap, not a people gap, and no amount of management attention on the team will close it. The intervention is aimed at the wrong target because the diagnosis came from the wrong instrument.
The same blindness runs in the other direction, toward work that looks worthless and is not. Repetitive tasks are the first items on any efficiency list, which is precisely why they deserve scrutiny before anyone touches them. “A task that looks repetitive may be where someone learns to handle exceptions,” Morris says. “If you change or automate that task, you need to know where that practice will happen next.” Organizations develop judgment the same way individuals do, through repetition that eventually produces pattern recognition. Strip out the repetition and the capability goes with it, often silently, surfacing years later as a bench that cannot handle anything unusual. The savings land in the current quarter. The cost lands somewhere nobody is measuring.
Why AI Makes This Urgent
This is where the argument stops being a governance observation and starts being a timing problem. Organizations are redesigning work around AI at speed, and the question most teams ask is whether a given step can be automated. Morris points out that capability and wisdom are not the same answer. “The technology may be ready to take the next step in the process,” he says. “That alone doesn’t tell you whether it should or what else needs to change around it.” A workflow is a system of dependencies, and removing a node changes the behavior of everything connected to it. Technology tells leaders what can be automated. Execution Visibility helps them understand what changes when they do.
So the sequence matters, and most organizations have it backwards. They are automating against process documentation that describes how work is supposed to happen rather than how it does, which means they are optimizing a fiction. Morris prescribes something deliberately narrow. “Pick one consequential workflow and trace it with the people who do the work,” he says. “Find where the value is created, find where the decisions get stuck. Ask which parts of the work build expertise.” The phrase “with the people who do the work” carries the weight. Nobody above the work can reconstruct it accurately, because the informal judgment that keeps it moving is exactly the part that never made it into a document. Only then does the real decision become available. “Then you can make a more informed call about what to fix, what to automate, and where people still need to exercise judgment.” Three distinct categories, and a leader working from an org chart has no basis for sorting between them.
Execution Visibility does not require leaders to map every task or delay transformation until they understand every dependency. It starts with the workflows that matter most, the decisions that shape outcomes, and the work through which people develop expertise.
For Morris, the question is straightforward: Before changing how work gets done, do leaders understand what they may be changing?
As AI accelerates organizational transformation, that understanding becomes increasingly important. The cost of getting it wrong may not appear in the initial productivity numbers. It may surface later, in broken handoffs, weakened judgment, and capabilities the organization can no longer develop.
Follow Kason Morris on LinkedIn for more insights on execution visibility, workforce transformation, and designing work around AI.
