In the world of agile methodologies, one question that often arises is whether removing committees can significantly reduce time to market. Some claim that this can lead to a reduction of up to 50%. But is that really true? My experience suggests that while the figure may be exaggerated, the impact of committees on decision-making and agility is profound.
The Myth of the 50% Reduction
Let’s be honest: the idea that you can cut time to market by half simply by eliminating committees sounds a bit too good to be true. As the saying goes, “Lies, damn lies, and statistics.” The reality is that while the exact percentage may be questionable, the detrimental effects of committees on decision-making are very real.
The Problem with Committees
In my current engagements, I’ve observed that both formal and informal committees often slow down the decision-making process. Here’s how:
- Decision Delays: When a decision is needed, it often requires the input of multiple stakeholders. This can lead to lengthy discussions, disagreements, and the need to involve even more people. The result? Prolonged decision-making that stalls progress.
- Stalled Teams: While committees deliberate, teams are left waiting. This not only affects morale but also impacts deadlines. Teams need clarity to move forward, and when they’re held up by committee processes, they can’t deliver value.
A Real-World Example
Let me share a specific example from a recent engagement. We were tasked with creating new procedures and policies to support a new way of working. The team on the ground wanted to use modern document management systems like SharePoint or Google Docs for collaboration. This would allow for quick feedback and iterative improvements.
However, the committee insisted on a more traditional approach: sending a final draft for review to a long list of stakeholders, who would then provide feedback through a cumbersome process involving Excel sheets. This not only delayed the project but also stifled innovation and responsiveness.
The Cost of Traditional Practices
The difference between these two approaches is stark. With modern collaboration tools, we could have produced a near-final document in a matter of days. Instead, we faced a drawn-out process that could take six to twelve weeks. This is where the real cost lies, not just in time to market, but in lost opportunities.
-
Missed Opportunities: Every moment spent in committee is a moment where potential business opportunities slip away. If decisions are delayed, competitors can swoop in and capture the market share that could have been yours.
-
Agility vs. Staging: Committees represent a traditional, staged approach to management that is at odds with the agile mindset. Agile is about collaboration, speed, and adaptability. Committees, on the other hand, create barriers that hinder these principles.
The Need for Change
It’s clear to me that committees need to be re-evaluated in the context of modern business practices. The agility of a team can be severely compromised by outdated decision-making structures.
-
Empower Teams: Instead of relying on committees, organisations should empower teams to make decisions. This not only speeds up processes but also fosters a culture of accountability and innovation.
-
Adapt to Change: In today’s fast-paced environment, the ability to adapt quickly is crucial. Companies that cling to traditional practices risk falling behind more agile competitors.
Conclusion
While the claim that removing committees can reduce time to market by 50% may be an exaggeration, the underlying truth is undeniable: committees slow down decision-making and hinder agility. The real question is, how many opportunities are you willing to let slip away while waiting for a committee to make a decision?
If you’re in a traditional organisation, consider how you can streamline your processes and empower your teams. The future of your business may depend on it.
Thank you for reading! If you found this post insightful, please like, follow, and subscribe. I’m always open to discussions about agile, scrum, or DevOps, so feel free to book a coffee chat with me through Naked Agility.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Unlocking Organisational Agility: How to Empower Your Team for Rapid Market Response
Learn how empowering teams, streamlining communication, and providing context enable organisations to respond rapidly to market changes and …
Empowering Teams to Tailor Their Processes: A Path to True Agility
Explains why empowering teams to adapt their processes boosts agility, reduces waste, and fosters innovation, using real-world examples and …
Unmasking Agile: How to Spot Genuine Practices Amidst the Myths
Learn how to identify authentic agile practices, spot common myths, and understand cultural barriers that hinder true agility in modern …
Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development
Explains how agile practices help teams manage complexity, adapt to change, and deliver value faster in modern product development, compared …
Beyond the Agile Illusion: Embracing True Agility in a World of Taylorism
Explores the difference between true agility and superficial agile practices, highlighting the impact of Taylorism and offering steps to …
Why Handoffs Are Killing Your Agility
Excessive handoffs in software development create delays, reduce quality, and harm team morale. Learn how eliminating handoffs boosts …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …