Q Hamirani has built people functions inside Deloitte, Aon, JLL, GE, TPG Capital, and Airbnb, plus two of his own startups. That career arc is unusual: most senior People leaders specialize either in scaled enterprises or hyper-growth, not both. The pattern showed up in this Reimagining Company Culture conversation, where Q described how he treats challenges (a layoff, a reorg, a sudden hiring freeze) as openings to redesign how the People function actually operates.
The conversation centered on a practical question: when the business changes faster than the org chart, what does a people leader actually do? Q’s answer is less about resilience platitudes and more about operating discipline. The teams that come out ahead are the ones that use the disruption to remove fragile processes and replace them with systems that scale.
What follows is a synthesis of the conversation paired with research and field practice from People teams shipping similar work today.
Why HR Leaders Should Treat Disruption as a Design Trigger
Most People functions inherit their processes. A round of growth gets bolted onto the legacy system, then another, then a reorg breaks something, and suddenly there are six tools doing the same job. Disruption is when that mess becomes visible. Smart leaders use those moments to consolidate.
McKinsey research on high-performing cultures reports that 70 percent of transformations fail, and 70 percent of those failures trace back to culture-related issues. The implication is sharp: technology and process changes do not stick unless the underlying behaviors and operating model change with them. Q’s framing matches that finding closely.
The structural opportunity in any disruption is to retire processes that no longer serve the company. Headcount changes are the obvious trigger, but reorgs, leadership turnover, and product pivots all expose hidden brittleness. The People teams that prepare for these moments end up with cleaner systems on the other side.
What Scalable People Operations Look Like in Practice
How do you build a people function that survives 5x growth?
Start with the questions you keep getting asked. If managers ask the same five questions every week, that is not a manager problem; it is a system problem. Scalable people ops looks like clear policy, predictable workflows, and tooling that absorbs repetitive work so HRBPs spend their time on the high-judgment cases. Pair that with a real people analytics function and the org gets a feedback loop that compounds.
What is the difference between operational HR and strategic HR?
Operational HR runs the engine. Strategic HR redesigns the engine. Both matter; the trick is to keep them from blurring. Q’s pattern is to push as much operational work as possible into automation and shared services so the strategic layer can focus on workforce planning, leader development, and culture.
What Actually Works in Hyper-Growth People Functions
Build the lightweight version first
The biggest mistake hyper-growth People teams make is buying enterprise tooling for a 200-person company. The right move is to build the lightweight version of every process, ship it, learn what breaks at scale, then upgrade. Most companies skip that learning loop and pay for it later in unused tools and frustrated managers.
Use AI to absorb the long tail of HR questions
Most HR questions are repeats. A GPT-powered HR assistant can take on the long tail (PTO policy, benefits triage, basic ER questions) and free up HRBP time for the harder cases that require judgment. The teams using this well treat the AI as a Tier 1 support function, not a replacement for ER specialists.
Standardize how cases get handled
The other compounding move is consolidating case handling. Centralized HR case management gives leaders one system of record across reports, investigations, and follow-ups. Without that, ER becomes a folder full of email threads and a few people’s memories, which falls apart the first time someone leaves the team.
Audit your tooling every 12 months
Tool sprawl is the silent killer of people ops. Annual audits, with a real willingness to retire underused systems, keep the stack maintainable. Most companies inherit two to three tools they do not need; cutting them frees budget and reduces the cognitive load on managers.
Where Employee Relations Fits in Scalable People Ops
ER usually breaks first under growth pressure. Cases multiply faster than headcount, intake quality drops, and managers stop trusting the function to follow through. Building a scalable people operations function means treating ER as core infrastructure, not a stretch assignment for whoever has bandwidth.
How AI changes ER capacity
AI does not replace ER specialists. It does what most specialists wish they could outsource: drafting the first version of an investigation summary, flagging case pattern matches, and surfacing risk before it escalates. managers account for 70 percent of the variance in employee engagement across business units, which makes high-quality ER signal critical for spotting which managers need coaching before issues turn into formal complaints.
Frequently Asked Questions About Scaling People Operations
What does people operations actually mean?
People operations covers the systems, tools, policies, and workflows that run HR day to day: onboarding, benefits, payroll integration, case management, compliance, and reporting. It is the operational backbone that lets strategic HR work happen.
When should a company hire its first people ops leader?
Most companies should bring in a dedicated people ops leader between 100 and 200 employees. Below that, an HRBP usually carries it. Above 200, the lack of a dedicated owner shows up as policy drift and tool sprawl.
How much of HR can be automated today?
Roughly 40 to 60 percent of repetitive HR work, depending on the company. The areas with the highest automation payoff are policy questions, intake triage, scheduling, and reporting. Anything requiring real judgment about a person’s situation should stay with humans, augmented by good data.
What is the right ratio of HRBPs to employees?
The healthy ratio for mid-market companies sits around 1 HRBP per 100 to 150 employees, depending on complexity. Heavily distributed or unionized environments need more. Hyper-growth environments often run leaner because automation absorbs the load.
How should people ops measure success?
Time to resolution on cases, manager NPS, employee Net Promoter Score, regrettable attrition, and policy clarity scores all matter. Pick a small set, measure consistently, and resist the urge to add new metrics every quarter.
The Bottom Line for HR Leaders
Hyper-growth is a stress test for the people function. The teams that come out of growth in better shape are the ones that used it to redesign rather than patch. Q’s pattern (build lightweight, automate the predictable, invest the saved time in judgment work) is the playbook most companies need to copy.
The structural move is to stop running people ops as a service desk and start running it as a system. Combine a modern HR operating model with disciplined tooling and situational leadership styles that fit the moment, and the team gets compounding advantage instead of compounding overhead.
Disruption is the cheapest design partner a People team will ever have. The leaders who use it well end up running smaller, sharper, and more strategic functions on the other side, with managers who actually trust the system and ER cases that get resolved before they become public.
See how AllVoices helps People teams turn workplace signals into action.
.avif)
.avif)
.avif)