The wireframes are on the table, and the CFO's question hangs in the air: what does this actually do for the bottom line? Alex Williams's piece on building a UX ROI case that survives the boardroom lands at exactly the right moment. We have watched too many promising design initiatives stall not because the idea was weak, but because the argument for it was built on enthusiasm rather than evidence. The era of the five-minute pitch is over, and Williams is honest about why. Storyboards tell a story, but they do not calculate a return. His worked example is a practical counter to the assumption that good design sells itself.
What we appreciate most about this approach is the discipline it demands. Defining business value, calculating costs, and testing causality are not glamorous tasks, but they are the difference between a proposal that gets funded and one that gets politely filed away. Williams is not asking designers to become accountants. He is asking them to translate their work into the language of the people who hold the budget. This is not about diluting the craft; it is about protecting it. In a related piece on why the best interface is sometimes no interface at all, the argument is that removing friction is a form of design. The same logic applies here: removing ambiguity about value is a form of UX, just aimed at the executive stakeholder.
The practical takeaway is sharp and quotable: "If you cannot define the business value, you are not ready for the meeting." That is the line we would underline and hand back to anyone preparing a case for investment. It is not harsh; it is honest. Too many teams treat ROI as a post-hoc justification rather than a design constraint. Williams flips that, and the shift is overdue. He also reminds us that causality matters. A pretty dashboard that correlates with a revenue bump is not the same as a dashboard that caused it. That distinction is where credibility lives or dies.
We would tell a reader preparing for a budget review to start with the cost of the problem, not the beauty of the solution. The boardroom does not need a demonstration of your tooling; it needs a demonstration of your thinking. And the thinking has to be traceable from user behavior to business outcome. This is also why we found the piece on building a vision pipeline for real-time chessboard detection so relevant. That project succeeded because it was scoped around a clear, testable outcome, not a vague ambition to modernize. The same principle applies to any UX initiative: define the metric before you open the design tool.
The question Williams leaves us with is not whether design can prove its value, but whether designers are willing to do the unglamorous work of proving it. That is the detail to watch. The teams that embrace this discipline will not just survive the boardroom; they will earn the trust to keep designing. The ones that do not will keep wondering why their best ideas never leave the whiteboard.