Give a practitioner a clean framework with clear rules and they will follow it precisely, which
is very often the exact moment it stops working. This is one of the least discussed problems in
professional practice, and it becomes more pressing every year that we get better at writing
frameworks down.
Here is the smallest possible example. Air puts out a candle. Air also fans a bonfire. If your
rule is “add air to reduce fire”, you will be right often enough to trust the rule, and then one
day you will add air to something smouldering and produce a considerably larger fire than the
one you were trying to manage.
The rule was not wrong. It was incomplete in a way that only shows up in application.
WHY FRAMEWORKS ARE WRITTEN THE WAY THEY ARE
A framework is a compression. Somebody with years of accumulated judgement writes down the
regularities they have noticed, because the regularities are the transmissible part. What cannot
be compressed is the constant micro-assessment that tells them when the regularity does not
apply, because that assessment is running on information specific to the moment.
So the document that gets handed over contains the pattern and omits the exception-handling,
and the person receiving it has no way of knowing what was left out. They are not being misled.
They have been given the most transferable version of something whose most valuable part is not
very transferable at all.
This is why so many well-trained practitioners are technically correct and ineffective. They are
applying an accurate model to a situation it does not fit, and the model gives them no signal
that this is happening.
WHAT EXPERTS ACTUALLY DO INSTEAD
Watch anybody genuinely skilled at an intervention and you will see the same pattern regardless
of discipline. They apply a small amount. They observe what happened. They adjust.
That loop is the competence. Not the size of the intervention and not the elegance of the model,
but the rate at which they check reality and correct. An experienced practitioner running a
crude model with a tight feedback loop will outperform a novice running an excellent model
without one, every time.
The consequence for anybody learning is uncomfortable. The framework you were taught is the
scaffolding, not the building. It gets you to the point where you can start observing usefully.
The years after that are spent finding out where it does not apply, which is knowledge you can
only acquire by being wrong in specific, correctable ways.
WHAT CHANGES WHEN YOU WORK THIS WAY
Small interventions become the default
If you know the model is incomplete, you stop making large moves based on it. You do the
smallest version, see what happened, and go again. This is slower per step and dramatically
faster overall, because the alternative is a large confident intervention followed by an
expensive correction.
Being wrong becomes information rather than failure
A practitioner who expects the model to be right experiences a mismatch as a personal or
professional failure. A practitioner who expects the model to be incomplete experiences the same
mismatch as the most valuable thing that happened all week, because that is where the
exception-handling gets built.
You get more careful about what you teach
Anybody writing up their own methodology should be uneasy about how confident it reads. The
document will be applied by people without your judgement, and the cleaner it looks the more
mechanically it will be followed. Some of the best practitioner documents I have seen include
explicit notes on where the model breaks, which is rare and worth copying.
THE THING THAT ACTUALLY TRANSFERS
Everybody wants the table. The table is genuinely useful and it is where you have to start,
because you cannot observe intelligently without a frame to observe against.
But the table is not the skill. The skill is the loop, and the loop is unglamorous, slow to
build, and almost impossible to sell, which is presumably why so much training stops at the
table and calls it a qualification.
If a method appears to work every time you apply it, the most likely explanation is not that
you have found an exceptional method. It is that nobody is checking closely.



