Aligned to What? Strategy as the Reference Point

Alignment assumes a reference point. Before any framework can tell you something useful, there has to be a stated version of what the organization is trying to achieve, because diagnosis on its own only produces a comparison.

Mapping a process surfaces the gap between what people believe is happening and what's actually happening. That gap becomes a finding only when you can say which version is closer to what the organization needs. Without that, the output is an inconsistency, accurately documented and impossible to act on, because nothing in it tells you which side should change.

Strategy in the Practical Sense

The standard comes from strategy, meaning the practical version rather than the aspirational one. It's the set of outcomes the organization committed to when it decided to invest in the platform: reducing the manual effort in payroll, giving managers the ability to act without routing every request through HR, shortening time to hire, producing reporting that leadership will use to make decisions rather than to confirm what they already believe.

Most organizations wrote these down during the business case. Most stop referring to them shortly after go-live. The business case gets built to secure funding, and once the funding is secured it stops being a working document. Nobody revisits it during design sessions, nobody checks configuration decisions against it, and nobody asks at go-live whether the outcomes it promised were actually delivered.

That's how a system ends up supporting processes nobody would design today, satisfying requirements nobody remembers agreeing to.

The Simpler Version

Underneath those objectives is a simpler statement of what the organization is actually trying to achieve: the right people, in the right positions, doing the right things.

The right people means the skills the organization needs rather than the ones it happened to hire for. The right position means those skills sit where they do the most good. The right things means the work in front of someone uses what they're actually good at.

When all three hold, the arrangement compounds on itself. The organization gets the benefit of people doing work they're suited to and want to do, and those people tend to stay, which means the capability the organization built stays with it. When one of the three breaks, the others absorb it for a while. Someone in the wrong position does adequate work by effort rather than fit. Someone with the right skills spends most of their week on things that don't use them. Neither situation announces itself, and both are expensive in ways that don't appear on any report.

HR technology exists to make that arrangement visible and maintainable at scale. The operational objectives sit downstream of it, and they're worth measuring precisely because they indicate whether the arrangement is holding.

What Happens Without a Reference Point

When strategic intent is unclear or contested, process mapping still produces a picture, and there's no basis for judging what it shows. Every function can describe its own work accurately, and every description is defensible, so the assessment turns into a negotiation rather than an analysis.

What fills the vacuum is proximity and persistence. Teams optimize toward whatever the most persistent function is asking for, or toward whoever has the shortest path to the executive team. The operating model drifts, and nobody makes a decision to change direction, because no decision was ever framed as a choice.

The same thing happens to enhancement backlogs. Without a stated set of outcomes to prioritize against, items get ranked by who asked most recently or most loudly. The backlog becomes a record of requests rather than a plan.

It shows up during the project itself, too. Issues surface, scope changes get proposed, and the conversation runs entirely against the timeline and the budget. Almost nobody reopens the strategy to ask whether the change still serves what the organization said it was doing. That question is available at every decision point and it rarely gets asked, because the timeline is concrete and sitting on a slide in front of everyone, while the strategy is in a document somebody wrote nine months ago.

The Cost People Absorb

The rest of it shows up in people rather than in the tenant.

People resist what they don't understand. Without a stated reason, a change looks arbitrary to whoever has to absorb it. Being asked to work differently is a reasonable request. Being asked to work differently for reasons nobody can articulate is a different request, and it gets a different response.

What follows is quieter than open resistance. Someone raises a concern, nothing comes back, and they raise fewer of them next time. Eventually they stop. What reads as acceptance in the room is often someone who has mentally checked out and is waiting for the project to be over. That person is still on the team after go-live, still holds the knowledge, and no longer volunteers any of it.

This is the part that doesn't recover on its own. Configuration can be corrected. Someone who spent nine months being told their concerns were a threat to the timeline takes considerably longer.

Getting the Reference Point Back

Four things make strategy usable rather than decorative.

Write down the outcomes in terms someone can verify

Reducing manual effort in payroll is a direction. Reducing the number of off-cycle corrections is a number somebody can check. The second one can be wrong, which is what makes it useful.

Revisit them on a schedule, not on an incident

Most organizations only reopen the business case when something has already gone badly. Reviewing the stated outcomes annually, against what the tenant actually does now, catches drift while it's still cheap.

Assign them an owner

An outcome nobody is accountable for behaves like an outcome nobody agreed to. That role doesn't need to sit in HRIS, and in most organizations it shouldn't.

Make it specific enough that people can find themselves in it

A strategy stated at the level of the organization gives an individual nothing to act on. Someone running payroll operations, or a manager approving requests, has to be able to see which part of it depends on them. Buy-in follows understanding, and understanding requires enough specificity that the connection is visible without anyone having to interpret it.

Don't sell a dream. Make it a reality people can see their part in.

Where This Fits

Strategy sets what good looks like. Process is where you find out whether the organization is achieving it. Technology and people are where the correction usually lands.

That sequence runs one step further back than the three layers suggest, and it's why diagnosis can still start at the process layer. Process is where intent and reality separate visibly. Strategy is what tells you which one to trust.

The full framework is covered in People, Process, Technology: The Alignment Framework Every HR Leader Needs.

How CRG Approaches This

We start by asking what the organization said it was trying to achieve, and whether anyone has looked at that statement since the business case was approved. The answer to the second question usually explains more than the first one does.

Talk to CRG about the reference point your HR technology is measured against.