Mandated transformation in a claims organization
Meridian Claims has launched a CIO-mandated Agile transformation across 12 teams. Four months in, daily stand-up attendance is around 70%, but stage-gate governance, annual budgeting, and individual performance bonuses remain unchanged. Middle managers say they are losing control and quietly require weekly status reports that duplicate the team boards. Teams describe themselves as “Agile” but still hand off work sequentially to a separate testing group. The CIO wants a dashboard proving the transformation is working by quarter end and is considering a SAFe rollout because “it looks more structured.” You are the external Agile coach asked to facilitate the next phase without formal authority over the managers or the governance process.
1. How would you frame the change problem, and what would you avoid doing first?
Read the worked answer
Frame the problem as a system-alignment issue, not a training or ceremony issue. Attendance at stand-ups is a weak adoption signal; the stronger signals are duplicated reporting, sequential testing handoffs, and stage gates that reward late certainty. The annual budget and individual bonuses still tell managers to optimize for local utilization and annual commitments, which conflicts with iterative delivery. I would avoid launching a framework rollout first, because SAFe would add structure without removing the underlying constraints and could create a new layer of compliance. Instead, map the current decision rights, funding flow, and reporting demands against the stated goals. Identify two or three governance changes that would reduce duplication and support earlier feedback. Use the CIO’s dashboard request to negotiate outcome measures such as lead time, flow efficiency, and defect escape rate, not ceremony attendance.
2. Design an engagement approach for the middle managers. What do you want them to own, and how will you handle resistance?
Read the worked answer
Treat middle managers as co-designers of the new operating model, not as resistors to be trained. Start with a working session that surfaces their real constraints: audit obligations, staffing decisions, escalation paths, and the weekly reports they are judged on. Ask them to identify which reports are duplicated and which decisions could move closer to the teams with clear guardrails. Give them ownership of a bounded problem, such as reducing handoff delay between teams and testing or redesigning the weekly status review. Resistance often signals a legitimate loss of control; address it by making decision rights explicit and agreeing what managers will still own. Do not bypass them with a team-only pilot, because they can quietly kill it. Use a small coalition of willing managers, publish early evidence, and let peers influence peers. Escalate only when a manager actively blocks a agreed experiment.
3. The CIO wants a quarter-end dashboard and is considering SAFe. How do you respond on metrics and framework choice?
Read the worked answer
Connect metrics to the CIO’s stated business outcomes, not to framework adoption. Propose a small set: lead time from accepted work to production, flow efficiency, change failure rate, escaped defects, and the percentage of teams with a current impediment log that is acted on. Add a qualitative check on whether duplicated reporting has fallen. Avoid a dashboard that rewards stand-up attendance or story-point velocity. On SAFe, do not reject it reflexively; ask what problem it is meant to solve. If the issue is coordination across 12 teams and funding alignment, consider whether lightweight portfolio cadence and dependency management would address it before a full framework rollout. Offer a comparison of options against the governance constraints and a 6–8 week experiment. Make the trade-offs visible: a structured framework may help coordination but can add overhead if stage gates and individual bonuses remain unchanged.