Lesson 0040 · Initiative Lead · Module 1
Facilitate Discovery and Brainstorming
“Get everyone in a room” is not a workshop design. A strong facilitator makes evidence, independent thinking, disagreement, and a decision happen in that order.
Mission tie-in: design quality depends on which options and risks become visible. Facilitation is how a technical lead increases the search space without surrendering the decision.
Knowledge: design the conversation
Unstructured brainstorming rewards the fastest speaker, the highest-ranking person, and the first plausible idea. The group then spends an hour decorating an anchor. For the returns initiative, that anchor is already “portal.” Your job is to make other interventions—policy clarification, proactive status, agent tooling, automated eligibility—available for comparison.
Use a deliberate diamond:
- Frame. Put one decision at the top: “What is the smallest intervention that can cut eligible resolution time during the pilot?” Share the frame and evidence before the session.
- Diverge silently. Each person writes observations, questions, and options alone. Silent first work prevents anchoring and gives design, operations, and quieter engineers equal surface area.
- Make meaning together. Share round-robin, cluster without judging, then name themes. Separate evidence (“38% are unopened domestic items”) from belief (“customers will trust automatic approval”).
- Converge with criteria. Score options against outcome impact, confidence, effort, reversibility, and guardrails. A dot vote may reveal sentiment; it does not make the decision.
- Close. Record the decision, dissent, unknowns, owners, and next evidence. A workshop without a closed loop is a meeting-shaped delay.
| Minutes | Activity | Output |
|---|---|---|
| 0–10 | Read outcome, evidence, constraints; clarify only | Shared decision frame |
| 10–20 | Silent: facts, assumptions, questions | Independent raw material |
| 20–35 | Round-robin share and cluster | Named opportunity themes |
| 35–50 | Silent solution sketches, then combine | At least three real options |
| 50–65 | Score against agreed criteria | Trade-offs and dissent |
| 65–75 | Choose tests, owners, deadline | Discovery actions and decision date |
Map the most consequential assumptions across two axes: impact if false and evidence strength. Test the high-impact, weak-evidence corner first. Label assumptions by risk:
- Value: will the user choose or understand this?
- Usability: can they complete it without assistance?
- Feasibility: can the system and team make it work?
- Viability: can the organization support its policy, cost, and operation?
For returns, “90% of requests match codifiable policy” is high-impact and weakly evidenced. Before designing a rules engine, sample two weeks of agent decisions. “Carrier supports label creation” is evidenced; “carrier returns within two seconds at peak” is not. Different uncertainty deserves different tests.
| Failure | Signal | Facilitator move |
|---|---|---|
| Anchoring | Every option resembles the brief. | Restate the outcome; require three mechanisms. |
| Authority bias | The room waits for the director. | Silent work; leader shares last. |
| False consensus | No disagreement is recorded. | Ask: “What would make this fail?” |
| Workshop theatre | Board full; owners empty. | End with action, owner, evidence, date. |
Skill: choose the facilitation move
Why generate ideas silently first?
Which assumption should be tested first?
A dot vote should determine:
Practice: design the workshop before inviting people
Choose one unresolved initiative decision. Write the decision question, participants and why each is needed, pre-read evidence, divergent prompt, convergence criteria, decider, and the exact closing artifact. If you cannot name the decision, cancel the meeting and find it first.
Reveal: a useful close for the returns session
Direction: test automated eligibility plus proactive status before committing to a full portal. Dissent: support believes guest checkout will dominate. Evidence: analyst samples 200 cases by Tuesday; designer tests policy comprehension with five customers; engineer spikes carrier latency for four hours. Decision date: Thursday. The board is not the output; this paragraph is.
Your win
You can run a discovery session that produces independent options, explicit assumptions, useful dissent, and owned next evidence—not just a wall of notes.
Read and watch deeper
- Gamestorming, Gray, Brown & Macanufo — opening, exploring, and closing a collaborative session.
- Sprint, Knapp, Zeratsky & Kowitz — ch. 2–4: structured divergence, sketching, and decision-making.
- Continuous Discovery Habits, Teresa Torres — assumption testing and the four product-risk categories.
- Reference: Initiative Playbook · workshop script.
Ask your agent-teacher to act as the sceptic in a pre-mortem, then cluster its risks with the team's rather than treating generated ideas as evidence.