The Judgment Reservoir | Shannph Wong

Execution built judgment for free. That subsidy is over. You are preparing for your annual board meeting, and for the first time in three years, you are not sure what story to tell. The numbers are genuinely impressive. The product teams launched three new products this year and cleared a feature backlog that had haunted quarterly reviews for years. The engineering organization shipped more in the last twelve months than in the previous two years combined. The sales team adopted AI-assisted outreach and pipeline management. The go-to-market motion that used to take a quarter to stand up now takes five weeks. Customer support response times dropped by 40%. By every execution metric the board tracks, this was the best year the company has ever had. A year ago, you told the board that the AI investments would drive a 30% gain in revenue growth. You believed it could be even higher, even a 50% gain was within reach. The reason was simple; if we could ship twice as much, move twice as fast, cover twice as much market surface, the results would follow. The teams executed on that logic flawlessly. The actual gain is 6%. In a previous era, you would celebrate that. A 6% acceleration in growth due to a single operational shift would have been made into a case study. But that’s not what you promised, or staffed for, or reorganized around, or what you told your investors to expect. The gap between how much was built and how little impact it actually produced points to something deeper, something you do not yet have language for. What bothers you is not just the number. It is what the year felt like. The place should be buzzing with energy. The pace of shipping alone should have created momentum. People should feel like they are winning. At the last all-hands meeting, you could feel something was off with the energy in that room, in a way you can’t trace to any single thing. Team meetings are productive but feel mechanical. Roadmap reviews surface priorities with sensible rationale, but nobody in the room has conviction about any of it. Decisions get made against options that all seem reasonable enough. You just can’t remember the last time someone pounded the table fighting for an idea they believed in despite the pushback they got in the room. The organization is making sensible choices, but it has stopped making brave ones. You have also lost some key people this year. Not many, but the ones who really mattered. The VP of Engineering had been with the company for over a decade, through the early-stage chaos, through three hard pivots, through a painful rearchitecture and platform migration, through the scaling crises that nearly broke the organization. And each and every time, the company and the team emerged stronger than ever. She resigned in September. She was not burned out from the work. If anything, it was the opposite. She told you she had spent the better part of the past year reviewing AI-assisted proposals, product specs, architectural recommendations, and every one of them seemed good enough; structured, defensible, needing at most a tightened trade-off or flagging a scaling concern. She had dozens of these landing on her calendar every week, each one adding to a growing accumulation of accountability over outcomes she could not really shape. She decided to leave after a product review. The team presented three approaches to an integration architecture required for the strategy to expand to enterprise customers. The proposal was developed heavily with AI assistance, and each option was presented with evaluation criteria documented: integration complexity, migration effort, development effort, maintainability, security posture. The team asked her to weigh in on which direction to take. She looked through all three and knew from her experience that none of them had the extensibility to handle the complexity that the enterprise customers would demand. When she started to explain, the room just asked her which of the evaluation criteria reflected her concern and what data she had that would justify changing the metric. Her feedback did not neatly fit into the specified criteria. She did not have a metric. She had twenty years of building systems that looked just like this and seeing where they broke. The room did not exactly reject her judgment. They added it as a footnote, but then made the decision on the existing criteria and moved on without her. She told you she stopped feeling like a builder and more like the owner of the rubber stamp. She missed the days when the team brought her a hard problem and her job was to see something they could not see. Now they brought her three well-formed options and her job was to vote on one. She was not tired from overwork. She was drained from the slow realization that the system no longer seemed to want what she was best at. It reminded you of something. Years ago, you had watched the same pattern play out in design. Organizations displaced design conviction with A/B testing UX changes. The system produced optimized outcomes but could not produce original ones. The designers who carried the intuition for what a product should feel like eventually left, because the system had no way of using what they knew. At the time, you noted it and moved on. It was a UX design problem. Now the same structural pattern is reproducing itself across your entire organization, and you understand it was never isolated to one department. It was an early warning you did not recognize. Your best senior architect left two months after the VP of Engineering. During his exit conversation, he said something you keep replaying in your mind: “I used to know why we were building what we were building. Not just the business case, the reason behind it. I don’t feel that anymore, and I don’t think anyone else does either.” At the time, you dismissed it as nostalgia. You’re not so sure now. The holes they left behind are larger than their role descriptions. When your VP of Engineering was in the room, she could look at the product approach and tell you in ten minutes whether it would hold together at scale because she had built and rebuilt enough systems to feel structural weakness before she could articulate it. That instinct is not in any documentation she left behind. It is not in the decision frameworks or the review templates. It walked out the door with her. The architect carried something similar. His code reviews were where junior engineers learned what mattered, what was worth fighting over and what was noise. Two of those engineers have told you, separately, that they are shipping faster than ever and yet somehow learning less than they have in years. The sobering realization that stopped you from sending the board deck is that another year of the same approach will not make these results compound beyond the 6%. You can already feel the plateau coming. The first six months of AI adoption produced tangible acceleration. The next six produced refinements on the approach. The gains are real but they are flattening out, and the operational advantage that felt decisive in January has now become table stakes. Two of your closest competitors have closed the gap. One of them, a company you were not even tracking seriously eighteen months ago, has nearly caught up to you. You did everything right. You moved early and boldly. You built real capability, not a headline. Yet here you are, sitting with this board deck draft, aware that the results do not match the effort, that the trajectory is not compounding, and that you cannot explain the gap by pointing to any single decision that was wrong. The people who might have told you why, the ones whose judgment the system had no way to use, are the ones who are no longer in the building. What happened here has an explanation. The organizations that have not yet felt it are on the same trajectory. The question is not if this will happen, but when. When the output metrics show real gains but the business impact does not match, the standard solution stays at the execution level: the tools need tuning, the workflows need refinement, the teams need better prompts or more training. That diagnosis is comforting because the solution is more of the same, done better. It is also insufficient. The deeper problem is not how an organization uses AI. It is what is happening to the people and the systems that do the critical work nobody accounted for. This is the work that AI displaces without replacing. Under the accelerated pace of the AI era, execution scales faster than coherence. Coherence is fundamentally different from alignment. Teams perfectly aligned to their goals can still produce a fragmented result if those goals were ambiguous, or if achieving them at AI-accelerated speed produced side effects nobody designed for. Alignment is about hitting the metric. Coherence is about staying true to the intent. To maintain that, organizations need to deliberately design their decision infrastructure1: clear decision ownership, feedback loops that detect drift from company-wide objectives, and incentives that reward coherence instead of just raw output. That infrastructure is what keeps an organization from breaking apart under its own speed. But even the best decision infrastructure is only as good as the people whose judgment it runs on. Decision infrastructure depends on the quality of people’s judgment. People who can tell the difference between drift that matters and noise that does not. People who know when a correction is urgent and when it is merely reactive. People who can feel that an integration architecture will not hold under enterprise complexity before the data confirms it, or that the adjacent market the product team is expanding into behaves fundamentally differently at scale than the models project. Right now, the need for that kind of judgment is higher than it has ever been, and the existing reservoir is draining. People leave. People burn out. People