Why most frameworks fail (and how to use them anyway)

I have watched a lot of teams adopt a framework, use it earnestly for two quarters, and then quietly abandon it. The frameworks are not the problem. The teams are not the problem. What's wrong is the unspoken expectation that a framework is supposed to give you the answer.

It isn't. A framework is a structured prompt for a conversation. It tells you what to think about, in what order, with what vocabulary. The conversation still has to happen, and the answer still has to come from the people in the room.

What goes wrong

The most common failure pattern: the team picks a framework, fills it in, and stops. The grid is filled. The cells are populated. There is an artifact. The Notion page is "done." Then someone asks what the team is going to do differently as a result of the analysis, and there is silence.

This is the "filled grid, no decision" problem. It's the failure mode of every framework I've ever seen — SWOT, OKRs, RICE, Eisenhower, Premortem, all of them. The artifact gets confused with the outcome. The team feels productive because they completed the framework, but completing the framework was never the point.

The point was supposed to be the conversation that the framework forced — the one where someone said "actually, that threat in the bottom-right quadrant is the only thing that matters, and we should drop quadrant three entirely." That conversation didn't happen because nobody felt obligated to say what the filled grid implied. The grid was treated as the work.

The thing frameworks actually do well

What frameworks are good at is making it socially safe to say the unspoken thing. In a SWOT, the threat quadrant exists, and therefore someone has to fill it. That fact gives an introverted team member permission to write down the threat that everyone has been quietly noticing but nobody has named. Without the framework, the conversation never lands there.

That's the lift. The framework provides a sanctioned slot for the awkward sentence. It moves the awkward sentence from "thing I might bring up if it feels right" to "thing the meeting's structure is asking for." That changes who is willing to say it.

If the team is already willing to say everything, the framework adds nothing. (You will sometimes see very high-trust founding teams skip frameworks entirely. They're not being undisciplined — they don't need the scaffolding, because the conversations they need already happen.)

If the team is reactive, polite, or seniority-bound, the framework can be the difference between a strategy decision and a feel-good meeting.

How to use a framework so it works

Three habits, easy to state and hard to do:

1. Always end the exercise with "so what." When the framework is filled, ask out loud: "given what we just wrote down, what are we going to do differently next week?" If the answer is "nothing," the framework didn't help. That's fine — the failure to reach an action is information. Don't pretend you arrived somewhere you didn't.

2. Time-box the filling and over-allocate the discussing. The most common time allocation is 80% on filling cells, 20% on talking about what the cells mean. Invert it. Fifteen minutes filling, forty-five minutes talking.

3. Re-run. A framework's output is stale in 4–8 weeks. Anyone using a quarterly SWOT in week 11 of the quarter is using a museum piece. Schedule the re-run on the calendar before you put the artifact away.

The other failure mode

The opposite failure: a team uses too many frameworks for too many decisions. Every meeting starts with picking a framework. Every email reply involves a 2×2. This is framework-cosplay — it looks like rigor and it produces nothing.

A framework should appear when a decision is stuck or stakes-dependent enough to warrant the meta-conversation. For routine work, just decide. The cost of a framework is real (60 minutes of three people's attention), and most decisions don't justify it.

The right rule of thumb: if you can defend the choice in two sentences without help, skip the framework. If you can't, that's the signal the framework is earning its overhead.

Why we built this anyway

We have 100+ frameworks in the library. Knowing that most teams will use most of them badly is part of why I think a library matters. The wrong assumption is that the right framework solves the problem; the right assumption is that the right vocabulary makes the conversation possible. A library of vocabulary is what a library of frameworks actually is.

Use them like that and they earn their keep. Use them as answer-vending machines and they will let you down, exactly as you described.

— King Mark

P.S. The framework I reach for most often, by far, is the premortem. It produces actions more reliably than any other. Worth knowing well.