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.
The leadership force is widening the search space without giving away the decision. Those two halves fail in opposite directions — a lead who decides alone searches a space of one, and a lead who lets the room decide gets the option with the least resistance rather than the most merit — and every move in this lesson exists to hold both at once.
The mechanism behind silent divergence is mundane and reliable. In a talking group only one person speaks at a time, so contributions queue; and each contribution after the first is conditioned on what was already said. The result is that a room of eight does not produce eight independent samples of the solution space, it produces something closer to one sample with seven elaborations. Silence restores independence, which is the only thing that makes the group larger than its loudest member.
Convergence has its own mechanism: criteria chosen before the options are visible. Criteria chosen afterwards are selected, unconsciously and honestly, to favour the option someone already likes. And the decision needs a named owner, because consensus-seeking has two exits and both are bad — the lowest-common-denominator option, or a silent dissenter whose objection reappears as an implementation surprise in week six.
The boundaries: this machinery assumes shared context. A group that does not know the domain will silently generate confident nonsense, so a pre-read or a facts round has to come first. And it assumes the decision is genuinely open. Running divergence on a question that is already settled is not facilitation; it is theatre, and it spends the trust you will need on the next real one.
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 |
Worked: choosing the test that could change the decision
The room's strongest belief is that "90% of returns match codifiable policy". Everyone nods; support's most experienced agent said it, and it sounds right. It is the assumption the whole automated-eligibility option rests on, and it has no evidence behind it at all.
The first thing an experienced facilitator does with a belief like that is not to argue with it. It is to ask what decision would change if it were false — and then to size the cheapest test that could distinguish the two worlds. Sampling 200 recent agent decisions takes an analyst about a day. If the true rate really is near 90%, a sample of 200 pins it to roughly ±4 percentage points at 95% confidence, so the answer comes back as a range like "86–94%".
Now put that beside the frame from lesson 0039. The manual review queue is capped at 50 cases a day and the pilot cohort is about 1,140 returns a day, so automation must decide at least 95.6% of them without a human. A measured 86–94% does not merely fail to confirm the plan — it refutes it, decisively, for one analyst-day. That is what a well-chosen test looks like: not "learn more about returns", but "a result that forces a different design".
And the design does change, in a way the workshop can now discuss with something real on the table: narrow the cohort until the exception volume fits the cap, or add an agent-assist path that clears exceptions faster than a full manual review, or renegotiate the guardrail with the operations lead who set it. Three options, all defensible, none of them available while the assumption was still a nod.
The alternative the lead rejects is the impressive one: a five-day design sprint, next week, to produce a prototype of the portal. It spends the most expensive week of the initiative decorating an option whose feasibility is unknown, and at the end of it the same unmeasured 90% is still holding up the whole structure. The other rejected move is quieter and more common: accepting the anecdote because it came from the most senior person in the room, which converts the highest-status guess into the initiative's foundation.
Over a few months the compounding shows up in calibration. A team that closes every session with an owner, a test and a date accumulates a record of which of its confident beliefs were wrong — and starts discounting the next confident belief appropriately. A team that closes with a photograph of a wall has no such record, and will have the same argument about the same assumption next quarter, with the same confidence.
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. |
- "Brainstorming means no criticism."
- The no-criticism rule belongs to the generation phase only, and it exists to protect half-formed ideas for twenty minutes. Carrying it into convergence produces a wall of unexamined options and a decision made on enthusiasm. Divergence protects ideas; convergence is where they earn their place.
- "The goal is to reach consensus."
- The goal is a decision with the dissent written down. A room that agrees unanimously has usually lost its dissent rather than resolved it, and unresolved dissent does not disappear — it returns in week six as a surprise, held by the person who could have told you in week one.
- "More people in the room means more ideas."
- Past roughly seven, coordination cost and anchoring both rise while independent contribution falls. Invite people because the decision needs what they know, not because exclusion feels impolite — then share the output widely, which is what most people actually wanted.
- "The wall of sticky notes is the output."
- The output is the closing paragraph: direction, dissent, the tests, their owners, and the date the decision gets made. The wall is raw material, and a photograph of raw material has never once changed what a team built.
When this is the wrong move
Do not run this when the decision is already made. Staging divergence to produce a conclusion you have chosen is manipulation with a whiteboard, and people can tell; announce the decision, explain the reasoning, and spend the workshop budget on a question that is still open. Do not run it when the group lacks the context either — the silent phase then produces confident guesses, and clustering guesses makes them look like findings. Run a facts round, or send a pre-read and delay a week.
Two smaller counter-cases. With two or three people who already speak daily, the ceremony costs more than the anchoring it removes: talk, decide, write the paragraph. And when the question already has an answer somewhere — a documented rate limit, a legal constraint, a published benchmark — a workshop is an expensive way to reinvent it. Go and read, then bring the answer to the room as a constraint.
In the lab: the companion Phase 4 exercise asks you to list the beliefs the existing returns implementation silently encodes — about eligibility, exception rates and carrier behaviour — rank them by impact and evidence, and design the cheapest test for the top one. For a fully worked version, see the capstone's assumption map.
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.
- In two sentences, explain to a junior why a room of eight talking people does not search eight times as much of the solution space.
- Take one belief your current initiative is resting on. Name the cheapest test that could refute it, and what the team would build differently if it came back at half the assumed value.
- Predict the one-year state if assumptions keep going untested: which decision will be revisited for the third time, and what will people call the reason?
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 — ch. 7–9: assumption mapping, the four product risks, and sizing a test to the decision it informs.
- Thinking, Fast and Slow, Kahneman — the anchoring and availability chapters: why the first number said aloud in a room keeps its grip on everyone in it.
- 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.