ART-024
From Experience to Institutional Intuition
Elsewhere I argued that organizations often document more than they remember; that remembering why is selective, owned inheritance; that an organization learns only when future execution changes under replacement; that prediction makes reasoning accountable; and that a serious company should know what it is bad at predicting.
Those habits, if they stick, leave a further question.
What do you call it when experience stops being a private scar and starts behaving like a shared prior—when the institution arrives at the next case already oriented, without needing the original experts to reappear and narrate?
People reach for soft words: culture, judgment, gut. I want a sharper one.
Institutional intuition — not mystique. Governed accumulated judgment.
Intuition without ownership is folklore
In individuals, intuition is compressed experience. A senior engineer “just knows” which dependency class will slip. A revenue-cycle lead “feels” which denial pattern will not reconcile. A change-board veteran “smells” when a clean run streak is still outside the envelope that matters.
That personal compression is real. It is also fragile. When the person leaves, transfers, or gets overloaded, the organization often rebuys the tuition—unless something owned and challengeable transferred with the role.
AI systems create a fluent cousin of the same failure. A long thread “sounds institutional.” Retrieval returns last quarter’s answers. A model proposes the obvious next move with confident tone. None of that is intuition for the organization. It is reconstructed plausibility from whatever happened to be stored.
I am not dismissing expertise, mentoring, or hard-won personal judgment. I am arguing that institutional intuition is a different claim: the next time the same class of work appears, the institution already allocates attention and authority differently—even if different people are in the room.
What institutional intuition actually is
Institutional intuition, as I mean it, is a scoped organizational prior.
It is scoped because it applies to a defined class of situations, not to “how we do everything.” It is organizational because it survives replacement of the humans and tools that first earned it. It is a prior because it changes the starting posture—thicker review here, thinner autonomy there, earlier demotion triggers elsewhere—before the new case is fully investigated.
It is governed because it carries a named owner, linked evidence (including miss patterns and successful promotions), and reconsideration conditions. Yesterday’s earned confidence is not allowed to become unchallengeable dogma when the world moves.
It is not a leadership personality cult. It is not “trust the vibe in the room.” It is not automatic self-optimizing magic that amends production paths without human authority. And it is not a promise that the organization will always be right—only that it will arrive differently, on purpose, with a trail.
Experience compounds only when posture changes
Memory alone is not enough. You can retain assumptions, scars, and reconsideration conditions and still fail to change Monday’s gate. Prediction accountability alone is not enough. You can write claims and still treat misses as private embarrassment. Calibration alone is not enough if the miss register never tightens promotion bars or returns authority.
Experience compounds into institutional intuition when those pieces close:
A recurring miss class stops being a story and becomes an owned prior: in this envelope, we do not treat the path as known. A scar from a brittle payment or payer path travels with the role as a challengeable inheritance, not as hallway lore. A demotion leaves behind not only “we narrowed coverage,” but what evidence would justify re-widening—and who watches for it. A promotion sticks after the expert leaves because the next equivalent case hits a different check, review requirement, or stop condition without requiring the original narrator.
The blunt test is the same one I use for institutional learning. After the loop, does the next equivalent case meet a different institutional posture—without the alumni having to reappear?
If the answer is no, you had experience. You do not yet have institutional intuition.
False substitutes that feel like intuition
Three substitutes show up constantly.
Guru mystique. The organization outsources judgment to a few heroic seniors and calls the dependency “culture.” When they are unavailable, fluency fills the gap—human or AI—and the institution discovers it never owned the prior.
Metric cosplay. Dashboards of activity, coverage, or model confidence are treated as if they were earned orientation. Volume of prior successful runs is used to dismiss a miss pattern that keeps repeating. That is costume confidence, not intuition.
Frozen war stories. Old incidents become permanent slogans—“we tried that”—without assumptions, envelopes, or reconsideration conditions. That is dogma wearing the clothes of experience. Useful institutional intuition stays challengeable.
I am not arguing against senior judgment, metrics, or incident history. I am arguing they become institutional only when they change allocation of scarce attention under ownership and evidence.
Dual inoculations
First: this is not anti-AI and not anti-automation. Institutional intuition often means less scarce intelligence is needed on the next familiar case—because judgment became governed capability—or that intelligence and human authority return quickly when miss patterns say the envelope broke. That is temporal maturity with memory, not a camp position against tools.
Second: this is not a call to buy an “organizational intuition” platform, and it is not a product-architecture shopping list. Most of the raw material already appears in incident reviews, ADRs, CAPA, change boards, and prediction/miss registers—if someone owns the prior instead of closing the ticket and moving on.
Full autonomy without retained human accountability remains the wrong north star. People still decide which priors matter, what evidence earned them, and what signal should force reconsideration.
Coexist with forums you already run
I am not asking for greenfield replacement of the forums you trust, and I am not arguing those forums are insufficient as starting points.
On Monday, institutional intuition can look ordinary. An incident review refuses to close until the miss class updates an owned prior attached to a gate or runbook. A change board keeps short “priors in force” beside stage gates: class, envelope, owner, evidence, reconsideration signal. A standards forum promotes a repeated fix into a deterministic check and verifies the next equivalent change no longer burns the same investigation. A quality or CAPA owner amends an exception class and retires the temporary workaround when the reconsideration signal fires. A release readout treats chronic slips on one dependency surface as an institutional prior about schedule confidence—not only as a one-off apology.
Executives do not need a new category name to ask a better steering question: Where do we already know how to be oriented—and where are we still performing confidence? Headcount of veterans and pages of lore are not substitutes for owned priors under replacement.
A Monday test for institutional intuition
For a consequential class of work that has already hurt you or taught you something expensive:
- What prior does the institution bring into the next equivalent case—thicker review, narrower autonomy, earlier stop, clearer demotion trigger?
- Who owns that prior now, and can a successor find it without interviewing the people who lived the original events?
- What evidence earned it (including miss patterns), and what signal should force reconsideration?
- Are you scoring guru availability, documentation volume, or retrieval hits instead of changed allocation of attention under replacement?
- Where would an assistant invent a fluent “we just know” narrative because answers were stored without posture change?
- If the original experts left tomorrow, would the institution still arrive differently on this class—or only the alumni?
Those questions do not require a product category name. They require an operating habit: convert repeated outcomes into scoped, owned, challengeable priors—and refuse to confuse personal mystique with institutional judgment.
The compounding claim
An organization that develops institutional intuition does not worship gut feel. It accumulates judgment on purpose.
I am not claiming a measured formula for how fast priors should form, and I am not promising that every scar compounds cleanly. I am claiming a direction: stop treating private expertise, fluent reconstruction, and unowned war stories as proof that the institution “just knows.” Ask whether experience changed the next starting posture for the organization.
If experience can compound that way, the remaining open question is how the learning loops fit together—how beliefs, execution, forecasts, and the promotion or demotion of known work reinforce one another as ordinary operating discipline—without turning the question into a product pitch.
