I've been observing the same pattern in very different organizations. Large and small companies. Different sectors. Different teams.
But the symptom always looks the same. Teams working at full capacity. Packed calendars. Constant meetings. Reports piling up.
And yet, the organization moves more slowly than it should. For years we assumed it was a productivity problem. I believe that, in many cases, it isn't. It's a decision problem.
Because when an organization can't move forward through decisions, it compensates with activity. More meetings. More follow-up. More coordination. More reports.
But no amount of activity can replace a decision that never arrives. Over time I've reached an uncomfortable conclusion: many organizations are trying to optimize work when their real bottleneck is their capacity to decide.
I've written about this. About productivity theater. About decision architecture. About the invisible cost of decision waste.
And about why artificial intelligence won't solve this problem if we don't first solve how we decide.
👇 The full article is below.
For years we have tried to improve productivity through processes, methodologies, and technology. Yet many organizations continue to move more slowly than they should.
What if the real bottleneck weren't in the work? What if it were in the decisions? Most organizations don't have a productivity problem. They have a decision problem.
But because decisions are hard to measure, we talk about productivity. And because productivity is hard to demonstrate, we generate activity.
This is how productivity theater is born. A system where looking busy ends up mattering more than creating value.
The obsession with looking busy
When an organization stops distinguishing between activity and value, it starts rewarding whatever it can easily observe. Meetings are visible. Emails sent are visible. Reports generated are visible. Hours invested are visible.
Value created rarely is.
And when measuring impact is difficult, organizations measure activity. That is when the theater appears. Saturated calendars. Recurring meetings with no clear purpose. Reports nobody uses to make decisions. Validation processes that add weeks to decisions that should take hours. Everything seems to work. Everyone seems busy. But the organization moves more and more slowly.
The architecture nobody designed
Most organizations spend years designing processes, structures, and tools. Very few design how decisions are made. And yet, every organization runs on an invisible architecture: its decision architecture. Who decides. When they decide. With what information. With what autonomy. With what consequences.
It is the system, designed or accidental, that determines the speed, quality, and cost of every decision made within the organization.
Just as we design processes to produce goods or services, we should design systems to produce decisions. Most never have. When this architecture exists by accident, decisions don't disappear. They scatter. They slow down. They dissolve among committees, approvals, and chains of sign-off that nobody remembers creating. And teams, meanwhile, do the only thing they can do: keep working. Or at least appear to be.
The real bottleneck
I have seen strategic projects delayed by months. Not for lack of technical capability. Not for lack of budget. Not for lack of talent. The blockage was much simpler: nobody knew who could make the decision. Meanwhile, the team kept producing. Meetings. Reports. Follow-up. Activity. Everything except deciding. This is not an isolated case.
McKinsey has pointed out that the speed and quality of decisions have become critical factors for organizational performance, and that many organizations remain stuck in decision-making processes that are excessively slow, complex, and bureaucratic.
In many organizations, the main bottleneck is not in execution. It is in decisions. Decisions nobody knows who should make. Decisions that require multiple approvals. Decisions that travel from committee to committee. Decisions delayed by fear of error. Decisions made too late to have any impact.
Because when an organization can't move forward through decisions, it compensates with activity. But no amount of activity can replace a decision that never arrives.
The invisible cost of decision waste
Lean taught us to identify physical waste. Waiting. Rework. Excess inventory. Unnecessary movement. The knowledge economy requires us to identify another kind of waste: decision waste.
I'm not talking about wrong decisions. I'm talking about decisions that are never made. That are made too late. Or that are made so many times they lose all their strength. Every delayed decision generates a cost that doesn't appear on any balance sheet. Clients waiting. Opportunities expiring. Teams losing focus and replacing judgment with bureaucracy. Projects accumulating silent deviations.
Decision waste doesn't show up in financial indicators. But it ends up affecting every indicator that does.
AI won't solve this problem
Many organizations expect artificial intelligence to increase their productivity. And it probably will. But there is a trap that few are seeing.
AI improves the speed of execution. It does not improve the quality of decisions.
An organization with a poor decision architecture won't become more effective with AI. It will become faster at doing what it already did poorly. It will generate more documents nobody reads. More analysis nobody uses to decide. More reports that will feed more meetings that will postpone more decisions.
Technology amplifies the existing system. It doesn't correct its structural flaws. If decisions are slow, AI will speed up the production of the bottleneck. If decisions are clear, AI will accelerate the creation of value. The difference between both scenarios is not technological. It is organizational.
The next competitive advantage
If tomorrow you eliminated 50% of the meetings in your organization, what would stop happening? And if tomorrow you doubled the speed of critical decisions, what would start happening?
For decades we have tried to optimize work. We have redesigned processes. We have implemented methodologies. We have digitized operations. We have automated tasks. The next competitive advantage will not be technological. It will not be methodological. It will not be operational. It will be decisional.
The winners will be the organizations capable of turning information into decisions, and decisions into action, faster than their competitors. Because in the knowledge economy, the winner is not whoever works the most. The winner is whoever learns to decide better. And that capability doesn't arise by accident. It is designed.
Every organization ends up resembling the quality of its decisions
For leadership
Before launching another transformation program, three questions:
→ How long does it take for a strategic decision to turn into action?
→ How many critical decisions are blocked today by organizational ambiguity?
→ How much time do teams spend coordinating compared with the time they spend creating value?
Organizations are not limited by their capacity to work. They are limited by their capacity to decide.
Comments (3)
Log in to your Scrum Manager area to comment
José Manuel Hernández Agudo
3 Jun 2026 16:57I have written a book called "Cómo transformar empresas de servicios con Agile, Scrum y TOC", and in it I talk about aligning AGILE and SCRUM with TOC, the theory of constraints, where I talk a lot about bottlenecks. This book gave rise to the podcast Agile, Scrum y TOC para empresas de servicios on Ivoox https://go.ivoox.com/sq/3123506, I look forward to your comments
Yo he escrito un libro llamado "Cómo transformar empresas de servicios con Agile, Scrum y TOC", y en él hablo de alinear AGILE y SCRUM con TOC la teoria de las restriciones, donde hablo mucho de cuellos de botella, de este libro ha salido el podcast Agile, Scrum y TOC para empresas de servicios en Ivoox https://go.ivoox.com/sq/3123506, espero vuestros comentarios
Automatic translation · View original
Jorge Sánchez López ★★★
29 Jul 2026 11:49Thank you, José Manuel. I know your work, and I think we share a common concern: identifying what really limits an organization's performance.
My approach starts from a different level. You analyze how to improve the way work is done through practices such as Agile, Scrum, or TOC. I am trying to answer an earlier question: what system produces the decisions that make it possible—or prevent—those practices from generating results?
My hypothesis is that, in many knowledge companies, the main bottleneck is no longer in the workflow, but in the decision flow. That is why I am interested in studying the architecture that determines who decides, with what information, with what autonomy, and at what speed.
I believe both approaches are complementary: improving the work is still necessary, but it is becoming increasingly difficult to do so if we do not first understand how the organization decides.
Gracias, José Manuel. Conozco tu trabajo y creo que compartimos una preocupación común: identificar qué limita realmente el rendimiento de una organización.
Mi planteamiento parte de un plano diferente. Tú analizas cómo mejorar el sistema de trabajo mediante prácticas como Agile, Scrum o TOC. Yo intento responder a una pregunta anterior: ¿qué sistema produce las decisiones que hacen posible —o impiden— que esas prácticas generen resultados?
Mi hipótesis es que, en muchas organizaciones del conocimiento, el principal cuello de botella ya no está en el flujo de trabajo, sino en el flujo de decisiones. Por eso me interesa estudiar la arquitectura que determina quién decide, con qué información, con qué autonomía y con qué velocidad.
Creo que ambos enfoques son complementarios: mejorar el trabajo sigue siendo necesario, pero cada vez resulta más difícil hacerlo si antes no entendemos cómo decide la organización.
Automatic translation · View original
Juan Tatay Galvany ★
7 Jun 2026 12:22I agree with your approach, word for word, Jorge.
With AI we can have advanced automations, but "garbage in, garbage out" still applies, and "a bad process can't be fixed with automation": the process has to be fixed… the decision-making ;-)
Suscribo tu enfoque, caso palabra por palabra, Jorge.
Con la IA podemos tener automatizaciones avanzadas, pero no deja de darse "garbage in, garbage out" ni que "un mal proceso no se arregla con automatización", hay que arreglar el proceso… la toma de decisiones ;-)
Automatic translation · View original