HR Should Not Start With People. It Should Start With the Business.
- Jeramy Johnson
- Aug 2
- 4 min read
A people strategy is only useful when it is built around the customer, the product, the operating model, and the financial plan.
I have spent most of my career in HR, and I understand why the phrase “people first” is so appealing. It sounds humane. It signals that employees matter. It also gives HR a clear place in the conversation.
But I do not believe strong HR work starts with people. It starts with the business.
That is not an argument for treating employees as secondary. It is an argument for giving people work that is connected to a real business need, supported by clear priorities, and designed to last. When HR begins with a program instead of the business problem, even well-intended work can become expensive, disconnected, or difficult to sustain.
Before I recommend an organization change, a performance process, a hiring plan, or a leadership program, I want to understand how the company works. What does it sell? Who is the customer? Where does revenue come from? What is getting in the way of growth? What must be true operationally for the strategy to succeed?
The people agenda should be a translation of the business agenda, not a separate list of HR priorities.
Start with the customer and the economics
The first questions should not be about engagement scores or job architecture. They should be about the customer, the product, and the economics of the business.
A software company moving from implementation revenue toward recurring revenue needs a different organization than one that still depends on large custom projects. A field-service business with an eight-month time to productivity cannot treat hiring as a simple requisition-volume problem. A company trying to improve margin may not need fewer people across the board. It may need different skills, clearer decision rights, a better management span, or more disciplined prioritization.
Those distinctions matter because the same HR solution can be right for one company and wrong for another. A new performance process may create useful accountability in a scaling business. In a company with an unclear strategy, it may simply create a formal way to measure confusion.
Translate the business problem into organizational requirements
Once the business context is clear, the people questions become much more specific. Instead of asking, “How do we improve culture?” we can ask, “Which behaviors does this operating model require, and where are leaders reinforcing the opposite?” Instead of asking, “How many people should we hire?” we can ask, “What capacity is required, when must it become productive, and which roles have the greatest effect on revenue, customer experience, or risk?”
That translation usually requires decisions across five areas:
Organization: What work must be done, where should it sit, and who owns the decisions?
Capability: Which skills are required now, and which will matter as the strategy changes?
Capacity: How much work can the current organization absorb before service, safety, quality, or growth begins to suffer?
Leadership: What must managers be able to decide, communicate, and deliver?
Systems: Which processes, measures, incentives, and tools will reinforce the intended way of working?
This is where HR can add substantial value. The function has a wide view across the organization and often sees issues that no individual business unit can see on its own. But that value is only realized when HR connects what it sees to the decisions the business is trying to make.
Do not confuse activity with impact
HR teams can be busy while the organization remains stuck. A company can launch manager training, refresh its values, redesign performance reviews, and add new recruiting tools without changing the outcomes that matter.
The test is not whether the work was completed. The test is whether the organization is now better able to deliver the plan.
Did the new structure reduce handoffs or simply redraw the chart? Did compensation changes improve hiring and retention in roles the business could not afford to lose? Did a talent review produce real development and succession decisions, or did leaders spend three hours discussing boxes on a grid? Did recruiting add productive capacity when the operation needed it?
Business-first HR is also better for employees
A business-first approach can sound harder than a people-first message, but in practice it often creates a better employee experience.
People are frustrated by unclear priorities, duplicated work, weak managers, shifting expectations, and programs that do not solve the problems they face. They benefit when the organization is designed around real work, when leaders can explain why decisions are being made, and when performance expectations reflect what the business actually needs.
Employees also deserve honesty. Not every business decision will feel positive. Strategies change. Investments move. Roles evolve. Sometimes work is eliminated. HR should bring rigor, fairness, and humanity to those decisions, but it should not pretend the business context does not exist.
Five questions I ask before recommending an HR solution
What business outcome are we trying to change?
Which customer, product, financial, or operating constraint is involved?
What must people do differently for the outcome to improve?
Which organizational condition is preventing that today?
How will we know the intervention worked?
These questions do not eliminate the need for judgment. They do force the work to begin in the right place.
HR should care deeply about people. It should also be willing to understand the business well enough to make people decisions that are useful, durable, and credible. That is the difference between running HR programs and helping build an organization that can perform.
The Practical Takeaway: Begin with the business problem. Then design the organization, talent, and systems required to solve it.