The CEO asks why features take three times longer than two years ago. How do you investigate and respond?
Short answer
Measure the delivery system (lead time breakdown, wait states, change failure rate, incident load, team dependencies), identify the main causes (technical debt hotspots, coupling, manual testing, organizational hand-offs), and present a prioritized plan with business-level outcomes and progress metrics.
Detailed answer
- Data: DORA metrics trends, value stream mapping (where work waits), incident and on-call load, code hotspots (churn × complexity), dependency between teams per feature, developer survey.
- Typical findings: manual regression testing, shared database coupling forcing coordination, a fragile module causing incidents, growing team count without boundaries.
- Plan: targeted fixes with measurable goals (automate tests on critical path; split the coupled module; align teams to domains), funded with a fixed capacity share.
- Communicate: one page with cause, plan, cost and expected lead-time improvement; monthly progress.
What the interviewer expects
Evidence over opinions, business framing, a credible plan.
Common mistakes to avoid
Blaming previous teams, asking for a long feature freeze without measurable outcomes.