Optimization

Optimization is improving a system toward a defined objective — making a chosen variable as good as possible given constraints. The objective might be cost, speed, throughput, or quality; the constraints might be time, capital, or physical limits. The discipline is explicit: name the objective, identify the constraints, then improve until the next improvement costs more than it returns. Without a clear objective, optimization drifts into local tweaks that don't move the needle. Without constraints, the "optimal" solution is often infinite scale or zero cost — useless.

In practice, most systems have one binding constraint at a time. The Theory of Constraints frames this: find the bottleneck, optimise there, then the bottleneck moves. Optimising a non-bottleneck is waste. A factory that speeds up a station downstream of the slowest station only builds inventory. A product team that optimises a feature few users touch burns cycles. The strategic question is always: what is the current constraint, and does this change relax it?

Optimization has a dark side: premature optimisation. Donald Knuth's line — "premature optimisation is the root of all evil" — applies when you optimise before the problem is stable, the objective is clear, or the bottleneck is known. Early-stage startups that tune database queries before product-market fit are optimising the wrong thing. The right sequence: validate the system, then optimise the constraint. Optimization also risks overfitting to the current environment. A process optimised for last quarter's demand can break when demand shifts. The best optimisers leave slack at the constraint and re-check the objective when the world changes.