Turning a business goal into a technical strategy with real choices, a sequence and measures, and defending it to executives.
6 questions in Executive & Engineering Leadership.
Treat executive conflict as information, not an attack. In the room, restate their strongest point, answer what your data covers, name what you will come back with and when. Afterwards, meet them privately, find whether it is a dispute about facts or priorities, and return to the CEO jointly. Never score points.
A modernisation business case for a CFO turns technical debt into what finance already manages: run cost, risk exposure and speed of change. Price the status quo from stated assumptions, offer options with costs, fund in gated tranches with measures, and let finance decide how the spend is treated.
Ask what slowed and against what baseline, then bring engineering metrics about the system: where capacity goes, DORA-style delivery and stability measures, flow, and business outcomes. Refuse lines of code, commit counts, cross-team story points and individual rankings, and give every trend its context.
Set decision criteria tied to business outcomes before scoring anything: the measured cost of the status quo, what each rewrite changes for customers, reversibility, capacity and any incremental route. Fund one rewrite properly rather than three partially, and tell the other teams first, in person, with the reasoning.
Define what entering means, then split the goal into a few engineering bets, each with a hypothesis, a leading indicator and a cost. Sequence the cheapest learning first, release capacity through gates, and agree kill criteria in advance that fire on early signals, not month-twelve revenue.
A two-year technology strategy needs a diagnosis of the business problem, a guiding policy with explicit choices, a few costed actions with owners, a stop list and measures. It is a strategy, not a roadmap, if it can refuse a funded proposal and still means something with every date deleted.