Lesson 0050 · Initiative Lead · Module 3
Steer, Replan, and Close the Initiative
Leadership is keeping the truth cheap to see. Review evidence while options remain, change the plan without disguising the change, and finish the operational and organizational work after launch.
Mission tie-in: a system is successful when it changes the intended outcome and remains responsibly owned. Shipping is a transition in that lifecycle, not the finish line.
Knowledge: run one evidence loop
Use a weekly initiative review built from live sources, not a status performance. Product, design, and engineering answer seven questions:
- Outcome: what does the latest measure say, by relevant cohort?
- Learning: which assumption became stronger, weaker, or false?
- Delivered evidence: what integrated behavior can now be demonstrated?
- Flow: what is aging or blocked, and where should the team swarm?
- Risk and quality: which driver, guardrail, dependency, or operational signal changed?
- Decisions: what was decided, what is waiting, and who owns the next evidence?
- Forecast: what range is credible now, and what scope trade preserves the outcome?
- Outcome
- Median 3.2 hours for eligible cohort; support contacts down 18% versus 25% target.
- Guardrails
- Fraud unchanged; manual queue 34/day under limit; mobile completion is 11 points lower.
- Learned
- Status visibility drives fewer contacts; label speed is not the limiting factor.
- Changed
- Move mobile comprehension work ahead of exchange automation; keep carrier design.
- Risk
- Guest orders are 29% of demand and remain outside pilot; product decision due Friday.
- Forecast
- Core pilot outcome likely in two weeks; exchange variation removed from this initiative.
- Ask
- Approve two design sessions with customer-support participants; no staffing change.
Make a change explicit across all affected artifacts. If guest checkout enters scope, update the frame, story map, threats, contracts, telemetry, rollout, and forecast. “We are still on plan” after the plan changed is how teams exchange trust for temporary comfort.
Pre-agree continue, change, and stop criteria. Continue when outcome movement and guardrails support the hypothesis. Change the solution or slice when the opportunity remains but evidence rejects the mechanism. Stop when the opportunity is too small, the intervention cannot move it economically, a guardrail cannot be protected, or strategy has changed. Stopping after cheap evidence is capital allocation, not team failure.
After release, close the initiative deliberately:
- Transfer service ownership, on-call, runbooks, access, dashboards, support knowledge, and vendor responsibility to a named steady-state owner.
- Remove release flags, temporary adapters, manual pilot paths, obsolete metrics, elevated access, and test data—or record each as debt with a trigger from lesson 0038.
- Supersede ADRs whose context changed; update context/container views, contract docs, and architecture fitness functions.
- Report the outcome against baseline and guardrails, including segments that did not benefit and costs that moved elsewhere.
- Hold a learning review: expected, observed, surprised, decision for next time. Turn at most one or two insights into owned system changes.
A retrospective about feelings can improve teamwork; an initiative review must also improve the organization's memory. Preserve decisions and evidence, not a victory narrative. Future leads need to know which assumptions failed and which shortcuts still charge interest.
| Pressure response | Damage | Leadership move |
|---|---|---|
| hide forecast until certain | Options disappear while confidence grows. | Share range, cause, options early. |
| add people late | Coordination load rises immediately. | Trade scope; remove blockers. |
| declare launch a success | Outcome and cleanup become orphaned. | Keep review through stabilization. |
| skip the closeout | Temporary machinery becomes permanent. | Assign removal and ownership dates. |
Skill: steer with evidence
The solution fails but the opportunity remains. Choose:
When should forecast risk be shared?
An initiative is operationally closed when:
Capstone: lead a simulated initiative
Choose a real or plausible product brief. In a 90-minute working session, produce the complete leadership packet: initiative frame, assumption map, current workflow, story-map slice, five architecture drivers, three-view architecture packet, one state/contract review, one ADR, walking skeleton, delivery/dependency map, team charter, and rollout contract. Then write the week-four review after inventing one adverse result. The templates live in the Initiative Playbook.
Reveal: how to review the capstone
Trace one line through every artifact: outcome → assumption → user slice → architecture driver → boundary/contract → decision → delivery milestone → test/telemetry → rollout gate → continue/change/stop criterion. Any broken link is either unnecessary work or an unmanaged risk. A strong packet is coherent, not large.
Your win
You can lead a new initiative from ambiguous brief through discovery, system design, team execution, controlled release, evidence-based steering, and responsible operational closure.
Read and watch deeper
- Thinking in Systems, Donella Meadows — feedback, delays, and why local delivery measures can misrepresent system outcomes.
- Accelerate, Forsgren, Humble & Kim — delivery performance and continuous improvement grounded in evidence.
- The DevOps Handbook, Kim et al. — feedback, telemetry, learning, and operational ownership across the value stream.
- Reference: Initiative Playbook · review and closeout, and the debt ledger.
Use your agent-teacher as a hostile reviewer of artifact coherence: it should ask what evidence connects each decision to the outcome, never manufacture the evidence itself.