Tech
Failing to Translate Architecture Into Economics
Engineering establishes causal relationships. Economics determines value. An engineer can tell you that six units of A plus four of B will produce eight of P. That cannot tell you whether producing P is the best use of A, B, and C.
When an engineer designs an interface, the cost of that decision compounds across years. Tight coupling creates coordination meetings that consume engineering hours at a real dollar cost. The engineer at the whiteboard does not see that number. Neither does the CEO approving the feature.