Five Coordination Mistakes CPO Groups Make (And How to Avoid Them)

CPO groups do not typically fail because their members do not care enough, or because the housing market makes it too difficult, or because the planning system is too slow. They fail because of coordination problems that were predictable and, in most cases, preventable. After watching a number of initiatives progress from early enthusiasm through to either stall or success, certain patterns appear consistently enough to be worth naming clearly.

These are not exotic failure modes. They are the ordinary mechanics of collective decision-making under conditions of unequal information, diffuse accountability, and high personal stakes. Understanding them early — before they arrive — is the primary value of having any kind of structured process.

Mistake 1: Deferring the Programme Conversation

The most common early mistake is to spend the first six to twelve months of group life discussing values and vision without translating those into a concrete spatial programme. Groups talk about sustainability, about community, about how they want to live. These conversations matter. But at some point the group needs to answer specific questions: How many units? What size range? What shared spaces, and how large? What is the target budget per m² of gross floor area?

The reason groups defer this conversation is understandable — the specific answers require commitment, and commitment before a site is identified can feel premature. But the alternative is worse. Groups that arrive at site selection without a clear programme have two problems: they cannot evaluate whether a given site actually fits their ambitions, and they are likely to discover deep disagreements about programme at precisely the moment when those disagreements are most costly to resolve — after the site is allocated.

A useful discipline is to produce a provisional programme document early, clearly labelled as provisional, with explicit decision points identified where the programme will be revisited as more becomes known. This is different from the group trying to lock down every detail before they have a site. It is about making the group's ambitions legible enough to use as an evaluation tool.

Mistake 2: Shared Cost Rules That Are Not Rules

Most CPO groups reach a rough agreement about shared costs at some point during the formation phase. Shared outdoor space, shared infrastructure, perhaps a community room or bicycle storage. The problem is that "rough agreement" is not the same as a binding rule with an enforcement mechanism.

What typically happens is this: early in the project, when shared spaces are abstract, everyone agrees in principle. As the design develops and the costs become concrete, some members discover that the shared space they were imagining (a large communal garden, a workshop space) is more expensive than they had assumed, while others decide they do not actually want or need it. At this point, the "agreement" breaks down into negotiation, and the negotiation is happening against a design that has already been developed on the assumption that the shared space is in the programme.

The fix is to establish the cost-sharing rules — including how shared costs are allocated per unit, and what process applies when a member wants to opt out of a shared element — as formal rules in the member charter, decided before the design phase begins. We are not saying that the rules have to be rigid or that they cannot evolve. But "we will work it out when we get there" is not a rule; it is an invitation to conflict at the worst possible time.

Mistake 3: No Protocol for Member Exit

Over a project that runs three to five years, member exits are not exceptional — they are statistically probable. A household's circumstances change: a job relocation, a relationship change, a financial shift that makes the project no longer viable for them. This is not a failure; it is life. The failure is not having a protocol to handle it.

A member exit without a protocol creates several cascading problems. The exiting member's share of the project cost needs to be redistributed or covered. Their position in the group (one household's worth of programme, one vote in decisions) needs to be filled or retired. And the timing of the exit matters enormously: a member exiting before site allocation is different from one exiting after the construction contract is signed.

A well-drafted member charter will specify what happens at each stage: what financial obligations a departing member has, what the group's obligation is to find a replacement versus absorb the cost, and what the timeline is for transition. A CPO group that a growing community in the Noord-Holland region has been assembling since mid-2025 handled a mid-process exit cleanly because they had specified, before anyone joined, that a member wishing to leave would have a three-month window to find a replacement household acceptable to the group, with a staged refund of their deposit if no replacement was found. It was uncomfortable when it happened; it was not a crisis.

Mistake 4: Informal Decision-Making

Small groups tend to operate informally, and there is real value in that. But "we will discuss it at the next meeting and see where we land" works well for low-stakes decisions and breaks down for high-stakes ones. Design changes with cost implications, changes to the agreed programme, decisions about which contractor to select — these require a clear decision-making process with a defined quorum and a clear record of the outcome.

The problem with informal decision-making is not that it produces bad decisions, but that it produces contested ones. When two group members later remember the "decision" differently, and there is no written record, the group is back at square one. In CPO, where a single decision can have consequences for construction cost and timeline, contested decisions are expensive.

The fix is straightforward: every meeting that makes a material decision should produce a written record of the decision, who voted, and what the outcome was. This does not require elaborate governance apparatus — a shared document with dated entries is sufficient. The discipline of writing it down is itself useful, because it forces a degree of clarity about what was actually decided.

Mistake 5: Treating the Architect Brief as the Programme

This is a subtler mistake than the others, and it appears consistently in groups that have otherwise done everything right. The architect brief — the document that the group hands to the architect at the start of the design phase — is a technical instruction. It specifies the programme in terms of unit count, sizes, shared spaces, and performance targets. It is not the group's shared vision document, and it is not a sufficient basis for the internal alignment the group needs to maintain cohesion through the design process.

When the architect produces first sketches, members react to them with mental models formed long before the brief was written. The member who was imagining a courtyard house discovers the design has a linear corridor plan. The member who assumed ground-floor units would have direct garden access finds that the site topography makes this impossible. These reactions are not failures of the architect — they are gaps between the brief and the unstated assumptions members brought to it.

Good pre-design work — a shared programme document that includes spatial preferences, section sketches, reference images, and explicit discussion of what the group will and will not trade off — dramatically reduces the number of these surprises. We are not saying groups need to be architects before they hire one. The point is that the group's internal alignment needs to be explicit and documented, not assumed, before the design process begins. Groups that invest in this stage find the design phase faster, cheaper, and less contentious than those who arrive at first sketches with unexamined assumptions.

The Pattern Behind the Patterns

Looking across these five mistakes, the underlying pattern is the same: deferred clarity. Each mistake involves a group choosing not to resolve an ambiguity when it first appears — because resolution requires commitment, because conflict is uncomfortable, or simply because the group does not yet have a structure for resolving it. The ambiguity then resurfaces at a later stage, when the cost of resolving it is much higher.

The antidote is not heavy process. It is timely process — the right decisions made at the right stage, with a clear enough structure to make them stick. CPO groups that build this in from the start spend less time in crisis management and more time actually building.