| name | building-product-movements |
| description | Strategies for transforming a software product into a global community and ecosystem. Use this when launching open-source projects, building developer platforms, or seeking to create a competitive moat through ecosystem incentives rather than just features. |
Building Product Movements
Successful platforms are more than just software; they are movements. By infusing a product with a clear philosophy and designing systems that prioritize ecosystem success over core company profits, you can create a "flywheel" effect that proprietary competitors cannot easily replicate.
Core Principles
1. Shift from Product to Philosophy
Don't just sell utility; give people a worldview to believe in.
- Infuse Art and Soul: Use branding to signal that the work is craft. For example, the WordPress tagline "Code is Poetry" and naming every major release after a jazz musician (e.g., Gershwin, Vaughan) humanizes the technology.
- Set the Values: Establish clear "freedoms" (like the GPL's four freedoms: use, study, change, and redistribute) so users know they are building on a foundation of liberty, not just a vendor's roadmap.
2. Design for Systems Thinking and Incentives
A true platform exists when the ecosystem built on top of it makes more money than the core company itself.
- The "True Platform" Test: If the third-party developers, agencies, and theme creators are collectively out-earning the platform owner, the moat is secure.
- Protect the "Rug": Never pull the rug out from under successful developers. Unlike social media giants that often cut off API access once a third party gets too successful, a movement ensures that even if the founder "grows devil horns," the code belongs to the users.
3. Establish Contribution Infrastructure
Provide clear "on-ramps" for people to contribute their specific talents, not just code.
- Create formal groups for non-coders, including accessibility, design, translation, documentation, and event organization.
