Who owns the gap?

Why distributed ownership must not mean vague accountability, and the governance system that turns human evidence into organisational response Every Promise Gap conversation eventually reaches the same question.

Who owns it?

The easy answers are also the wrong ones.

Employer brand owns the promise, so give it to employer brand.

People and culture owns employees, so give it to HR.

Managers create the experience, so make managers accountable.

Or create a cross-functional working group, which is often where ownership goes to become collective, polite and optional.

The problem is that the Promise Gap crosses every boundary those answers rely on.

The promise may be written by marketing or talent. The onboarding moment may be enabled by HR technology. The roster belongs to operations. The difficult conversation belongs to a manager. The departure data sits in a dashboard. The customer consequence sits somewhere else again.

No single function can deliver the whole experience. That does not mean nobody can own the system.

Ownership and stewardship

The first distinction is between owning the promise and personally delivering every proof of it.

An enterprise promise belongs to the organisation. It is a commitment made in the organisation’s name.

A central function can steward that promise. Stewardship means protecting its integrity, translating it into practical standards, maintaining the promise inventory, connecting evidence and challenging contradictions.

Depending on the organisation, the steward may sit in people experience, employer brand, organisational development, strategy or a cross-functional experience office.

But the steward cannot personally keep the promise in thousands of daily moments.

Operational leaders own the conditions around those moments. Managers and teams bring them to life. Systems either enable or obstruct them. Executive governance decides what receives attention, authority and investment. Distributed delivery requires explicit accountability.

A five-part governance model

The enterprise owns the promise. This means senior leadership accepts that the EVP, values and change commitments are organisational obligations, not campaign language. The promise is approved with awareness of what keeping it requires.

A central steward protects integrity. The steward maintains the architecture: promise inventory, segment translations, moment maps, evidence standards and the overall view of where gaps are opening. The steward does not become the owner of everyone else’s actions.

Operational leaders own critical moments. Every priority moment needs a named business owner: offer-to-start, first fortnight, flexibility request, development decision, change communication, recognition, departure. Ownership means authority to change the conditions, not simply responsibility for a score.

Leaders and managers bring the experience to life. The organisation designs the scaffolding. Leaders and managers interpret the promise in real situations. They need capacity, capability, information, permission and clear escalation routes. Accountability without those conditions is theatre.

Evidence triggers organisational response. Employee voice, behavioural data, workforce outcomes, customer evidence and financial consequences must meet in a review rhythm that ends with a decision. Evidence without response becomes another broken promise.

The missing actuator

Many organisations already possess most of the sensors.

Engagement surveys. Exit data. Reviews. Attrition dashboards. Customer complaints. Safety reports. Recruitment metrics. Manager feedback.

What is missing is the actuator: the mechanism that converts a recognised gap into a changed condition.

A useful governance meeting therefore does not ask only, “What does the data say?”

It asks:

Which promise is implicated?

For which group?

At which moment?

What evidence supports the diagnosis?

Who owns the condition producing it?

What decision is required?

How will we know the gap narrowed?

That sequence connects voice to accountability and accountability to action.

A practical Promise Gap register

The work can be made visible in a simple register.

Promise: what commitment is being tested?

Segment: whose experience is most affected?

Moment: where does the gap open?

Evidence: what quantitative and qualitative signals support the finding?

Owner: who has authority over the condition?

Response: what will change, by when?

Outcome: what workforce, service or business indicator should move?

Status: kept, at risk, broken or being repaired.

The register is not meant to turn experience into bureaucracy. It prevents the opposite problem: powerful human evidence being discussed repeatedly without acquiring an owner.

The role of technology

Technology can connect evidence, automate journeys and make moments more consistent. It cannot resolve unclear ownership.

An onboarding workflow can send the welcome message. It cannot make a manager care.

A listening platform can identify a theme. It cannot decide which operating condition changes.

An AI summary can surface a pattern. It cannot carry accountability.

Technology is part of the scaffolding. Governance determines what the organisation does with what the technology reveals.

The counterargument: this sounds heavy

A governance model can easily become another layer of meetings, templates and central control. The concern is valid.

The solution is to govern only the promises and moments that matter most.

Start with a small portfolio: perhaps five enterprise commitments, three priority workforce groups and six critical moments. Use existing leadership rhythms wherever possible. Add sharper questions, not another committee.

The purpose is not to centralise every decision. It is to make sure significant contradictions between promise and experience cannot remain ownerless.

The sentence to keep

Distributed ownership must not mean vague accountability.

The enterprise owns the promise. A steward protects it. Operational leaders own the conditions. Managers bring the moments to life. Evidence shows where belief is breaking. Governance ensures the organisation responds. That is how the Promise Gap moves from an idea to an operating system.

Shehzad Bhanji writes The Promise Gap, a weekly perspective on the relationship between organisational promises and lived experiences. Across a 25-year international career spanning marketing, customer experience, employer brand, HR technology and people experience, he has worked across Australia, Asia, Europe, the Middle East and Africa.