Engineering leaders have always needed to translate between technology and business. The gap has been tolerable because delivery cycles were long enough to absorb misalignment. That tolerance is shrinking.
The disconnect is structural. Engineers and boards are accountable for different things, measure different outcomes, and rarely translate between the two.
Observation
Engineering teams optimise for system reliability, code quality, and technical debt. Boards measure growth, cost, and competitive survival. Both are rational. Both are incomplete.
The translation layer between them is thin or missing. Technical decisions with significant commercial implications get made without commercial framing. Board-level priorities arrive in engineering as “the board wants X feature,” often filtered through someone who couldn’t articulate the reasoning behind it. Trade-offs that should be explicit stay invisible until something breaks.
This has always been true. What’s changed is the cost of leaving it unresolved.
Hypothesis
The conversation about where to accept less robustness and where it is non-negotiable is not happening explicitly. AI is accelerating delivery timelines, which makes this worse. Boards see acceleration. Engineers see compounding risk. But the trade-off conversation was missing before AI arrived.
Engineering leaders who only speak engineering will lose influence. Not because their technical judgment gets worse, but because the decisions that matter are increasingly commercial. Where to hedge. What quality trade-offs the business is willing to make. How technology investment translates to bottom-line impact.
The leaders who close this gap won’t do it by learning finance. They will do it by learning to ask different questions. Not “what?” but “so what?” Not system health, but what that system health means for the business.
What Could That Look Like
- Engineering leaders who frame technical decisions in commercial terms because that’s how they think, not because they’re presenting to the board
- Trade-off conversations that happen before architectural commitments, not after delivery surprises
- Boards that understand what they are asking for when they demand speed, because someone translated the cost
- Engineering teams that can explain what their work costs and what it returns, not just whether it shipped
Reflection
Technology leadership has always required translation. The industry treated it as a nice-to-have. A soft skill. Something you pick up eventually. AI is turning “eventually” into “now.” The leaders who matter will sit in a boardroom and an architecture review in the same week. And know what each one needs from the other.