The strongest business cases are not simply calculations with a recommendation attached. They are structured decision processes that bring together people, evidence, economics, institutional priorities, and a clear rationale for action.
That is why developing a reliable business case often requires the project team to shift roles as the work progresses. At one moment the task is coordination. At another it is stakeholder discovery, fact-finding, analysis, writing, or assembling evidence. The useful question is not whether one person literally performs every role, but whether the process covers all of them.
WORKING PRINCIPLE
A decision-ready business case requires more than one kind of thinking.
The quality of the recommendation depends on how well the process integrates management, stakeholder judgment, information gathering, analysis, communication, and evidence.
The hats are roles, not job titles
The language is intentionally memorable. The “politician” is not about politics in the partisan sense, and the “salesperson” is not about pushing a predetermined answer. They describe two capabilities that are easy to neglect in analytical work: understanding how decisions actually get made, and understanding what the people making them genuinely need.
In a complex energy or infrastructure decision, no spreadsheet can substitute for those capabilities. The model becomes useful only when it is built around the right question, informed by the right people, supported by credible evidence, and translated into a recommendation the institution can understand and act on.
1. Project Manager — organize the decision process
A business case has scope, dependencies, contributors, assumptions, deadlines, and decisions of its own. Someone has to organize the work so technical analysis, stakeholder input, financial modeling, commercial questions, and evidence develop in a coherent sequence rather than as disconnected workstreams.
The project-management hat asks: What decision are we supporting? What information is required? Who owns each input? What remains unresolved? What has to happen next?
2. Politician — understand who matters, how, and why
Infrastructure decisions rarely belong to one person. Facilities may understand the physical need. Finance may control capital. Operations may inherit the consequences. Procurement, legal, risk, sustainability, executive leadership, customers, regulators, or governing boards may each influence what can actually move forward.
Wearing the politician hat means mapping that institutional reality. It means distinguishing formal authority from practical influence, understanding where legitimate concerns sit, and recognizing whose support, knowledge, or acceptance is necessary for a durable decision.
3. Salesperson — uncover what decision makers actually need
The best salespeople are often good listeners. In business-case development, this hat is about discovering the needs behind the decision rather than promoting a favored solution.
A CFO may need confidence in the capital exposure and downside case. An operating leader may care more about reliability, staffing, maintenance, and service response. An executive sponsor may need to understand strategic importance and timing. Those needs should shape the analysis without changing the underlying facts.
4. Detective — find the information that changes the answer
Important business-case inputs are rarely waiting in one clean data set. They may be buried in utility bills, maintenance histories, equipment records, contracts, engineering studies, interviews, budgets, operating practices, vendor proposals, or institutional memory.
The detective hat is about finding the missing facts, tracing assumptions back to their sources, noticing contradictions, and deciding which gaps materially affect the decision. Good investigation often matters more than adding another decimal place to the model.
5. Investigative Reporter — interview clearly and write coherently
Complex projects generate fragmented knowledge. Engineers know one part of the story. Operators know another. Finance, customers, vendors, and leadership each see different dimensions.
The investigative-reporter hat turns those perspectives into a coherent account of the decision: what is happening, why it matters, what alternatives exist, what is known, what remains uncertain, and where the evidence leads. The objective is clarity without oversimplification.
6. Analyst — calculate accurately and assess insightfully
This is the hat most people associate with a business case, and it matters enormously. Lifecycle cost, cash flow, capital requirements, avoided costs, sensitivity, risk, alternatives, and non-financial criteria all need disciplined analysis.
But the analyst is most useful after the other hats have helped define the right problem, criteria, baseline, assumptions, and evidence. Otherwise, rigorous analysis can produce a very precise answer to the wrong question.
A USEFUL REMINDER
The analyst is only one of the seven hats.
A strong model cannot rescue a weak decision process. The arithmetic becomes persuasive when the surrounding work makes the assumptions, evidence, institutional priorities, and recommendation credible.
7. Attorney — build the case from evidence to conclusion
The attorney hat does not mean advocating for a project regardless of the facts. It means constructing a disciplined chain of reasoning: this is the problem, these are the alternatives, this is the evidence, these are the economics and tradeoffs, and this is why the recommendation follows.
A decision-ready business case should be able to withstand reasonable challenge. Its claims should be traceable. Its uncertainties should be visible. Its logic should hold together when someone asks why a particular assumption, comparison, or recommendation deserves confidence.
The value comes from changing hats at the right time
These roles overlap, and they do not always occur in a neat sequence. New information can send the analyst back into detective mode. An operating concern can require the project manager to reopen scope. A stakeholder interview can change which alternatives deserve analysis. Evidence can strengthen—or undermine—the emerging recommendation.
That iteration is not inefficiency. It is how a business case becomes more reliable.
The larger lesson is that business-case development is an integrative discipline. It sits between engineering, economics, operations, commercial structure, stakeholders, and organizational decision-making. The quality of the answer depends not only on expertise inside each area, but on the ability to connect them.
A good business case helps an institution decide
The final product should do more than demonstrate that a project can work or calculate an expected return. It should help decision makers understand what problem they are solving, what alternatives they have, what the evidence supports, what risks and uncertainties remain, and why one course of action is more defensible than another.
That takes analysis. It also takes coordination, institutional awareness, listening, investigation, communication, and disciplined reasoning.
Seven hats is a simple way to remember the point: a credible business case is built by seeing the same decision from more than one perspective—and integrating those perspectives into a recommendation that can actually be used.