Meridian Software: Redesigning a Country-by-Country HR Model
Meridian Software has 4,200 employees: US 2,300, Poland 700, Singapore 600, Brazil 600. Its 96-person HR function is organized entirely by country - each site runs its own recruiting coordinators, payroll vendor relationship, onboarding, benefits administration and employee relations. A diagnostic found 31 different HR policy documents, requisition approvals averaging 11 days in the US and 19 days in Brazil, three separate payroll vendors, and a manager net-promoter score for HR of -12. The CHRO must cut HR operating cost by 15% within 18 months while improving the manager experience. The CFO has approved no new HR technology spend before month 12. Brazil's labour courts scrutinize documentation closely; Singapore's tripartite guidelines expect consultation with unions and fair employment practice; Poland's HR team also supports consultation for a separate manufacturing subsidiary.
1. Classify these five activities - recruiting coordination, payroll vendor management, onboarding, benefits administration, employee relations - as centralize, standardize, or retain locally. State the criteria you are applying rather than giving a blanket 'global standard' answer.
Read the worked answer
Criteria to apply first (not the activity name):
- Is the cross-country variation driven by law, or only by legacy habit? Legal variance must stay local; habit variance should be eliminated.
- Transaction volume and stability - high-volume, low-judgement work is the cheapest to centralize.
- Cost of error - where a mistake creates statutory or litigation exposure, accountability must sit with someone who is liable under that country's law.
- Manager experience - fragmentation is what produced the 11- and 19-day approvals, and that is a process-design problem, not a legal one.
Application
- Recruiting coordination - centralize into two regional hubs (Americas; EMEA/APAC) with a standardized requisition-to-offer workflow and documented delegated authority. Nothing legal prevents this; the approval delay is self-inflicted.
- Payroll vendor management - centralize contract and relationship management, retain country delivery. Consolidate three vendors to one with in-country capability (possibly two if Brazil requires a local provider), but keep a named in-country accountable owner for statutory filings and payroll data.
- Onboarding - standardize global content and administration, localize only the statutory modules and language.
- Benefits administration - standardize platform and process, localize plan design. Plan design is market- and statute-driven; administration is not.
- Employee relations - retain locally. This is the highest-sensitivity activity for Brazil and Poland; a central team can set principles and case-review standards, but decisions and documentation must be owned locally.
The judgement the exam is testing: 'global standard' is only correct where the variation is not legally required. Applying it to employee relations or benefits design converts a cost programme into a legal exposure.
2. Where can the 15% cost reduction realistically come from, given no technology spend before month 12? What would make the target unachievable?
Read the worked answer
Baseline first. HR at 96 staff for 4,200 employees is roughly 1:44. Mature shared-service software organizations run 1:70–1:100 on simple footprints, but a four-country operation with Brazilian litigation exposure, EU consultation obligations and a manufacturing subsidiary justifies the conservative end - say 1:60. That implies an arithmetic capacity of roughly 25–30 roles, well above the 15% target. But headcount capacity is not the same as deliverable savings.
Realistic sources, phased
- Year 1 (no technology): vendor consolidation on payroll typically takes 10–20% out of payroll administration cost; collapsing 31 policy documents to roughly 8 cuts maintenance and review effort; moving approvals to documented delegated authority removes HR from routine transactions. A defensible year-1 target is 6–8%.
- Year 2 (post-HRIS): manager and employee self-service, a single case-management system, and absorption of site coordination roles into hubs deliver the balance.
What would break it
- Setting the target as a pure headcount cut before any process change - this produces the same work with fewer people and worse manager scores.
- Ignoring one-time costs: severance and notice in Brazil and Poland, and dual-running costs while old and new payroll providers overlap, can exceed year-1 savings.
- Hollowing out local employee-relations capability to hit a number, then paying it back in litigation.
Recommendation: present an 18-month plan with a 6–8% year-1 tranche and the remainder contingent on the HRIS business case in month 12. Committing to 15% by month 18 without technology is a promise the CHRO cannot keep.
3. What consultation obligations do Poland and Singapore create, and what is the risk of treating them as a compliance checkbox?
Read the worked answer
Map the obligations before the design is frozen.
- Poland: any transfer or reduction of functions affecting the manufacturing subsidiary triggers information and consultation duties with the trade unions and, where established, the works council. Consultation must be genuine and timely; failure can delay or block the change and generate claims.
- Singapore: not a co-determination regime, but tripartite guidelines create a strong expectation that employers inform and consult unions and apply fair employment practices. The risk is regulatory scrutiny, union-relations damage and reputational cost rather than a statutory veto - which makes it easy to underestimate.
The checkbox risk
- Announcing the design to staff before the statutory bodies are informed converts a manageable consultation into a fait accompli dispute - the single most common way these programmes fail.
- Consultation bodies will ask for the economic rationale, alternatives considered, and selection criteria. If HR has not prepared these, consultation stalls and the 18-month timetable slips.
- Consultation is also where local HR earns credibility with managers. Treating it as a formality damages the same ER relationships the model depends on for the 'retain locally' activities.
Practical approach: assign one accountable ER lead per country, sequence consultation ahead of the announcement to affected staff, prepare a consistent rationale and selection methodology in advance, and log consultation as evidence. Coordinate messaging globally; never synchronize the legal steps globally.