Halo Alert Demonstration

Worked examples that show the expeditionary method in action

Start here: Halo Alert at a Glance puts the whole expedition, twenty-nine days from ten candidate communities to one validated pain, on a single page. Everything that follows is the working record behind it.

Purpose of this Demo Part

This book teaches a repeatable process for reducing uncertainty and finding unmet needs.
The Halo Alert demos show what that process looks like when it is written down: field notes, interview transcripts, observation logs, clustering, hypotheses, and confirmatory tests, complete enough that you can trace every step and reuse the same tools on your own project.

  • Narrative + How-to: Every method chapter in the book explains why and how.
    These demos show what it looks like when a real team does the work.

  • Linkable & modular: Each demo stands alone, and chapters link back to the relevant toolkit guides (templates, checklists, prompts).

  • Right level of detail: Brief vignettes for quick ideas; full transcripts where depth helps (e.g., conversations).

What Halo Alert Is, and Where It Came From

Halo Alert is a personal-safety concept for women who walk as part of their commute, including professionals and university students. It explores discreet, low-friction ways to stay connected: a subtle trigger that signals I need you watching me now, without escalating a situation or visibly reaching for a phone.

The concept and much of the framing come from a real innovation project that never shipped. The idea was promising, and it had been tested: the team ran solution tests with real customers, including a wow-factor test and a $100 test. What they could not do was work together. The innovation died on the drawing board and the bench rather than in the market, and no test ever found it wanting.

That failure is why Organize for Innovation exists, and why this book treats psychological safety as a condition of the method rather than a courtesy. A team that cannot suspend judgment cannot diverge, and a team that cannot disagree safely will converge on whatever the loudest person already wanted.

Where the evidence on these pages came from

The original project’s artifacts are gone. Everything you will read here, the transcripts and the observation logs and the counts, was reconstructed, written with an AI so the record would be complete enough to follow end to end.

That makes these pages illustrative of form rather than evidence of fact. They show what a good conversation record looks like, how a clustering board is laid out, what a pain test reports and how its three probes can disagree. They do not establish that any particular claim about commuters is true.

And notice what that means for you, because it is the opposite of what it might seem to license. Doing this with your own project would break the method. This demo may generate a record, because its job is to show you the shape of one. Yours may not, because yours has to be the evidence — which is the one prohibited act in the standing orders.

One artifact is genuine. The screening matrix in Hypothesize a Good Solution is the original team’s own, recovered from course files because it happened to have been built in software that kept a copy. Its ideas, its reference solution and its ratings are theirs.

Two further notes. The setting is New York and the original work was not; a dense transit city makes a walking commute legible to readers anywhere, so it was chosen rather than reported. And Diamond 3 here is reconstructed rather than recorded: the original team did diverge, converge, and test, but this method did not exist in this form when they worked, most of their artifacts are gone, and they never reached the later market-facing tests.

How to Use These Demos

  1. Read the appropriate narrative chapter first (e.g., Explore the Community, Hypothesize a Pain…).
  2. Skim the matching toolkit guide for the method (template + checklist).
  3. Open the corresponding Halo Alert demo to see the method applied (design → execution → evidence → learning → next steps).

Keep your own data room in parallel: copy the templates, adapt the guides, and mirror the demo structure (file naming, links, and cross-refs).

What’s Included

Halo Alert at a Glance lists every file with its date and what it produced. Rather than repeat that here, two notes about scope:

Diamonds 1 and 2 are complete: divergence, the access test, two full conversation transcripts, three observation outings, clustering, personas, the experience map, abduction, and three pain-test probes with their raw responses.

Diamond 3 runs as far as the original project did: generation, screening against the women’s own requirements, and two solution tests. It stops before the smoke test, because that is where the team stopped and because a landing page shown as screenshots is not a landing page. Explorable smoke-test examples are being prepared separately.

New files follow exp-XX-[modality]-[short-label]-YYYY-MM-DD.qmd, lowercase with dashes, with a readable title set inside the file.

Conventions & Reuse

  • Structure: Every record here follows the same six sections — Unknown → Design → Execution → Evidence → Knowledge update → Next steps — which is the shape the toolkit describes. Copy it; the order is what stops you writing the conclusion first.
  • IDs & Links: Use stable anchors (e.g., #sec-conversation-guide) for cross-refs from narrative chapters.
  • File naming: exp-XX-[modality]-[short-label]-YYYY-MM-DD.qmd (sortable, human-readable).

Ethics & Privacy

  • Pseudonyms are used and personally identifying details are removed or altered.
  • Public-space observations avoid facial features and identifying markers; private locations require permission.
  • Do no harm: Avoid interventions that could escalate risk; prefer reassurance over confrontation.
  • Consent: For recorded conversations, obtain explicit permission and state your non-sales intent.

How These Demos Connect to the Toolkit

Every demo ties to at least one guide:

The intent is traceability: a reader can jump from a technique in the narrative → to a guide → to a concrete Halo Alert example → and back to their own data room with the same template.

What to Look For (Learning Lenses)

  • Signals of unmet need: friction, workaround, anxiety, surprise, “I wish…”
  • Moderators: lighting, crowd density, time of day, route familiarity
  • Reassurance patterns: connection rituals (texts/ETAs), discreet triggers, route choices
  • Decision rules: how each experiment updates beliefs and points to the next test

License & Attribution

This demo content follows the book’s license, CC BY-NC 4.0.
Teaching use, adaptation and translation are expressly permitted for non-commercial purposes. Please attribute Before You Build — Halo Alert Demos and retain the license notice.