10x Strategy Meeting

Write the framing block in the business's own terms. Name what an incremental version looks like and what a tenfold version would require so the room can see which assumptions constrain the current plan. A group without a Note Taker loses the record. More than one Challenger can shift the balance toward evaluation before the idea is fully formed. Assign additional participants as Idea Generators and state the exception in the packet.

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.

Ask why the business should pursue the outcome before asking how to deliver it. Asking how too early narrows the discussion to what the team already knows how to build. Schedule feasibility for the challenge block, where the Challenger probes scale and asks what would have to be true. Require the facilitator to enforce the sequence regardless of seniority.

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, or role
play. Judge the idea and its rationale, not the polish of the medium.

Rewrite the seven starter questions in the room's product, market,
and customer terms so participants can answer with relevant evidence.

Consolidation introduces provenance risk when the recorder fills gaps that were not in the notes. Use one entry per idea and five fields. Every sentence in every field must trace 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. 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: source notes end here; no further detail recorded

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.

A capture document with no routing table is a brainstorm. Give every captured idea a next decision, an owner for that decision, and a review date. The next step may be evaluate, test, combine, defer, or decline. When the notes name no owner or date, keep Owner needed or Date needed visible. Turning captured ideas into measurable goals or a phased plan is a different job with a different artifact, so the skill names that destination by its exact slug.

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.