"A committee is where good ideas go to die slowly."
You have a solid proposal. It looks good, was validated with data, and solves a real operational problem. But before it becomes a reality in production, it needs to pass through a ritualistic barrier: the Committee. That bi-weekly or monthly meeting where 12 people who do not follow the technical context vote in fifteen minutes on something that you and your team studied for weeks.
What is the practical result most of the time? Delay, dilution of the original proposal, or silent death in the queue of the next meeting.
Why committees stall companies
Approval committees rarely arise out of malice; they emerge from the legitimate attempt to control risks as the organization grows. The problem is that, when poorly designed, they produce three serious dysfunctions:
1. Diffusion of responsibility
When everyone approves as a group, no one is individually responsible for the result. For the committee member who does not deeply know the project, it is always safer to ask for "one more study" or say "no" than to assume the risk of approving.
2. Information asymmetry and Parkinson's Law
Whoever built the solution and is close to the problem knows much more about the technical details than whoever judges in the room. In 1955, in the pages of The Economist, historian C. Northcote Parkinson described how bureaucracy expands and formulated the famous Law of Triviality: in a committee, the time spent discussing a subject is inversely proportional to its complexity and real importance. Since few deeply understand the architecture of a complex system, the committee approves or stalls the technical core in the dark and spends forty minutes debating the color of the button or the name of the project.
3. Fixed calendar vs. Real urgency
Committees have a fixed schedule on the executive calendar; operational problems and customer opportunities do not. Waiting three weeks in the queue to approve a simple change that needed to be running yesterday is an expensive dysfunction. Research conducted by Michael Mankins, a partner at Bain & Company, and published in the Harvard Business Review (2014) shows that large companies lose thousands of leadership hours in cascading meetings that do not generate clear decisions, turning organizational time into the most wasted resource of the company.
Alternatives that actually work
Unblocking the company does not mean giving up governance or turning production into a lawless land. It means replacing the human bottleneck with intelligent criteria:
1. Distributed authority with clear limits
Explicitly define who can approve what within each impact and budget range. Not every technical change needs to escalate to the board. Not every product improvement requires unanimous consensus among five departments.
2. Reversible decision vs. Irreversible decision (Type 1 and Type 2)
In the celebrated Amazon 2015 Letter to Shareholders, Jeff Bezos warned against the mistake of using the same heavy process for all types of choices. He divided decisions into two categories:
- Type 1 Decisions (Irreversible): these are one-way doors, such as firing a person, selling a business unit, altering the data security structure, or signing an exclusive contract for 5 years. These deserve rigor, deep debate, and careful review.
- Type 2 Decisions (Reversible): these are two-way doors, such as testing a feature with 5% of users, adjusting an internal workflow, or hiring a tool during a trial period. If the choice does not work, you can turn back in minutes. Using a slow Type 1 decision committee to approve Type 2 decisions kills speed, discourages experimentation, and bogs down engineering.
3. Asynchronous review by exception
Instead of waiting for a synchronous meeting with twelve busy calendars, circulate a lean one-page document explaining the problem, the proposed solution, the risk, and the rollback plan, with a 48-hour deadline for substantiated technical objections. If no one points out a real blocking risk within the deadline, silence counts as approval and the team moves forward.
4. Clear and lean RACI matrix
Before calling any group, make it transparent: who is Responsible for executing? Who is the only person who answers for the final decision (Accountable)? Who really needs to be Consulted beforehand (Consulted) and who should only be Informed afterwards (Informed)? Put fewer people voting in the room and more clarity on who hammers out the final call.
The agility test
Look at the last simple improvement your team put into production and do an honest calculation: how long did it take to build and test the change, and how long did it sit waiting for approval?
If in your company it takes longer to approve than to implement, something is structurally wrong with your governance. Review your rituals. Protect with rigor where the risk is irreversible, automate security barriers in the pipeline, and let go where the team can advance.
Continue deepening: also read Categorization and Priority and Culture that Restrains or Sabotages. Also learn about the work in Executive Engineering Leadership and the Case Studies.
References and verifiable readings
- Parkinson, C. N. (1955 / 1957). Parkinson's Law, and Other Studies in Administration. The Economist / Houghton Mifflin.
- Bezos, J. (2015). 2015 Letter to Shareholders (Type 1 and Type 2 Decisions). Amazon.com, Inc. / U.S. Securities and Exchange Commission.
- Mankins, M., Brahm, C., & Caimi, G. (2014). Your Scarcest Resource: Time, Talent, Energy. Harvard Business Review, May 2014.
Good ideas keep the conversation going.
Share this article or publish the visual deck to your Stories and Feed.

Cesar Zanis
15+ years leading software architecture, database performance, FinOps, and applied AI across enterprise operations. Built and scaled an engineering organization from zero to 20+ developers.
Enjoyed this article?
I publish practical analyses on critical systems architecture, Cloud FinOps, data, AI, and engineering leadership directly on LinkedIn.
Continue Reading
Take this analysis further with data and sources
All visual cards of this article are ready above to share on your Stories, Feed, WhatsApp, or LinkedIn with full sources.



