FREESKILL v1.0UPDATED 2026-08

10x Strategy Meeting

Ten percent thinking takes the path everyone else is already on. This playbook runs a session that asks for an order of magnitude instead, splits the room into threes with a role each, keeps feasibility out of the generation block, and ends with every idea routed to a person and a date. Run it here, then install it where you actually plan.

A planning session that opens with how tends to end where it started. The most senior person asks how would that work, the room prices the idea against what it already knows how to build, and the output is another increment on the thing already running. That is not a failure of imagination. It is a failure of sequence.

A 10x session fixes the sequence. Generation asks only why the business should reach a tenfold outcome, and the feasibility question waits for its own block. Groups of three carry an Idea Generator, a Challenger, and a Note Taker, so the person whose job is to probe an idea is not the same person whose job is to have one. What comes out is not a plan. It is a captured set of ideas, each with the reason it matters, each pointed at an owner.

An idea nobody wrote the why for does not survive the week.

SIGNALS YOU NEED THIS

Every plan lands within a few percent of last year, and the ceiling is described as the market rather than as a choice.

Ideation dies in the first ten minutes because somebody asks how it would be staffed.

The session felt great and produced nothing anyone can point to a month later.

REPLACES

Brainstorms that end in a photo of a whiteboard, planning cycles that only ever compound the existing funnel, and the idea that got applause and no owner.

PAIRS WITH

Business Goals, Prioritization Formula, and How to Plan New Product & Services.

0 of 4 steps complete

STEP 01Frame the contrast, then design the room

The framing block earns its minutes, and it has to be written in the business's own terms. Naming what a ten percent version looks like, then what a tenfold version would have to be, is what stops the room from answering with the thing it already planned. Groups are threes with all three roles, because a group without a Note Taker produces energy and nothing else, and a second Challenger ends generation early. Attendee counts rarely divide by three, so the remainder is handled out loud: extra people become extra Idea Generators, never extra Challengers.

THE FRAMING BLOCK names a droppable assumption
  Ten percent looks like:   one more van, a wider service radius
  Tenfold would have to be: ten times the customers served
  Drop the assumption that: growth means more of the same work

THREE ROLES PER GROUP, and the group is three people
  Idea Generator   proposes; does not self-censor for feasibility
  Challenger       asks what would have to be true, never that
                   will not work; silent until the challenge block
  Note Taker       records the why alongside the what

A remainder is split visibly, e.g. 11 people, two groups of 4 and
one group of 3, with the groups of 4 carrying two Idea Generators.
No group is left without a Note Taker; if one is, the packet says
Note Taker needed before the session starts.

STEP 02Why, not how

This is the rule the whole format exists to protect. The session asks why we should get there and never how we would get there, because how-thinking collapses the idea space to what the team already knows how to build. That is exactly the ten percent path the session is trying to escape. Feasibility is not banned, it is scheduled: it belongs to the challenge block, where the Challenger probes scale and asks what would have to be true. The facilitator owns the interruption regardless of who makes it, which matters because the person most likely to ask how is the person nobody interrupts.

THE FIVE BLOCKS, scaled to the slot you actually have
  1. Framing and rules        10x not 10 percent, why-not-how
  2. Group ideation           groups work the starter questions
  3. Present back             the what and the why, any medium
  4. Challenge and build      feasibility and scale, building
  5. Capture and route        consolidate; owner names next step

Block minutes are fractions of the slot supplied, and they sum to
it. No canonical session length is ever asserted.

PRESENT BACK ACCEPTS ANY MEDIUM: text, a sketch, a diagram, role
play. The medium rule keeps polish from becoming a filter. A
sketch presented with conviction beats a deck.

The seven starter questions are rewritten in the room's own
product, market, and customer terms. Generic questions produce
generic ideas, and a room answers a generic question with what it
already believes.

STEP 03Capture what the room said, and only that

Consolidation is where a good session quietly becomes fiction. One entry per idea, five fields, and every sentence in every field traces to something the notes record. A gap in one field never backfills another: when the notes carry no why, the why reads Not recorded, and the missing reason does not reappear as a paragraph of reasoning inside the discussion field. Hedging does not help. An inference labeled as inferred is still content nobody in the room said. The only substitute for missing content is the gap label.

FIVE FIELDS PER IDEA, and the labels are the honest ones
  What              the idea as the group presented it
  Why               the case for it, or Not recorded
  Discussion points what was raised, or None noted
  Scale check       per the room, or Not discussed
  Data check        data named, or Data needed

A BARE WHAT STAYS A BARE WHAT
  Notes say: "partner with home builders?? something about
  install day. rest of the page is missing"
  Captured as:
    What: a partnership with home builders, tied to install day
    Why: Not recorded
    Discussion points: the page cuts off; nothing further survived

TEN PERCENT CREEP IS LABELED, never dropped and never dressed up.
An idea that optimizes the existing funnel is kept and marked
incremental. It may be a good idea in a different meeting.

STEP 04Route every idea to a person and a date

A capture document with no routing table is a brainstorm. Every idea gets a next step, an owner, and a date, and where the notes name none the field carries Owner needed or Date needed in plain sight rather than a guessed name. A guessed owner is worse than a blank one, because it looks resolved. Turning the captured ideas into measurable goals or a phased plan is a different job with a different artifact, and the skill names that destination by its exact slug rather than paraphrasing it, because a paraphrase reads like a handoff without being one.

THE ROUTING TABLE closes the session
| Idea | Next step | Owner | By when |

Every row is filled. Where the notes named nobody:
  Owner needed        not a plausible name from the room
  Date needed         not a guessed quarter

WHAT THIS SKILL HANDS OFF, by slug
  business-goals                        measurable goals
  how-to-plan-new-product-and-services  a phased plan
  prioritization-formula                scoring and ranking

The reply is the artifact and nothing else. It begins at the
capture title line and ends at the routing table's final row: no
preamble, no closing summary, no count of the gaps it labeled.
In-place labels are part of the artifact and stay.

The skill is a folder, not a service. It runs where your work runs, works only from what you give it, and never fetches anything remote.

skills/10x-strategy-meeting

10x-strategy-meeting/
├── SKILL.md                          ← the two modes + the delivery boundary
├── meta.yaml                         ← version, sources, test prompts, changelog
├── LICENSE.md                        ← MIT
├── assets/
│   ├── capture-template.md           ← one entry per idea + the routing table
│   └── session-packet-template.md    ← the packet the owner sends to the room
└── references/
    └── facilitation-notes.md         ← roles, why-not-how, failure modes

INVOKE IT LIKE THIS

"Use the 10x-strategy-meeting skill to prep a 10x strategy session for my team."

Download skill v1.0 View source on GitHub

WORKS WITHClaude Code