Most People & Culture leaders don’t struggle with ideas. They struggle with getting those ideas approved.
You can see what’s going wrong in the business. Turnover is higher than it should be. Leaders are inconsistent. Hiring isn’t delivering the quality you expected. Engagement is drifting.
You likely have a clear view on what needs to change. But when it comes time to put that forward?
The idea doesn’t land the way it should.
That usually comes down to one thing. The business case isn’t doing enough heavy lifting.
A business case is not a document for HR.
It is a decision-making tool for the business.
Its job is to help a small group of stakeholders decide whether something is worth investing in. That means it needs to be clear, grounded, and commercially relevant.
If it feels vague or overly conceptual, it creates doubt.
And when there is doubt, decisions slow down or stop altogether.
This is where many people go wrong early.
They build something that looks like a business plan when what they actually need is a business case.
Here is the difference in practical terms:
| Business Case | Business Plan | |
|---|---|---|
| Scope | Focused on a specific project or initiative | Covers the entire business |
| Audience | Internal stakeholders such as executives and finance | External stakeholders such as investors |
| Purpose | Justifies a decision to invest in something specific | Outlines overall strategy and direction |
| Content | Problem, options, costs, benefits, risks, implementation | Market analysis, strategy, financial forecasts |
|
Nature |
One-off, decision-focused document |
Ongoing, evolving document |
If you take one thing from this section, it is this. A business case is not about explaining everything. It is about making a decision easier.
The issue is rarely the idea itself. The issue is how it is presented.
Most business cases coming out of People and Culture teams lean too heavily on language that does not connect to business priorities. They talk about culture, engagement, and wellbeing without clearly linking those things to cost, performance, or risk.
From an executive perspective, that creates a gap.
They are not asking whether something is a good idea in principle. They are asking what it will change and what it is worth.
If that connection is not made clearly, the initiative feels optional.
A strong business case is rarely written in isolation. It is shaped through conversations.
That might mean testing assumptions with finance, getting input from leaders who will be affected, or understanding what is already competing for attention and budget.
By the time the document is written, the thinking has already been challenged and refined.
That approach is consistent with how most consulting-led business cases are built. The alignment happens early. The document then reflects that thinking rather than trying to create it from scratch.
At a high level, every effective business case answers three questions.
Why should we do this?
What is the best way to do it?
What will happen if we go ahead?
Those questions sound simple, but answering them well requires structure.
You can follow different formats depending on your organisation, but most effective business cases follow a similar flow.
| Stage | Section | What it covers |
|---|---|---|
| Why should we do this? | 1. Recommendation | Start with the answer. What are you proposing and why does it matter now? |
| 2. The Problem | What’s happening in the business, and what is it costing in real terms? | |
| What’s the case? | 3. Supporting Argument | What data, insight, or evidence proves this is worth solving? |
| 4. Other Options Considered | What else could we do, including doing nothing, and why is this the best path? | |
| What does it look like? | 5. Cost & Expected ROI | What will it cost, and what will the business get back? |
| What happens next? | 6. Next Steps | What needs to happen next to get this approved and underway? |
It starts with a short summary that outlines the problem, the proposed solution, and the expected impact. This is often the only section some stakeholders will read in detail, so it needs to be sharp.
From there, the context is laid out. What is happening in the business and why this issue matters now. This is where you create a sense of urgency using data and observable trends rather than opinion.
The problem is then defined clearly. This is a critical step. If stakeholders do not agree with how the problem is framed, they will challenge everything that follows. Strong business cases use data, feedback, and evidence from across the business to make the issue clear and specific.
Once the problem is understood, the focus shifts to the solution. This usually starts at a high level before moving into more detail. The key here is not to jump straight to a recommendation. It is to show that different options have been considered and assessed.
Including a “do nothing” option is often useful. It makes the cost of inaction visible and provides a baseline for comparison.
After that, the recommended approach is presented in more detail. This includes what will be delivered, what it will cost, and what benefits are expected. This is where the commercial side of the case becomes clear.
The implementation plan follows. This shows how the work will actually happen. Who is involved, what the key milestones are, and how progress will be tracked. This reduces uncertainty and builds confidence.
Risks are then addressed. Rather than avoiding them, strong cases acknowledge where things could go wrong and how those risks will be managed. This tends to increase trust rather than reduce it.
Finally, the case closes with a clear recommendation and next steps. This should make it easy for stakeholders to move forward without needing further clarification.
For People and Culture leaders, this is not just about getting approval for a project.
It is about how your work is understood.
When business cases are built well, they connect people initiatives directly to business outcomes. They show how improving retention affects cost. How leadership capability affects performance. How employee experience influences results.
That changes the conversation.
It moves HR away from being seen as a support function and positions it as something that directly contributes to business success.
That shift does not come from better ideas. It comes from making those ideas easier to back.
Writing this from scratch can take time, especially if you are not doing it often.
We have built a practical business case template based on how we approach this work with clients. It follows the structure outlined above and includes prompts to help you think through each section properly.
A business case is not about proving that something is a good idea. It is about making it clear why it should be prioritised now.
When the problem is well defined, the options are clear, and the value is easy to see, the decision becomes straightforward.
That is what a good business case does.