What Relational Change Management Actually Is — And Why We Built It Instead of Importing One

There is a moment in most change initiatives that nobody writes down.

The plan is sound. The framework is credentialed. The steering committee has signed off, the communication cascade is scheduled, and the training calendar is booked. And then somebody senior says, in a hallway, to one other person: hindi ito uubra dito. This won't work here.

That sentence never makes it into a status report. But it travels. And six months later, when adoption numbers are flat and the initiative is quietly described as "on hold pending realignment," that hallway conversation turns out to have been the most accurate piece of analysis anyone produced.

Relational Change Management exists because of that gap — the distance between what a framework assumes about how organizations decide, and how they actually decide.

The frameworks are not the problem

Let's be clear about what this is not.

This is not an argument that ADKAR is wrong, or that Prosci is a Western import to be discarded in favor of something home-grown. Those frameworks are rigorous. They were built on real research, refined across thousands of engagements, and they describe something true: that change happens one person at a time, through awareness, desire, knowledge, ability, and reinforcement.

The problem is not the model. The problem is the delivery assumption sitting underneath it.

Most change management consulting applies these frameworks exactly as written, regardless of who is on the other side of the table. And as written, they tend to assume a particular kind of organization: one where decisions move down a chain of command, where individual accountability is the primary lever, and where "securing sponsorship" means getting a signature from the person at the top.

Plenty of organizations work that way. Many Filipino organizations do not.

What actually happens instead

Consider a cooperative. A new direction does not take hold because the board approved it. It takes hold when the General Assembly reaches genuine consensus — and consensus is not a vote you win, it is a state you build. The decision-making structure is the stakeholder engagement process. There is no separate step where you go and get buy-in afterward, because the buy-in is the mechanism.

Consider a government agency. The approval path runs through layers of stakeholders, each with legitimate accountability to the public. The person who can formally authorize the change is often not the person who can actually make it stick, and neither of them is the person who will quietly determine whether the new process gets used or worked around.

Consider a private enterprise mid-migration. On paper it is the fastest-moving of the three. In practice, the technically sound rollout stalls for reasons that never appear in the risk register — because the team lead who everyone actually listens to was never consulted, and hard feedback got softened at every level until it disappeared entirely on the way up.

In all three cases, the framework was fine. The framework was just being applied to an organization it had never been introduced to.

Pakikipagkapwa and bayanihan, as working concepts

Two Filipino concepts do real analytical work here, and it's worth being precise about them rather than treating them as decoration.

Pakikipagkapwa is the shared sense of identity that shapes how Filipinos relate to one another — the recognition of the other person as fundamentally not separate from yourself. In organizational terms, this is why individual-accountability models often underperform here. A change that asks someone to adopt a new behavior at the cost of their standing within their group is not a training problem. It is a relational cost, and people will pay it far more slowly than any adoption curve predicts.

Bayanihan is the spirit of collective effort — the practice of moving something heavy by having everyone lift at once. It is usually invoked as a nice cultural value. Treated properly, it is a design constraint: if the change requires collective lift, then sequencing it as a series of individual behavior changes is working against the strongest force in the room instead of with it.

Relational Change Management grounds ADKAR and Prosci in these two realities. Awareness and desire still matter — but awareness travels through relationships, not through cascades, and desire is shaped by what your kapwa think of the choice. Reinforcement still matters — but it holds when the group holds it, not when a dashboard tracks it.

Where this came from

None of this was designed in the abstract.

It came out of over fifteen years of hands-on change management and organizational transformation work across healthcare, education, technology, and government — including a large-scale telecom system migration where the same pattern kept surfacing at scale. Well-credentialed frameworks, competent teams, sound strategy, and a persistent gap between the plan and the way decisions were actually being made.

The same pattern appeared again in the public sector, supporting disaster risk reduction and emergency preparedness for the City of Makati — where systems had to function under real crisis conditions, not just on paper. And again in education, leading Project Alpha, AC Education's acquisition of the University of Nueva Caceres, then guiding the university's Planning and Analytics function through the transition that followed.

Different sectors, different stakes, same recurring gap. At some point it stopped looking like a series of individual project frictions and started looking like a structural problem with how the frameworks were being applied.

What it looks like in practice

The methodology runs in four stages, and the relational grounding shows up in each one.

Assess. We map how your organization actually makes decisions — not what the org chart says. That means stakeholder mapping that identifies informal influence alongside formal authority, an honest read on change fatigue from initiatives that stalled before, and direct conversations about where the last one broke down.

Design. The strategy is shaped around that real decision-making structure from the start. If consensus is your mechanism, the plan is built for consensus rather than retrofitted for it after a top-down approach stalls. Communication plans, training, and success metrics are defined upfront and matched to how information actually moves through your organization.

Implement. Change rolls out in phases, with stakeholder engagement running continuously rather than concentrating at the announcement. This is the stage where standard frameworks most often stop.

Sustain. The work does not end at go-live. We build in continuous improvement and internal capability, so the change holds after the engagement ends — which is the only test that actually matters.

The point

Change management fails less often because the strategy was wrong, and more often because the plan never accounted for how people actually decide and adapt.

Relational Change Management is not a rejection of proven methodology. It is proven methodology, delivered to the organization that is actually in the room — one that decides relationally, collectively, and often through consensus, and that deserves a strategy built for that rather than one imported wholesale from somewhere else.

The result is change that gets adopted, not just announced.

If your organization is planning a transformation, or already in the middle of one, let's talk about what Relational Change Management could look like for you. Schedule a Consultation →