Who Decides? Designing Shared Authority for Your Partner Network

There's a question every growing partner network eventually asks, and the founder is always the last to hear it: who actually decides things around here? In the early days nobody asks, because the answer is obvious — you do, and everyone is fine with that. You recruited each partner personally. You talk to all of them. Disagreements get sorted in a single conversation.

Then the network grows, and the question stops being rhetorical. Partners want to know why a pricing change happened without their input. They want a process for challenging a decision they disagree with. They want to understand why one colleague seems to have a private line to you that others don't. When the answer to "who decides?" is still "the founder, informally," the question curdles into resentment.

This is the moment to introduce shared governance: a small elected Partner Council that holds real decision-making authority alongside you, across domains you've defined in writing. The structure is simple. The timing and the boundaries are where founders get it wrong — so let's start with the warning signs, then work through the design.

The Warning Lights Before the Breakdown

Informal rule doesn't fail all at once. It frays. Watch for these signals that the handshake model is reaching its limit:

• Backlash to a decision nobody was asked about. Several partners push back on something you decided alone — not because the call was wrong, but because they were never consulted.
• A partner-versus-partner dispute lands on your desk and whatever you rule feels arbitrary, because there's no agreed process behind it.
• Issues travel through private back channels instead of community forums. When partners lobby you one-on-one rather than raising things openly, informal power dynamics have already taken root.
• Headcount crosses roughly 25-30 active partners — the rough point where personal relationships can no longer do the work of formal structure.

In practice these signals tend to cluster. A methodology disagreement escalates with no resolution path. A new cohort arrives and veterans feel their views on selection were ignored. None of it is a crisis on its own. Together, it's a vacuum where authority should be.

"A governance vacuum never stays empty. Either you fill it with a structure everyone can see, or it fills itself with influence nobody voted for."

Why the Handshake Model Has a Ceiling

Three Forces That Arrive With Scale

A network of 12 governs itself through social pressure. Everyone can see everyone else's reputation, free-riding gets spotted, and the unwritten expectation to contribute and uphold the methodology does the job that rules would otherwise do. A network of 40 has lost that mechanism, for three reasons that reinforce each other.

First, partners become strangers to each other. Past a certain size, most members have never worked alongside most other members. A partner whose delivery quality is slipping won't be caught by peer visibility, because the peers aren't looking. Standards drift unevenly across the community unless someone formally monitors them.

Second, founder decisions lose their legitimacy. In a dozen-person group, the founder deciding everything reads as collaborative leadership — first among equals. In a forty-person group, the identical behavior reads as rule by decree, even when every individual call is sound. The questions start: who made this decision, on what basis, and how do I change it?

Third, unelected influence fills the gap. Without designed governance, sway accrues to the most persistent, the most charismatic, or whoever lobbies you most effectively in private. Most partners can't see these dynamics — but the ones on the losing end feel them acutely, and the moment a partner realizes a colleague has special access to the founder, trust in the whole system drops.

Formal governance won't abolish politics. What it does is force politics into the open, with named roles and visible processes. Partners can see who holds which authority, how a decision gets made, and where to push if they want change. That transparency matters more than the outcome of any single decision the council will ever take.

The Authority Map: Two Columns, No Gray Zones

Write the Charter Before You Elect Anyone

Before you think about who sits on the council, decide what the council owns. The core artifact of good network governance is the authority map: a public, written split of decisions between the council and the founder. Ambiguity here is the single biggest driver of governance frustration, so eliminate it on paper first.

Council territory:

• How the methodology evolves. Refinements, additions, tooling. The people delivering it every week see things you can't see from the strategy seat; the council turns that frontline knowledge into coherent proposals.
• Where the quality bar sits. Peer-review criteria, delivery thresholds, what engagement scope each tier may take on. When the community sets its own bar, the bar carries communal legitimacy instead of resting on founder say-so.
• Disputes between partners. Referral conflicts, territory overlap, interpersonal friction. A neutral elected body can mediate; a founder ruling on partner-versus-partner fights inevitably gets read as playing favorites.
• Community programming. Call formats, summit agendas, which case studies get published. Operational calls that improve with many voices and need no strategic mandate.

Founder territory:

• Direction. The 2-5 year arc of the methodology — new markets, new tiers, retiring offerings. Vision is not a committee output.
• Who's in and who's out. The council can shape admission criteria, but final calls on bringing partners in or removing them stay with you. That firewall prevents admissions becoming favors to council allies, and removals becoming weapons against rivals.
• Money and contracts. Pricing, licensing terms, external partnership deals. These hit your business directly and don't belong to consensus.
• IP and legal. Intellectual property boundaries, trademark enforcement, disputes. Liability demands a single accountable owner.
• The brand. Market positioning, PR, publishing. External voice stays with the founder.

Codify this split in a governance charter, publish it, and bake it into partner onboarding. Any partner who wants something changed should be able to read the charter and know immediately whether their request goes to the council or to you.

Composing the Council

Small, Contribution-Elected, Always Rotating

Keep the body lean: 5-7 members, elected from your certified partners. Below 5, you don't get genuine diversity of perspective — you get a clique with a title. Above 7, coordination costs swamp the benefit and meetings sprawl. Five covers most communities under 75 partners; seven serves networks up to around 150.

Elect on contribution, never on seniority. Being in the founding cohort earns gratitude, not a seat. Seats go to the partners with the deepest demonstrated investment in the ecosystem — engagements delivered, thought leadership published, referrals made, methodology improvements proposed. They're the members who best understand what's actually working on the ground.

Rotate on a stagger. Two-year terms, with half the seats turning over annually. Full annual turnover destroys institutional memory; no turnover hardens into a permanent inner circle. Staggering hedges both failure modes at once.

Keep elections almost boring. Candidates self-nominate with a short statement — contribution record, priorities, motivation — and all active partners vote. Resist elaborate electoral machinery; the moment the procedure gets more attention than the community, you've built governance theater.

One structural detail does outsized work: you sit on the council, but a partner chairs it. The council owns its meetings, its agenda, and its conclusions. Your reserved powers live in the charter; the chair lives with the community. That arrangement signals — credibly — that governance is shared, not granted.

Switch It On With Conviction

Founders mistime this in two directions. Some bolt governance onto a community of 12, drowning a tight founding group in process it doesn't need. Others wait until the network is on fire and improvise a constitution mid-crisis. The better sequence: draft the charter in Year 1, while the group is small and you can think clearly, then activate the moment the warning lights from the first section start blinking.

And when you activate, do it loudly. Announce the structure, explain its purpose, run a real first election, publish the charter, and hand the council genuine authority on Day 1. A ceremonial council that everyone recognizes as decoration is worse than no council at all.

Expect resistance from exactly the partners you most want serving. Your top performers are usually your most independent operators and your most bureaucracy-averse. The argument that lands with them isn't civic duty — it's efficiency. A council seat gives them a direct lever on decisions that affect their business, instead of competing for space in your inbox.

Don't confuse governance with bureaucracy. Bureaucracy slows decisions; governance makes them legitimate, visible, and durable. A contribution-elected council of 5-7, paired with a published authority map, is what turns a founder-dependent partner program into a community that can govern itself. Draft the structure while things are calm. Deploy it when the strain shows. And remember that distributing authority doesn't diminish you — it compounds the value of the ecosystem your position depends on.