Innovation Radar

---
name: innovation-radar
description: Spot emerging practices, business models and operating patterns — not raw technology — that change how value is created in an industry or function, with named practitioners, scored for novelty, adoption momentum and strategic fit. Use when the user asks "how are others doing this differently", "new business models in", "innovation radar", "emerging practices", "who is reinventing X". Stage: sense.
---

# Innovation Radar

A scan, run against the **Innovation Radar** playbook. The steps live in
`../../core/scan.md`; the categories, metrics, sourcing rules and boundary
live in `../../core/playbooks/innovation-radar.md`. Read both before starting, plus
`../../core/envisioning.md` and `../../core/grounding.md`.

**Audience:** Innovation, transformation, business strategy.

## Boundary

This scan needs a **scan scope** — an industry, function, or value chain (e.g. "claims handling in insurance", "B2B SaaS pricing"). Practices with an identifiable practitioner; no management theory.

If the user hasn't stated it, ask for it in one line and wait. If a briefing
exists (`scope` writes one), use its boundary verbatim.

## Run

1. Ground on the boundary — reuse prior cards as the starting corpus.
2. Generate per category, following the playbook's *what counts* line and
   the writing rules in `scan.md`. Assign exactly one category.
3. Merge near-duplicates per the playbook's *merging* line; freeze, don't
   delete.
4. `ground` each card using the playbook's *sourcing* line.
5. Score every card on each playbook metric, comparatively.
6. Persist cards and the scan index per `scan.md` §5.

## Output

The scan index, then one line: `wrote <n> cards + index to <path or folder> · <mode>`.

Example: `/innovation-radar "customer onboarding in retail banking"`