WordPress fans often cite “the community” as one of WordPress’s main selling points. Makers get excited by the prospect of participating in the development, design, and support of the WordPress software product (zomg 30% of the web). Yet the prospect of participation doesn’t hold the same charm for organizational decisionmakers who are choosing which software products to build their business on. How can we argue for WordPress as a business solution when an honest look at history shows that community-driven projects don’t necessarily, or even usually, result in superior products? How can we conceive of WordPress so that we’re realistic about the shortcomings of the community development process, without selling short WordPress’s strengths as a product?