Why Cooperatives Can't Be Changed by Memo

A cooperative general manager once described a failed initiative this way: the board approved it, so I thought we were done.

They were not done. They were, at best, one-third of the way through a process they had mistaken for the end of one.

This is the single most common structural misunderstanding in cooperative change management, and it is not a competence problem. It is what happens when you apply a framework built for hierarchical organizations to an organization that is, by design and by law, not hierarchical in that way.

(For the broader methodology this piece sits inside, see What Relational Change Management Actually Is.)

The structure is the point, not an obstacle

In a Philippine cooperative, the General Assembly is the highest policy-making body. Members vote on the principle of one member, one vote — regardless of how much share capital they hold. The board is elected by and accountable to that assembly. This is not incidental to how a cooperative works; it is what makes it a cooperative rather than a corporation with friendly branding.

Standard change frameworks are built around a different picture. They ask you to secure executive sponsorship, cascade communication downward, and manage resistance among the people receiving the change. All three of those instructions assume the decision has already been made somewhere above the people being managed.

In a cooperative, the people you would classify as "affected stakeholders" under a standard framework are the same people who hold the deciding vote. They are not downstream of the decision. They are the decision.

Which means the usual sequence — decide, then communicate, then manage resistance — is not just suboptimal here. It is inverted.

Three places cooperative change actually stalls

Across engagements, the failures tend to cluster in the same three places.

Treating the board vote as the finish line. Board approval means you have permission to begin building consensus. It does not mean consensus exists. Initiatives that treat it as a mandate arrive at the General Assembly having done no relational groundwork, and are then genuinely surprised when the floor pushes back.

Bringing the proposal to the assembly fully formed. There is an instinct, borrowed from corporate practice, to arrive with the polished deck and the finished plan. In a consensus-driven body this reads as a decision already made, presented for ratification. Members who had no hand in shaping it have no stake in defending it — and in a room governed by pakikipagkapwa, the person who objects first gives everyone else permission to agree with them.

Mistaking silence for agreement. This is the expensive one. In many Filipino organizational settings, open disagreement with a leader in a public forum carries real social cost. A quiet General Assembly is frequently not a supportive one. It is a room that has decided the conversation will happen elsewhere, later, without you — and that conversation is where your adoption rate is actually being determined.

Designing for consensus from the start

Relational Change Management approaches this by building the strategy around the General Assembly process rather than around it. In practice that looks like four shifts.

Map influence, not just authority. The elected officers are visible. The members whose opinion moves a room — the long-tenured member, the barangay-level organizer, the one whose family has been in the co-op for three generations — usually are not on any chart. Assessment work identifies both, because only one of those groups can formally approve the change and only the other can make it survive.

Build consensus before the assembly, not during it. Consensus is constructed in smaller, lower-stakes settings where disagreement is socially affordable: committee discussions, chapter meetings, informal conversations with members who will be asked to speak. By the time the proposal reaches the floor, the objections should already be known, already addressed, and ideally already voiced by someone other than management.

Bring an unfinished proposal on purpose. Arriving with a genuine open question — one where member input will visibly change the outcome — converts the assembly from an audience into a co-author. This costs some control over the final design. It buys ownership, which is the thing that determines whether anyone follows the new process in month seven.

Surface disagreement deliberately. Someone has to create the conditions where hard truths can be said without anyone losing face for saying them. That means structured opportunities for dissent, and management publicly receiving criticism without defensiveness the first time it happens — because the room is watching to see what happens to the first person who speaks.

What this is not

It is not slower, in the way people assume. It front-loads time into assessment and pre-assembly consensus-building, and it saves the far larger amount usually spent re-litigating a stalled initiative that was announced before it was agreed.

It is not the absence of a framework. ADKAR and Prosci still structure the work — awareness, desire, knowledge, ability, reinforcement all still have to be built. What changes is the delivery mechanism: awareness travels through relationships rather than cascades, and reinforcement holds because the collective holds it.

And it is not only for cooperatives. Any organization that decides collectively rather than through a single chain of command has the same underlying dynamic — a professional partnership, a mission-driven NGO with an engaged board, a government agency where genuine authority is distributed across several offices. The General Assembly is simply the clearest and most formalized version of a pattern that shows up in many Filipino organizations.

The test

The question worth asking before any cooperative change initiative is not have we secured approval.

It is: if this were put to a vote today, with no further preparation, would it pass — and would the people who voted yes still be following it a year from now?

If the answer to either half is uncertain, the work is not yet ready for the floor. That is not a delay. That is the change management.

If your cooperative is planning a transformation, or already mid-initiative and struggling to gain real adoption, let's talk about what Relational Change Management could look like for you. Schedule a Consultation →