Frameworks should serve leaders — not the reverse.

There is a particular moment every leader who opens a governance framework experiences. Page one promises clarity. Page forty introduces the third layered model. By page one hundred, you are learning a vocabulary in order to read the vocabulary. Somewhere along the way, a quiet inversion happened: you stopped using the framework, and started serving it.

Let's be fair to the frameworks. The thinking inside the world's established governance and skills references is genuinely excellent — decades of hard-won lessons about who should own which decisions, how to measure what matters, and how capability actually develops in organizations. These are not academic exercises. They describe how the best-run IT organizations on earth actually operate.

Written for enterprises with armies

But read the fine print of their assumptions. They assume a governance office. They assume analysts to tailor the model, consultants to run the assessment, and a program office to maintain the binder. They assume, in short, an army — because they were written by and for organizations that have one.

A three-hundred-person company has no army. It has a leadership team with day jobs. Handed an enterprise framework, that team faces a false choice: ignore the accumulated wisdom entirely, or sacrifice a year of attention learning to operate it. Most choose a third path — buy the binder, hold the workshop, and quietly shelve the results. The framework wins. The organization loses.

The translation, not the doctrine

The answer is not simpler frameworks. Simplified wisdom is usually just wisdom removed. The answer is translation: keep the substance — the objectives, the priorities, the skill levels — and remove the ceremony. Ask the leader plain questions about their organization. Do the mapping quietly, in the background, the way a good advisor does. Return an answer scored for this organization, not a curriculum about all organizations.

That is the test of a framework being on your side: you never have to learn its name to benefit from its judgment. The instrument disappears into the work. What remains is direction you can defend — and revise — without an army standing behind you.

Frameworks are staff, not sovereigns. Hire them accordingly.