hardScenarioCase StudySeniorStaffLead
You need a steering committee to fund a quarter of platform hardening instead of two customer features. How do you put technical risk and feature risk side by side so an executive can choose?
5 min readUpdated 2026-08-15
Answer
Short answer
Express both in the same currency, which is expected cost to the business over a stated horizon, and show the arithmetic from assumptions the room can argue with. Give the committee a real choice with a decision date rather than a single option and a plea.
Was this answer helpful?
Likely follow-ups
- The CFO disputes your incident-cost figure and halves it. Does your recommendation survive, and how do you handle being challenged on the input?
- How would you present this if you genuinely could not estimate the probability of the failure at all?
- What does it look like six months later if the committee funds the features and nothing breaks? How do you avoid having spent your credibility?
- Which parts of the hardening would you deliberately leave undone to fit a half-quarter, and how do you choose?
Related questions
- Make the case to a CFO for funding a modernisation programme that nobody outside engineering can see.hardAlso on technical-debt and executive-communication6 min
- The platform migration has no user-visible benefit. How do you rank it against features customers are asking for?hardAlso on technical-debt5 min
- Feature delivery and paying down architectural debt are competing for the same engineers. How do you decide the split and defend it?hardAlso on technical-debt6 min
- You present last week's major outage to the board next week. What goes in the paper, and what stays out?hardAlso on executive-communication6 min