Run your first Loop with operational clarity.

Set conditions before activation.

Most pilots fail before they start. A clean setup creates the room for honest learning.

1. 01CHECK

   Define challenge scope

   One question, one timeframe, one observable outcome. Narrow beats ambitious.

2. 02CHECK

   Recruit participants

   Mix builders, operators, domain holders. Cap at 12 for a first Loop.

3. 03CHECK

   Identify facilitators

   One lead facilitator per cohort. One observer per group when possible.

4. 04CHECK

   Prepare spaces

   Wall surface, movable furniture, no stage. Optimize for ground-level work.

5. 05CHECK

   Prepare evidence templates

   Reflection sheets, evidence logs, signal capture. Print before you start.

6. 06CHECK

   Define timing

   Choose a 4h Loop, Buildathlon (8h), 5-day Challenge or 12-week Program. Lock it.

7. 07CHECK

   Align ethics expectations

   Consent, opt-in visibility, participant ownership of evidence. State it out loud.

8. 08CHECK

   Set your impact baseline

   Before the sprint starts, identify one societal or environmental dimension your venture touches. Not a constraint - a lens.

An operational sequence, not a workshop.

Each stage produces evidence. Each transition is a decision moment.

1. T+0

   Kickoff

   Frame the protocol. Set ethics. Distribute evidence templates. 30 min max.

2. T+1

   Signal discovery

   Capture real signals from the field, not assumptions. Document sources.

3. T+2

   Framing

   Convert signals into a testable proposition. One sentence, one user, one outcome.

4. T+3

   Build sprint

   Ship the smallest demonstrable artefact. No slide decks at this stage.

5. T+4

   Testing

   Expose the artefact to real people. Capture reactions, not opinions.

6. T+5

   Evidence review

   Sort what was learned vs what was performed. Discard theatre.

7. T+6

   Reflection

   Each builder writes their own learning, in their own words. Operators do the same.

8. T+7

   Closing loop

   Decide: continue, pivot, drop. Record the decision and its evidence base.

9. T+8

   Impact checkpoint

   At mid-sprint: does the direction taken create or destroy value beyond the customer? Flag it. Don't solve it. Just name it.

What collapses a pilot.

These patterns predict failure. Name them out loud and they lose power.

• ⚠ M.01

  Endless brainstorming

  Ideas inflate, evidence stalls. Cap ideation. Move to artefact.

• ⚠ M.02

  Premature building

  Code before signal. The team builds confidently in the wrong direction.

• ⚠ M.03

  Fake customer validation

  Friends, classmates, sponsors. Not signal. Engineer real exposure.

• ⚠ M.04

  Mentor overreach

  Mentors decide. Builders comply. Authority replaces evidence.

• ⚠ M.05

  Pitch obsession

  Polishing narrative instead of testing reality. Ban decks during the Loop.

• ⚠ M.06

  Performative startup culture

  Theatre wins applause and kills learning. Reward evidence, not energy.

Choose a format, then run it cleanly.

Four standard formats. Pick one. Do not blend them on a first pilot.

1. 4h Loop

   Discovery sprint

   Signal → frame → micro-test. Best for first exposure to the protocol.

2. Buildathlon (8h)

   Compressed cycle

   Full Signal-to-Decide cycle in a single day. Operator-led pace.

3. 5-day Challenge

   Field challenge

   Real users, real builds, real evidence. The default ecosystem format.

4. 12-week Program

   Founder emergence

   Multiple Loops chained. Evidence compounds. Operators rotate roles.