HR Data Labs

The Companies Betting Everything on Speed Just Skipped a Step

Cartoon businessman sprinting up a staircase and leaping over a missing step outlined in red

By Desiree Goldey, Senior Consultant and Project Lead, HR Data Labs

Every leadership team in 2026 says the same thing, that they need to move faster, and seven in ten business leaders now name speed and adaptability as their top competitive strategy for the next three years, according to Deloitte’s 2026 Global Human Capital Trends report. That kind of consensus rarely shows up in a boardroom, which makes the gap underneath it worth paying attention to: wanting to be agile and actually being built for it are two very different things.

Deloitte’s research also found that 66% of C-suite leaders believe their traditional HR, finance, and legal functions need to change to keep pace with the business, yet only 7% say they are making progress toward that goal. That distance between what leaders know needs to happen and what is happening is where most agility initiatives quietly stall out, usually without anyone ever officially calling them dead.

This isn’t happening because people aren’t trying. Employees are already absorbing an enormous volume of organizational change, and Deloitte found that a third of them experienced fifteen or more major changes at work in the past year alone, from reorganizations and new tools to shifting reporting lines and AI folded into daily workflows almost overnight. The volume of change is real, and what most organizations are missing isn’t effort or urgency, it’s the structural capacity to absorb that much change without something important breaking along the way.

The Infrastructure Gap Nobody Budgets For

Most companies treat agility as leadership behavior, something built from faster decisions, flatter approvals, and more delegation. Structurally, though, agility depends on something far less glamorous than any of that: a job architecture that actually reflects how work gets done today rather than how it was designed several reorgs ago.

Mercer’s Job Architecture Pulse Survey found that 76% of U.S. organizations have some form of job architecture already in place, but only about 20% have built skills into that framework, and fewer than half say their current structure genuinely meets the needs of the business. In other words, most companies are navigating with a map that stopped matching the terrain a while ago, and few have noticed just how far off it has drifted.

That gap carries a measurable cost rather than just a theoretical one. The same Mercer research found that organizations whose job architecture fully supports the business deliver, on average, roughly 5% higher annual shareholder return than organizations working from an outdated structure, which is a strong argument that structure isn’t overhead so much as it is return on investment hiding in plain sight.

AI is widening that gap rather than closing it, mostly because organizations are applying it to a foundation that was never built to hold it. Deloitte’s 2026 research found that 59% of organizations are simply layering AI onto legacy systems and job structures instead of rethinking how roles, skills, and decision rights actually work now, an approach that can look impressively fast in the short term but tends to get expensive quickly, showing up later as pay inconsistency, unclear leveling, and roles nobody can define cleanly enough to hire against, promote into, or benchmark with any confidence.

Where This Stops Being an Efficiency Problem and Becomes a Legal One

Loose job architecture used to be a problem you could quietly clean up on your own timeline, but that window has mostly closed. As of 2026, roughly 18 states plus Washington, D.C. require some form of pay transparency in job postings or upon request, and that number keeps climbing every legislative session. Once compensation ranges are public, inconsistent job leveling and undocumented pay logic stop being something you fix eventually and start being something a candidate, an employee, or a regulator can see the moment a range gets posted.

“Speed without structure isn’t agility,” says David Turetsky, founder and CEO of HR Data Labs. “It’s just faster chaos. The organizations winning right now aren’t the ones making the quickest decisions, they’re the ones whose job architecture and compensation data are solid enough that fast decisions hold up once someone else starts asking questions.”

What Agile Infrastructure Actually Looks Like

None of this is an argument for slowing down. It’s an argument for building the parts that let speed hold up once it’s under real pressure, which usually comes down to a short list of fundamentals most organizations have let slide:

  • Job architecture that reflects the work as it actually exists now, not as it was designed several reorgs ago
  • Skills mapped directly to roles, rather than bolted on afterward as a separate initiative
  • Compensation bands built on current data, not whatever benchmarking cycle happened to be current two years ago
  • A single source of truth for role and pay data that can survive contact with a pay transparency audit without anyone scrambling

Companies with this in place can restructure, redeploy, and respond to AI-driven change without guessing their way through it. Companies without it are making fast decisions on a foundation that was never built to hold the weight, and the bill for that tends to come due later, usually at the worst possible moment.

If your organization is chasing speed without knowing whether your job architecture and compensation strategy can support it, that gap is worth a conversation before it becomes a much bigger problem. Book a call with HR Data Labs.

Leave a Reply

Your email address will not be published. Required fields are marked *