Leading ambiguous initiatives
On this page 9 topics
Overview
Topics
- Defining problems
- building alignment
- sequencing delivery
Learn first
3.5 h of practice (estimate)
Learning outcomes
- Define a problem worth solving from vague signals ("checkout feels fragile").
- Build alignment on the problem before the solution.
- Sequence delivery to show value early and learn quickly.
- Know when to hand an initiative to a team and step back.
Lessons
Lab and exercises
Lab
SRA-014-LAB1 · Fragile checkout
Outcomes: 1–4 · Time: ~2 h
- From provided interview notes and incident data, find patterns and write a problem statement (who, what, evidence, impact, scope, success measure).
- Meet role-played stakeholders (product, SRE, support, engineering manager) individually, then hold a short alignment session.
- Record agreement on the problem in writing.
- Plan the first two milestones with value, risk, and measures.
- Draft the handoff note naming the receiving team and your exit date.
Acceptance: stakeholders agree on the problem statement in writing.
Exercises (case-based; six exercises)
| ID | Outcome | Task |
|---|---|---|
| SRA-014-EX01 | 1 | Given five raw signals about "slow to change", write a problem statement with evidence and no solution. |
| SRA-014-EX02 | 1 | Edit a draft statement that contains "we need a new platform" into a clean problem statement. |
| SRA-014-EX03 | 2 | Plan the alignment conversations: order of stakeholders, what each must confirm, and how you handle a disagreement. |
| SRA-014-EX04 | 3 | Choose and justify the first two milestones for fragile checkout using early value and riskiest-first. |
| SRA-014-EX05 | 4 | Write a handoff note for the receiving team, including decision rights and your office hours. |
| SRA-014-EX06 | 4 | Decide whether to hand off now or in two months given three facts about the team's capacity and the problem clarity. |
Show solutions
- EX01 Example: median change waits six days for approval; two teams hold approvals; support tickets and incidents cluster around the same releases; impact stated in lead time and failure rate.
- EX02 Replace the solution with the observed delay and its measured effect; list solutions separately for later discussion.
- EX03 Meet individuals first, then the group; each confirms problem, impact estimate, scope; where wording differs, reconcile in writing; escalate only unresolved scope questions.
- EX04 M1: six weeks, timeouts and dashboard on the top two failure points (visible value, quick learning); M2: isolate payment calls, measure checkout failure rate; riskiest assumption tested in M1.
- EX05 Contents: problem statement, alignment record, milestones, risks, who decides what, contact period until a set date.
- EX06 Hand off when the problem is clear and the team has mandate and capacity; if capacity is missing, secure it or delay the handoff, but set a date.
All four outcomes are also exercised in the lab.
Workplace evidence: an initiative you started from an ambiguous problem and handed to a team.
Quiz
Outcomes: O1 defining the problem · O2 alignment before solutions · O3 sequencing for early value · O4 handing off.
A self-check for you: nothing is graded, saved or sent anywhere. Choose an answer, then check it. You can try again as often as you like.
Practical part
Six case exercises SRA-014-EX01 to EX06 plus the lab (initiative brief and alignment session). Pass: quiz at least 8/10, and a brief and session in which stakeholders agree the problem statement in writing and the first two milestones are sequenced for early value.
Common mistakes
Jumping to a favorite solution; trying to own the initiative forever.
Assessment
Initiative brief and alignment session.
Workplace evidence
An initiative you started from an ambiguous problem and handed to a team.
Career relevance
Cross-team programs and organizational change (STF-013, STF-014).