The Synthesis

Niche saturation isn’t the opposite of coalition. It’s the prerequisite.

Daniel Ek’s principle is right: saturate your niche before you expand. But the card was incomplete. It assumed the niche is a standalone unit. It’s not. Niches that share a method, a market structure, or an identity sit on top of shared infrastructure, like lakes fed by the same aquifer. Auto auctions, livestock auctions, industrial equipment, personal property. Different surfaces, same water underneath.

A consortium doesn’t connect separate things. It maps what was always there. But you can’t tap into the aquifer until you’ve secured your own lake. An organization still fighting to define itself can’t sit at a table with a bigger player without it feeling like absorption. An organization that’s settled into its lane, with its own membership, its own advocacy, its own identity? Sharing infrastructure amplifies them instead of threatening them.

The Pattern Is Fractal

It works at every altitude:

  • Person: Get good at your craft before you start serving on boards and committees. Someone still building their business has no bandwidth for association leadership. Once they’re established, the association compounds what they’ve already built.
  • Business: Get established in your market before joining trade associations. A company still scrambling for clients can’t afford to invest energy in industry work. Once the business is stable, association involvement becomes additive.
  • Association: Saturate your niche before joining a consortium. A cross-industry alliance works when the organizations at the table have each done the work. One has $16.5M in assets and 75 years of standards-setting. Another has 800 members and a real lobbying operation. They’ve earned the security to share.

The equal voice principle is the structural requirement that holds it together. The moment one organization outweighs the others, you’re not connecting lakes anymore. You’re flooding one into the rest. That’s the dilution Ek warned about, just at the association level. Everyone stays sovereign in their own vertical. The consortium only exists in the shared layer underneath: aggregate data, advocacy weight, workforce pipeline. Things no single organization can produce alone.

For-profit companies figured this out years ago. Apple, Samsung, and Google compete on phones but sit on the same USB standards board. They compete on the product and cooperate on the plug. A consortium is the plug.

The aquifer was always there. The consortium just makes it usable. But only because everyone did the hard work of going deep first.

Open Questions

  1. How do you keep the voice equal when the lakes aren’t the same size? Governance design matters, but practical influence tends to follow resources.
  2. What happens when two lakes share a border? When one member organization was born from a split with another, does the consortium force that boundary question to resolve, or can it work around it?
  3. Is there a saturation threshold, some signal that tells an organization “you’re ready to share now”? Or is it just a feeling of security that leaders recognize when they see it?
  4. Does this principle apply in reverse? Can a consortium that loses a member’s trust push that member back into niche-protection mode?