When One HR Model Had to Serve Different Realities
They came with
“We need an HR strategy for International Markets.”
The question became
What does each business need to become capable of — and what must HR become capable of enabling?
The organization had ambitious plans for its International Markets business. But those markets were not all the same.
Different geographies were operating with different business models, different maturity levels, different priorities and different challenges. A single HR model, applied identically everywhere, would have been answering a question nobody had asked.
So before asking what HR should do, we started with a more fundamental question: what does each business actually need to become capable of?
Understanding the business before designing HR
We began with the businesses themselves. Their jobs. Their pains. Their gains. Their priorities. Their KPIs. Their current realities.
The aim was not to collect a list of requests for HR. It was to understand what each business was trying to make possible.
That distinction mattered. Because the receiver of HR value is not HR. It is the business.
Translating business needs into organizational capability
Once the business needs became clearer, we translated them into the organizational capabilities required to deliver them.
Some markets needed stronger commercial execution. Some needed greater organizational maturity. Some needed clearer roles, stronger leadership capability or better coordination. Some needed faster growth. Some needed more consistency.
The point was not to ask which HR practice should be introduced. The point was to ask what this organization must become capable of — and what HR must become capable of enabling in response.
Looking at HR through the same lens
Only then did we turn to the HR function. We looked at current practices, systems, processes, roles and capabilities, and at the value HR was currently perceived to create.
Then we compared that reality with what the different businesses actually needed.
The gaps were not identical across markets. And therefore the HR contribution could not be identical either.
Designing an outside-in HR model
The design logic ran from the outside in. Business reality — strategy, business model, maturity, KPIs, jobs, pains, gains — sets the organizational capability required to deliver it. That capability sets the HR capability required to enable it. Only at the end does HR's own contribution follow: its roles, practices, systems, relationships and responsibilities.
This moved the conversation away from a standard HR model applied everywhere in the same way. Instead, HR was designed around the value different businesses needed it to create.
International markets
Business → HR contribution
The result was not one universal answer for every market.
It was a clearer logic for deciding what HR needed to enable, where, and why. What began as an HR strategy project became a broader exercise in understanding how an enabling function should respond to different business realities.
ALIGN delivered the design and roadmap to the organization for internal implementation.
It began as a question about HR. It became a question about what the business needed HR to make possible.