A VP of Engineering presents a proposal to replace the company’s batch processing infrastructure. Current infrastructure runs nightly jobs that take six hours. The replacement would run streaming jobs with near-real-time output. The cost: fourteen engineer-weeks to build. The benefit: customers see fresher data.
The board asks the natural question: is fourteen engineer-weeks worth fresher data? The VP cannot answer, because the proposal was framed as an engineering improvement, not an economic decision. Nobody had asked what fresher data is worth to a customer. Nobody had asked what fourteen engineer-weeks would cost in opportunity — what else could be built with that capacity. Nobody had asked what the streaming infrastructure would cost to operate per month at 2x current data volume.
Engineering decisions are economic decisions. The vocabulary of engineering economics — cost of delay, total cost of ownership, investment return — converts engineering proposals from capability arguments into decision inputs that non-technical stakeholders can evaluate alongside the organisation’s other investments.