The senior biller who knows that this payer always flags that code pair. The category manager who knows this supplier only moves when volume visibly moves. The marketer who can smell creative fatigue a week before the numbers admit it. Ask where that knowledge is stored and you'll get the honest answer: in them.
That's the most valuable operating asset most companies own, and it's held in the least durable format available — tenure.
Why writing it down hasn't worked
The traditional fix is documentation: playbooks, wikis, standard operating procedures. And everyone knows what happens next — they rot. Not because people are lazy, but because a rule separated from its decision is trivia. Stripped of context, "always check the code pair" sits in a wiki with no way to fire at the right moment, nothing to weigh itself against, and no feedback on whether it's still true.
Rules don't rot inside a decision
Put the same rule inside the decision it belongs to and everything changes. In the claim decision, "never submit a known code-pair mismatch" isn't a wiki line — it's a working part. It fires exactly when a claim carries that risk. It's weighed against the submission deadline and the appeal economics. And every cycle, the outcome quietly tests it.
That's the difference between judgment that is archived and judgment that is employed. One is a document. The other shows up for work.
Sharper, not just saved
Documentation freezes judgment at the moment of writing. A rule running inside a decision keeps learning: the fatigue threshold turns out to be frequency 6, so the next campaign rotates creative at 5. The counter-offer that worked becomes the opening position next quarter. Thresholds move with evidence, not anecdote — and the tenth cycle of the decision is measurably sharper than the first.
The people question, answered honestly
None of this replaces the senior people. It promotes their judgment from tribal memory to infrastructure — which frees them for the calls that are genuinely novel, the ones no rule should touch. And it changes what joining the team means: a new hire inherits the tenth-cycle version of the playbook on day one, instead of spending two years reconstructing it by osmosis.
The judgment already exists. You've already paid for it — in tenure, in tuition, in the mistakes that taught it. The only open question is whether it stays a person or becomes an asset. The way to find out is small: start with the one decision that leans on one person hardest.