Nearly the same as the number of large companies in Silicon Valley who want everyone to feel good about a decision internally but don’t care in the slightest about how outsiders feel about it. Matt unfortunately makes a solid point, weakened as it may be by his presentation: consensus-based project management is around two orders of magnitude slower than authority-based project management, as currently implemented by most open-source and open-source-like projects. Ghostty is a good example of authority-based project management, and advances far more efficiently towards its goals than Wordpress. I will freely admit that I’m biased to assign zero relevance to people’s emotional hangups about having to disagree and commit; having seen that catering to soothing ego dramas in project processes, rather than directing those with personal drama to professional counseling out-of-band from the project itself, serves up a catastrophic derail for any serious effort, I now have zero tolerance for “we will never agree, we haven’t the courage to decide, and we have not assigned any individual as final decision-maker”.

Regarding the main story’s point, I think the original concern raised (the committee balked while a paid employee got lightning-quick approval) is correctly addressed by focusing attention upon consensus-based project management as a defect in short- and medium-term work. It’s the right approach for long-term work — otherwise you get yanked around as priorities shift in the wind by a shifty leader (see also Tesla) — but it’s the wrong approach for making any decisions in less than a year of consideration.