Govern Like a City, Not a Company: Leading Practitioners You Can't Command

Something goes wrong in your practitioner network. A certified partner delivers a sloppy engagement. A client escalates. A standard you thought everyone understood gets ignored. Your reflex is immediate and feels completely responsible: add a checkpoint. Require an approval. Mandate a report before anyone acts.

Each new control seems reasonable on its own. Stacked together, they quietly hollow out your platform — because the practitioners with the most talent and the most options are precisely the ones who refuse to live under them.

This is the trap most methodology founders walk into when their network outgrows personal relationships. They try to run an ecosystem the way they ran a company. It doesn't work, and understanding why is the difference between a platform that scales and one that stalls at the limit of your calendar.

The fix isn't better management. It's a different model of authority altogether.

Citizens, Not Staff

What Changes When the Network Outgrows Your Address Book

In the early days, governance is invisible because it's personal. You know every practitioner by name. Friction gets settled with a phone call or a coffee. Quality stays high because everyone feels personally accountable to you. Somewhere around practitioner 40 or 50, that machinery breaks. There are simply too many people for personal influence to reach, and the founder has to decide what kind of authority replaces it.

Alex Moazed supplies the framing I keep coming back to: running a platform is being the mayor of a town, not the boss of a company. The distinction matters because of what each role can actually compel. A boss directs employees. A mayor cannot direct citizens — she can pass zoning laws, fund infrastructure, shape incentives, and respond when things break, but residents decide for themselves where to live, what to build, and how to spend their days.

Your practitioners are citizens in exactly this sense. They don't draw a salary from you. Most of them walked away from corporate life specifically so no one could approve or veto their decisions. They affiliated with your ecosystem because of the methodology, the brand, the community, and the flow of opportunities — not because they wanted a new manager.

Accepting that you hold a mayor's authority rather than a boss's is one of the most uncomfortable psychological shifts in a founder's career. It is also mandatory. There is no platform-scale version of command and control.

The Selection Effect of Heavy Oversight

Who Stays When You Tighten the Rules — and Who Walks

Here is the mechanism that makes over-control so destructive. Every additional layer of oversight — mandatory check-ins, pre-approval gates, status reports — imposes a tax on practitioner autonomy. Different practitioners respond to that tax differently, and the difference runs in exactly the wrong direction.

High performers feel the tax most acutely and tolerate it least. They generate their own pipeline, command respect in the market, and could affiliate elsewhere tomorrow. When your governance starts resembling the middle management they escaped, they leave — and they leave first, because they have the most alternatives.

Who tolerates heavy oversight? Disproportionately, the practitioners who need it: the ones who can't create opportunities on their own and depend on the platform to feed them. Tighten the grip and you filter your network toward its weakest members while repelling its strongest. The grip gets tighter, the platform gets smaller, the quality problems you were trying to fix get worse. That's the paradox.

A mayor escapes the paradox by never trying to grip in the first place. No mayor personally signs off on every building permit. Instead: building codes, civic culture, zoning that rewards good development, tax incentives that make the desired behavior the profitable behavior. Citizens stay free to act — inside a structure where acting well is the rational choice.

The Mayor's Toolkit

Four Levers, From Invisible to Explicit

Parker, Van Alstyne, and Choudary lay out four governance instruments that translate directly to methodology platforms. I'll present them in the reverse of the usual order — starting with the most elegant and ending with the most blunt — because that's the order in which you should reach for them.

Architecture — the rules nobody has to read. The best governance instrument is built into the platform itself. If your delivery system only supports the standardized assessment, no policy memo about "always use the standardized assessment" is ever needed. If client matching is driven by satisfaction scores, you never have to lecture anyone about keeping clients happy — the routing logic does the persuading. Every design choice is a governance choice: which fields are required, which dashboards practitioners see, which defaults ship, where friction lives and where it doesn't. When the architecture is right, the correct behavior is simply the path of least resistance.

Markets — self-interest pointed at ecosystem health. Visibility in the directory rises with completed engagements. Larger clients get matched to practitioners with stronger satisfaction records. Contributors to the methodology's thought leadership earn featured placement. Design the economics so that what's good for the network and what's good for the individual practitioner are the same thing, and most enforcement problems never materialize.

Norms — the culture that polices itself. Norms govern everything rules can't reach: how practitioners treat each other, how they carry the methodology in public, how they respond when a client is unhappy, how credit gets shared on joint work. You can't legislate any of this, but you can deliberately cultivate it. Your founding cohort sets the original tone. Community calls reinforce it month after month. Practitioners who embody the standard get celebrated in the open; behavior that betrays it gets handled quietly, one-on-one. Eventually the senior practitioners model the culture and newcomers absorb it by watching — and the norms enforce themselves.

Laws — explicit rules, written down, enforced every time. Some things must be non-negotiable: certification requirements, quality floors, data handling, the conditions under which someone loses their certification. The operative word is written. The ugliest governance failures come from rules that exist only as folklore — "everyone knows you don't..." — until someone who never got the memo breaks one. Publish the rules. Keep them current. Apply them consistently, with consequences everyone understood in advance.

You need all four levers at once. Each one alone has a failure mode: laws by themselves read as bureaucracy, norms by themselves are too vague to enforce, architecture without market incentives feels like a cage, and markets without architecture descend into chaos. The blend is what scales.

A Handover With a Timetable

Four Stages From Founder Rule to Community Rule

Governance also isn't a one-time design decision. It has to be rebuilt as the network grows, and every rebuild asks the founder to surrender something.

Founding, 1-25 practitioners. You govern personally and directly, and that's correct — the culture is still being formed, and personal trust does the work that formal process will do later. This is the one stage where being the boss is appropriate.

Growth, 25-100 practitioners. Direct rule stops scaling. You stand up a Partner Advisory Council — 5-7 senior practitioners — to advise on policy and absorb first-level disputes. You still write the rules; the council helps interpret and apply them. This is where the boss-to-mayor transition actually happens, because you're learning to govern through other people for the first time.

Scale, 100-500 practitioners. The council graduates from advisor to primary governing body. Working groups carry the day-to-day. Regional leads own geographic questions; specialty leads own discipline-specific ones. You keep veto rights on the things that define the platform — methodology changes and decertification — and let go of everything else. You set direction; the structure runs operations.

Maturity, 500+ practitioners. Regional councils, specialty councils, and a central standards board govern the ecosystem. Your role is strategic direction, full stop. Self-governing is not the same as ungoverned — it means governed by the community instead of by you.

Notice the pattern: every stage is defined by what the founder releases. First the disputes. Then the daily decisions. Finally, operational management itself.

The founder who refuses the handover becomes the ceiling. Not from lack of skill — from arithmetic. Personal relationships can govern perhaps 50 practitioners; an exceptional founder might stretch to 100; nobody reaches 500 that way. Past your personal bandwidth, governance is either systemic or the platform stops growing. The mayor who tries to be the boss ends up presiding over a town that never becomes a city.