Scrolls
3 min read
On this page

Choosing a Framework

With dozens of communication frameworks in circulation, the meta-problem is knowing which one to use. This subtopic offers decision heuristics for picking the right framework based on the situation at hand. The goal is not to memorize every framework, but to recognize which one fits the problem in front of you.

Why This Matters

Applying the wrong framework is often worse than applying no framework at all. Using SBI for a strategic influence campaign is awkward. Using RACI for a two-person conversation is absurd. Using the Hero's Journey for a status update wastes everyone's time. Matching the framework to the situation is the core skill.

The Selection Dimensions

Use these four dimensions to pick a framework:

1. Direction:    One-way (broadcast) vs. two-way (dialogue) vs. group
2. Synchrony:    Async (written) vs. sync (spoken)
3. Stakes:       Low (routine) vs. medium (consequential) vs. high (existential)
4. Purpose:      Inform / Decide / Influence / Resolve / Coach

Different combinations point to different framework families.

Decision Table

| Situation                           | Reach for...                         |
|-------------------------------------|--------------------------------------|
| Writing an email or memo            | BLUF, Minto Pyramid                  |
| Proposing a technical change        | ADR, RFC, Design Doc                 |
| Pitching an idea to leadership      | Amazon 6-pager, PR/FAQ, SCQA         |
| Assigning responsibility            | RACI, DACI, DRI                      |
| Making a high-stakes decision       | RAPID, DACI                          |
| Giving feedback                     | SBI, CEDAR, COIN                     |
| Navigating conflict                 | Crucial Conversations, DESC          |
| Breaking an impasse                 | Ladder of Inference                  |
| Negotiating                         | BATNA/ZOPA                           |
| Persuading stakeholders             | Cialdini, SPIN, Ethos/Pathos/Logos   |
| Running a retro                     | Start/Stop/Continue, 5 Whys          |
| De-risking a project                | Pre-mortem                           |
| Coaching a report                   | GROW, Situational Leadership         |
| Presenting to an audience           | Duarte Sparkline, Pixar Story Spine  |
| Designing org communication         | Conway's Law, Team Topologies        |

Meta-Heuristics

Beyond the table, a few rules of thumb help:

Match the Stakes to the Structure

Low-stakes communication needs little structure. High-stakes communication needs a lot. Over-structuring a casual message feels robotic; under-structuring a critical one feels careless.

Low stakes  -> No framework needed, be casual
Med stakes  -> Single framework (BLUF, SBI, etc.)
High stakes -> Multiple frameworks stacked (AIM + Minto + Cialdini)

Pick for the Hardest Constraint

If the audience has 2 minutes, optimize for brevity (BLUF). If the audience is skeptical, optimize for persuasion (Ethos/Pathos/Logos). If the audience is emotional, optimize for empathy (NVC-inspired approaches). The hardest constraint dictates the framework.

Written Beats Spoken for Complex Decisions

For anything involving nuance, trade-offs, or permanent record, default to written frameworks (RFC, ADR, 6-pager). Verbal discussion is for alignment and Q&A, not for the decision itself.

Use Frameworks as Scaffolding, Not Cages

Frameworks are guides, not scripts. A SBI feedback delivery that reads like a form letter is worse than an unstructured but honest conversation. Use the framework to ensure you covered the bases, then deliver in your own voice.

Tech & Company Example

A staff engineer needs to convince the platform team to adopt a new observability tool.

Situation analysis:
  Direction:  One-to-many, dialogue expected
  Synchrony:  Async primary (written RFC), sync follow-up (review meeting)
  Stakes:     Medium-high (tool decision affects 20+ engineers for 2+ years)
  Purpose:    Influence + Decide

Framework stack:
  1. AIM to clarify intent (get RFC approval in 2 weeks)
  2. RFC format for the document structure
  3. Minto Pyramid for the executive summary section
  4. Cialdini's principles (social proof, consistency) for stakeholder sections
  5. Pre-mortem in the risks section
  6. DACI for decision owner/approver clarity

Using a stack of frameworks, each for the right sub-problem, is much more effective than forcing one framework to do everything.

Common Failure Modes

  • Framework worship — treating the framework as the goal rather than the means
  • Wrong granularity — using a heavyweight framework for a lightweight situation
  • Framework collision — stacking frameworks that conflict (e.g., BLUF and narrative storytelling for the same audience section)
  • Framework amnesia — knowing a framework exists but not applying it under pressure
  • Over-theorizing — spending 30 minutes picking a framework to avoid writing the thing

When to Skip Frameworks Entirely

  • One-line replies ("yes, ship it", "thanks, on it")
  • Informal chat with a trusted peer
  • Raw brainstorming or early-stage exploration
  • When the framework feels more disruptive than helpful — your instinct is a signal

Further Reading

  • Bent Flyvbjerg — How Big Things Get Done (on picking mental models for projects)
  • Shane Parrish — The Great Mental Models series (general framework selection)
  • This repo's topic READMEs — each lists when to reach for that category