The Four E's

The order, and why it cannot be reshuffled

Engagement comes first: is anyone showing up to use this at all? Experience comes second: is using it pleasant, or does it fight the person every step? Effectiveness comes third: does using it actually lead to a better decision or outcome? Efficiency comes last: can we now do all of that faster and cheaper, having already earned the right to optimize it. Each stage only matters once the one before it is real — optimizing the efficiency of a dashboard nobody is engaged with is optimizing the delivery speed of a product that will still gather dust, just faster.

The mistake almost every team makes

Most analytics leaders reach for Efficiency first, because it is the easiest one to put a number on — query runtime, pipeline latency, cost per report. Those are real and worth tracking eventually. But a beautifully efficient system nobody engages with is still a system nobody uses, and no amount of speed fixes that. The vanity-metrics failure and the Four E's failure are the same failure wearing different clothes: optimizing a number that was never the bottleneck.

This is the same instinct behind an exec dashboard full of lagging indicators — last month's revenue, last quarter's pipeline — that only tells a room what already happened. A dashboard weighted toward leading indicators forces the conversation from "what happened" to "what's coming and what do we do about it," which is a more useful conversation at every one of the Four E stages, not just the first.

What to check at each stage

At Engagement: are people opening this at all, and coming back a second time? At Experience: when they open it, do they find what they need without a workaround, or do they quietly export to Excel and do the real work somewhere else? At Effectiveness: can anyone point to a specific decision this actually changed? At Efficiency: now that the first three are real, where is the waste in how it gets delivered?

If you cannot answer the Engagement question with real usage numbers, nothing downstream is worth measuring yet — you would just be polishing something on its way to the graveyard, faster.

Where this shows up in the book

This is the throughline of the second leadership essay, built around watching a VP parse a metrics report with a physical ruler and highlighter because the report itself never asked what the reader actually needed from it.