Your Policy Was Implemented. But Did It Produce the Experience?
A decision can be fully implemented and still fail.
The policy was distributed.
The training was completed.
The new process launched.
The boxes were checked.
The dashboard turned green.
Everything says done.
So leadership calls it a success.
But implementation only proves that something happened.
It doesn’t prove that the organization produced the experience it promised.
Implementation Is Not the Same as Impact
Organizations are very good at measuring activity.
We know how many people completed the training. How many managers acknowledged the policy. How many candidates entered the interview process. Whether the initiative launched on time.
Those numbers matter.
But they answer one question:
Did we do what we said we were going to do?
They don’t necessarily answer the harder one:
What happened because we did it?
A leadership-development program can reach 100% completion while employees still don’t have meaningful opportunities to grow.
A reporting process can be fully operational and employees still be afraid to use it.
A hiring policy can meet its representation target while candidates experience a performative process.
A manager can follow every documented step and still undermine the purpose of the decision.
Everything can look right on paper.
And still feel very different to the person on the other side of it.
Where the Intended Experience Begins to Change
A leadership decision rarely moves directly from intention to outcome.
It travels.
INTENT → TRANSLATION → EXPERIENCE
Intent is what leadership meant to accomplish.
Usually, that part is clear in the room where the decision is made. People understand the problem. They debate the options. They know why the decision matters. And they put a lot of thought into it.
Then the decision leaves the room.
And that’s where things get interesting.
Someone has to communicate it.
Someone has to interpret it.
Someone has to resource it.
Someone has to manage it.
Someone has to make a judgment call when the written policy doesn’t quite fit what is happening in front of them.
That’s translation.
And translation is where much of the distance between what leadership intended and what people eventually experience is created.
A manager reads the policy and decides what it really means.
A system rewards one behavior while the policy asks for another.
A deadline creates pressure the original decision never accounted for.
An unofficial norm becomes more powerful than the official process.
Eventually, all of that reaches someone.
The candidate sitting in the interview.
The employee deciding whether it’s actually safe to report something.
The manager trying to determine what leadership really expects.
The employee who completed the training and is waiting to see whether anything changes afterward.
That’s experience.
What survives translation becomes someone’s reality.
And here’s where leadership often gets into trouble or misses opportunity:
We inspect the beginning and the end.
We confirm the intent.
We approve the decision.
We review the outcome.
But we don’t always inspect what happened in between.
Then the outcome disappoints us, and we start looking for someone to blame.
By then, the failure may have been traveling through the organization for months.
That distance between what leadership intended and what people actually experienced is what The Experience Check™ is designed to examine.
The Person–Leader–System Question
When something goes wrong, one of the easiest questions to ask is:
Who messed up? Who didn’t follow the process?
Who needs more training? Who needs coaching?
Who should be held accountable?
Sometimes that is exactly the right question.
People have agency. Judgment matters. Integrity matters. Performance matters.
But if that’s the only question leadership asks, the diagnosis is incomplete (and so may be any solution implemented at that point).
The PLS Framework™ examines three connected perspectives:
Person — What did the individual understand, decide, and do?
Leader — What did leadership communicate, reinforce, inspect, and tolerate?
System — What did the structure measure, reward, discourage, or make possible?
Because sometimes a person makes a poor decision.
And sometimes a person makes a predictable decision inside a system that quietly taught them to make it.
A manager may technically comply because leadership has made the metric more important than the purpose.
An employee may follow the unofficial norm because experience has taught them that doing otherwise comes with a cost.
A strong initiative can lose its meaning one translation at a time.
So yes, hold people accountable when accountability is warranted.
But don’t discipline a symptom and congratulate yourself for solving the problem.
If the conditions that helped produce the behavior remain untouched, don’t be surprised when the same problem shows up wearing a different name badge.
Diagnosis must come before prescription.
Why What People Experience Matters to the Business
This is the danger of relying too heavily on completion metrics.
A dashboard can tell you that the organization did what it said it would do.
It cannot always tell you what became true for people because of it.
And eventually, what becomes true for people becomes true for the business.
If employees complete leadership training but managers don’t lead differently, performance doesn’t improve.
If employees receive a reporting policy but don’t trust the system enough to use it, risk doesn’t disappear. It goes underground.
If a hiring process meets its targets but candidates experience it as performative, the organization may check the representation box while damaging trust, reputation, and its ability to attract talent.
If employees repeatedly encounter systems that make it harder to do good work, eventually that shows up somewhere else: productivity, turnover, quality, customer experience, cost, or organizational risk.
The system does not stop affecting the organization simply because leadership hasn’t diagnosed it.
An unaddressed system problem eventually becomes a business problem.
That’s why implementation metrics aren’t enough.
The better question isn’t:
“Did we implement it?”
It’s:
“What became true for people after we implemented it — and what did that make true for the business?”
Did employees gain access to development — or merely attend training?
Did candidates receive equitable consideration — or merely appear on an interview slate?
Did staff gain a reporting channel they trusted — or merely receive another policy?
Did managers change their behavior — or merely acknowledge the expectation?
And then:
What happened to performance?
What happened to retention?
What happened to trust?
What happened to risk?
What happened to the organization’s ability to deliver?
Those are not separate conversations.
The employee experience is happening inside the same system producing the business outcome.
So when the experience repeatedly fails, leadership shouldn’t be surprised when the numbers eventually tell the same story.
A green implementation dashboard can coexist with a business problem already growing underneath it.
The Experience Check™
The Experience Check™ is a practical leadership field tool designed to help leaders discover what actually happened after a strategy, initiative, policy, or leadership commitment left the room where it was created.
It examines the distance between:
What leadership intended
What happened as that intent moved through translation
What people actually experienced
The outcome those experiences ultimately produced
This isn’t an invitation to distrust every decision.
It’s an invitation to stop treating implementation as proof that a decision worked.
Strong leadership isn’t proven because something launched on time.
It’s demonstrated by staying accountable for what the decision becomes after it leaves the executive table.
So before you call the next policy, program, or strategy a success, ask one more question:
Did we complete the process — or did we produce the experience we promised?
Those are not the same accomplishment.
And your dashboard may not know the difference.
On Thursday, I’m putting a real workplace-standards decision under the microscope — one involving a national brand’s stated commitments and what can happen when those commitments have to travel through a structure the organization does not fully control.
Run the Experience Check™ with your organization →
Stay Connected
If this perspective challenged your thinking or gave you a new way to diagnose the issue, I'd love to continue the conversation.
Follow me on LinkedIn for executive insights on leadership, organizational culture, and people strategy.
Explore more Insights to deepen your thinking around The Third Perspective™ and the PLS Framework™.
Looking for a speaker, executive advisor, or strategic thought partner? Let's connect.
Kimberly D. Sanders
Creator of The Third Perspective™ • Diagnosing before prescribing.
