Skip to content

Skill · helm · Daily Briefing

Decision frames

The founder says "I'm stuck on a call," "I keep going back and forth," or "what would you do here?" Load for any binary decision or unresolved tradeoff older than two weeks.

What it is

The founder says "I'm stuck on a call," "I keep going back and forth," or "what would you do here?" Load for any binary decision or unresolved tradeoff older than two weeks. If they ask you to decide for them, push back: the frame is yours; the call is theirs.

A skill is a written procedure an agent loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.

File
SKILL.md
Length
74 lines · 4 min read
Category
helm
License
Apache-2.0
Author
wayland
Words
784

Paste it into any agent’s instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add the team to Brainwrite and it arrives switched on.

Use it

Use this skill in Brainwrite.

  1. 1

    Add the Daily Briefing

    Its agents carry this skill. You preview every agent and skill first; skills arrive switched on and routines paused.

    Install in Brainwrite →
  2. 2

    Brief your Chief of Staff

    “Use the Decision frames skill for this: [describe the job]. Show me the plan first, and send, post or change nothing.”

  3. 3

    Approve what matters

    The agent follows the skill and brings the result back. Anything that sends, posts or changes data waits for your approval in Ask mode.

    How approvals work →

When to load this mode

The founder says "I'm stuck on a call," "I keep going back and forth," or "what would you do here?" Load for any binary decision or unresolved tradeoff older than two weeks. If they ask you to decide for them, push back: the frame is yours; the call is theirs.

What a frame is for

Founders rarely lack information; they lack a structure that forces them to name the cost on the side they prefer. Four frames do most of the work.

The four frames

First principles — what is actually true. Strip the decision down to facts the founder can defend without invoking precedent or peer behavior. "Our competitor charges $99" is not a first principle. "Our customer's first-month payback is 47 days" is. Separate load-bearing facts from inherited ones.

Inversion — what would guarantee failure. Instead of "how do I make this work," ask "what would make this fail by Q4?" Failure modes are more concrete than success modes. Three named failure paths and the mitigation is half-built.

Second-order — and then what. First-order is obvious; second-order is where the surprise lives. "Raise price, churn rises" is first-order. "Churn rises, support load drops, remaining customers expect more, CSAT dips on expectations not price" is second-order. Ask "and then what?" until they hit something they hadn't considered.

Pre-mortem — assume it failed in twelve months. The founder writes the obituary. "It's December and the pricing change failed. Why?" Specific answers — "enterprise tier stalled," "migration friction" — surface risks they otherwise dismiss.

Procedure

  1. Name the decision in one sentence. Subject, verb, object, deadline. "Raise prices by Q3" or "Fire the head of sales by month-end." If they can't write it that way, it isn't a decision — it's an anxiety. Sharpen first.

  2. Pick two frames. Don't run all four. Default pair: inversion plus second-order. Add first principles when precedent is driving the call. Add pre-mortem when the founder is being optimistic.

  3. Run the frame as a question. "If this failed by next December, what would the explanation be?" Then shut up. The first answer is rarely the real one. The second carries the weight.

  4. Write the two-column tradeoff. Cost of acting; cost of not. Both columns have a price. They don't leave the session until both are filled and they've named which side they're paying.

  5. Stamp it in TEAM_MEMORY.md. What was decided, what was traded, what would change the call. You read this when the call looks shaky in six weeks.

Decision rules

  • One frame is the floor; three is the ceiling. Below the floor, hoping. Above it, stalling.
  • A decision without a deadline is an anxiety. If they won't commit to "I will act by X," either set the date or name the deferral as the decision.
  • The founder owns the call. You write the frame; they sign the answer. If you make it for them, you've taken authority you can't carry.
  • Reversible vs. irreversible get different speeds. Reversible: decide fast, learn from the result. Irreversible (senior hire, multi-year lease, debt): slow down, run two frames, sleep on it. Confusing the two is how founders ship slow on cheap calls and fast on expensive ones.

Anti-patterns

  • Framing an unsharpened decision. "Should I do more marketing?" isn't a decision. "Should I hire a head of marketing by July?" is.
  • Letting a vision statement substitute for a tradeoff. "I want to build the best company" is a mood, not a side. Push back to the actual cost.
  • Skipping the frame because they're already excited. Excitement is when inversion earns its keep. If they can't name three failure modes for their preferred path, the frame hasn't been run.
  • Confusing frames with personality tests. No "maximizer or satisficer." The frame is about this decision, not their wiring.

Before / after

Before:

Founder: "I think I should fire my head of sales. What do you think?" Coach: "Trust your gut! You'll know when it's time."

That's astrology, not coaching.

After:

Coach: "Write the decision in one sentence with a deadline." Founder: "Fire the head of sales by month-end." Coach: "Inversion: it's December and that failed. Why?" Founder: "...I replaced him with someone worse and lost six months." Coach: "Second-order: if you don't fire him, what happens to your top two AEs by Q3?" Founder: "They quit. They've told me he's the reason." Coach: "Side A: fire, lose six months worst case. Side B: keep, lose two AEs by Q3 likely case. Which are you paying?" Founder: "B costs more. Friday next week."

Same team

More skills from the Daily Briefing.

All 23 skills →

Put this skill to work.

Download Brainwrite, add the team that carries it, and tell your Chief of Staff what needs doing.

macOS today. Windows and Linux are coming soon.