GoKawiilA project can be obviously important, technically sound, budgeted, and still go nowhere. I don’t mean slowness. I mean the weird kind of stalled where everyone involved can point to work, meetings, approvals, and progress, yet nothing actually moves.
I no longer start by asking whether the team lacked skill or effort. A lot of the time, the problem is much less flattering to the organization than that. They were using the wrong map or they didn’t know they needed a map.
The constraint map is the org chart. It shows who manages whom, who owns the budget, and who carries formal accountability when something blows up. That is useful. It still does not tell you how work actually moves.
Execution runs through other maps: expertise, trust, memory, and influence. When those line up with the org chart, the place feels sane. When they do not, you get friction, phantom vetoes, repeated mistakes, and people reading performance through the wrong lens.
The Five Maps Behind Execution
The expertise map says who people actually ask when the system gets into trouble. In a healthy company, you can usually find the right expert without too much pain. In a messy one, expertise is locally visible and globally hidden. One team knows who their person is. Another team has no idea that person exists.
This one causes some of the ugliest confusion because it looks like approval on paper but behaves like politics in practice. In some rooms, the person with the most actual power says the least. Everyone else just glances at them before landing the plane.
If you push work through the formal line without securing the real buy-in path first, the initiative will stall, get revisited, die in committee, or get vetoed for reasons nobody can explain in one sentence.
I remember a time where one of the sibling orgs had a no-deploy rule on Fridays. No exceptions, no escalation path, just a hard stop. I remember thinking it was overcautious the first time I ran into it. We needed them to deploy a fix. It was small. The weekend was two days of unnecessary exposure. I pushed back and someone older than me in the org said no, flatly, and didn't explain it.
Six months later I found out why. A Friday deploy eighteen months before I joined had taken down an integration over a long weekend. The oncall engineer was unreachable. The person who understood that part of the system was at a wedding with no signal. By Monday they had lost three days of integration volume. The rule was the memory.
... continue reading