Community

translate Automatic translation · View original

Endless Meetings and "Everything Needed Yesterday": Two Symptoms of the Same Problem?

Canal De Escalado Y Liderazgo

1 February 2026
Endless Meetings and "Everything Needed Yesterday": Two Symptoms of the Same Problem?
A few weeks ago we asked on LinkedIn which unhelpful habit you would most like to eliminate from your teams. The answers were clear: "everything needed yesterday" came first, closely followed by "endless meetings". And one of your comments made us think: we know these problems, but how are they solved? The answer is not a magic recipe. As with everything, it depends on the context, on the root of the problem, on whether psychological safety exists...

"Everything Needed Yesterday": Anatomy of False Urgency

Why does it happen?

The culture of constant urgency has many origins, and it is rarely the fault of a single culprit. This kind of culture usually appears in organizations where "activity" is equated with "progress". As a consequence, the pressure to show visible results generates a cycle of urgent demands that displace strategic work.

A first factor is real market pressure that is poorly managed. We live in competitive environments that demand speed, but many organizations turn that external pressure into internal chaos because they lack effective prioritization systems. Market urgency passes unfiltered to every level, creating "urgency theater": everything seems critical because there is no clarity about what really is.

The lack of strategic planning is another obvious catalyst. Daniel Kahneman, in Thinking, Fast and Slow, explains how cognitive biases lead us to overvalue the immediate over the important. In organizational contexts, this translates into reactive roadmaps where every new request is perceived as urgent because there is no strategic frame of reference to assess its real priority. Teresa Torres, in Continuous Discovery Habits, argues that without a continuous system for validating opportunities, teams operate in firefighting mode: putting out fires without understanding which ones really matter.

But there is a less visible dimension: the culture of heroism. Many organizations implicitly value and reward those who "do the impossible" by working against the clock. Glorifying extreme effort turns urgency into a currency of professional value. If finishing projects in record time makes you stand out, the system encourages the artificial creation of urgencies.

Micromanagement disguised as agility is another recurring cause. The agile transformation promises autonomy, but in practice some leaders use the "need for constant alignment" as a control mechanism. There is a fine line between getting involved with your team and carrying out obsessive supervision. This supervision can generate constant "urgent" reviews that fragment the work and create ongoing pressure.

Fear also plays an important role. Depending on the culture, there may be an organizational fear of saying "no". Many product managers and leaders lack the backing or the tools to reject requests, even when they know those requests have no strategic value. In these organizations, every request from stakeholders can automatically become urgent because there is no room for negotiation and no clear criteria for rejection.

There may be many other factors, which is why the essential thing in these cases is to understand the why first. Not only to find a suitable solution, but to avoid the consequences of these symptoms. Because when everything is urgent, everything is under pressure. The stress this generates in the team over the long term can become burnout. And decisions made under pressure are not always of the best quality. Not to mention the gradual loss of the ability to plan strategically.

What to do?

The answer depends on your level of influence in the organization and on its type of culture. Without psychological safety, changes will be much harder to implement, especially if your level of influence is low.

Limited formal authority

Your room to maneuver is limited, but not nonexistent. The main strategy is to make the cost of constant urgency visible without pointing fingers.

An effective tactic is to ask questions during meetings. This is where your communication skills and choice of language come into play. It may seem obvious, but the language you use, the tone, and even the timing can work for or against you. As in any human interaction, the friendlier, clearer, and more respectful you are, the better. Even so, questions are likely to make people uncomfortable; not everyone is used to discomfort.

Another option is to apply the principle of documentation over escalation. This is where "data beats narrative" applies. Keep a simple but visible record of incoming work: what arrives, when, and how it affects the existing plan. Not as a complaint, but as information. Over time, patterns become evident and the conversation about prioritization becomes easier because the data speaks for itself.

You can also experiment with micro-commitments to focus. If you work in sprints, negotiate time windows during which the team does not accept new urgencies except for very specific criteria. It is a version of "bug triage": establishing clear thresholds for what justifies interrupting the work in progress.

With influence at team or product level

Here the main lever is to institutionalize transparent prioritization systems and objective criteria for urgency. The WSJF model (Weighted Shortest Job First) offers a useful method: evaluate the cost of delay against the size of the work. It is not perfect, but it forces data-based conversations.

Chris Matts introduced the concept of Cost of Delay precisely to quantify urgencies. If a "urgent" feature has a low cost of delay (we will lose little if we wait a week), then it is not really urgent. Making this exercise explicit with stakeholders changes the nature of the negotiations.

You can also implement "opportunity solution trees" adapted to your context: decision trees where each request is evaluated against the strategic goals of the quarter. If it does not clearly connect to a goal, it is not a priority (regardless of who requests it).

The technique of visible capacity planning is another option. If stakeholders can see your backlog and the team's current load in real time (tools such as Jira, Linear, or Monday make this possible), conversations about urgency become more honest. It is hard to insist that something is urgent when everyone can see the team is already at 120% capacity.

With organizational authority or direct access to leadership

Here the responsibility is to create the systemic conditions that eliminate the need for false urgency. High-performing organizations do not work faster because everything is urgent, but because they have systems that eliminate unnecessary work and reduce dependencies.

A critical cultural change is to redefine success metrics. If you currently value "delivery speed" without considering quality or strategic impact, you are encouraging a culture of urgency. Metrics such as "time to validated learning" change the game: it is no longer about doing things fast, but about doing the right things.

You also need to explicitly protect time for strategic work. Reserving 20-30% of the sprint for technical debt, refactoring, or exploration is a clear cultural message: not everything is urgent, and there are long-term investments that matter.

But if you prefer something more personal: set a precedent. If you send urgent messages at 11 p.m. or request last-minute changes yourself, you are implicitly giving permission for urgency to become the norm. Being clear about priorities, about what we will not do, and why, is an act of leadership.

"Endless Meetings": The Theater of Collaboration

Why does it happen?

Unproductive meetings are a symptom, not the disease. Understanding their causes requires looking beyond the "incompetent facilitator", although that is one factor.

The lack of facilitation skills is real and well documented. A 2017 Harvard Business Review study by Michael Mankins found that executives spend an average of 23 hours a week in meetings, compared with fewer than 10 hours in the 1960s. But the problem is not only the quantity, it is the quality: most professionals have never received training on how to design or facilitate effective meetings. We take for granted that knowing how to schedule a meeting is intuitive, when in reality it is a complex skill.

But there are deeper dynamics. Organizational insecurity plays a crucial role. In low-trust cultures, people attend meetings not because they are necessary, but because they fear that "if I'm not there, I won't have visibility" or "if I don't take part, they may make decisions that affect me without consulting me". The lack of psychological safety can turn meetings into self-protection mechanisms.

The confusion between collaboration and control is another pattern. Some organizations adopt collaborative tools and multiply meetings, believing that more interaction equals better alignment. But there is a fundamental difference between valuable collaborative work and "simulation work" that gives the appearance of productivity without generating real value. Meetings become a performance of activity.

The absence of clarity about responsibilities also perpetuates unnecessary meetings. If nobody knows who decides what, meetings become the default space where that ambiguity gets resolved. In other words, "alignment" meetings that are really power negotiations in disguise.

It is also common for some meetings to persist through institutional inertia. They were created for a valid purpose months or years ago, and nobody has stopped to think whether they are still needed. This is the "this is how we've always done it" syndrome: routines that outlive their usefulness simply because nobody questions them.

Regardless of the why, the consequences are clear: cognitive fatigue accumulates, deep work is systematically fragmented, and there is a constant sense of being busy without producing anything meaningful. A cost that is both personal and economic for the organization.

What can you do?

Once again, the approach varies depending on your position and on the type of culture in the organization.

Without formal authority

Your main goal is to protect your time without earning a reputation as "difficult" or "uncollaborative". It requires political tact.

A useful strategy is "ask privately first". If you are invited to a meeting whose purpose is unclear, contact the organizer beforehand and ask: "How can I prepare to add more value in the meeting?". Two things can happen: either they give you useful context that improves your participation, or they realize you may not need to be there.

During meetings that go off track, you can use "constructive reframing": "If I understand correctly, by the end of this conversation we need to decide X. Do we agree?". You are not questioning the meeting, you are helping to focus it. It is leadership without formal authority.

You can also apply the principle of "strategically limiting your availability". If you block specific hours in your calendar for deep work and consistently respect them, over time people learn when you are available for meetings. It is not rejection, it is professional management of your time.

With influence at team level

Here you can redesign how meetings work within your sphere of control.

Start by applying the "documentation first principle". Before scheduling a meeting, write down: the specific objective, the decision to be made or the expected deliverable, the list of necessary participants (not invitees, necessary ones), and an agenda with timings. If you cannot complete this document in 5 minutes, you probably do not need the meeting.

Experiment with alternative formats. Amazon is famous for its "six-page narratives" that are read in silence at the start of meetings. The format forces clarity of thought and eliminates PowerPoint presentations that consume time without adding value. Jeff Bezos argues that writing is thinking: if you cannot write it down clearly, you have not thought it through sufficiently.

Another powerful technique is the "standing meeting audit": every quarter, review all of your team's recurring meetings. For each one, ask: is it still necessary? Is it achieving its objective? Could it be an email? If the answer is not a resounding "yes", cancel it for a month as an experiment. You will almost always find that many of them are not missed.

You can also implement explicit "optional attendance": indicate in the invitation who is really needed and who is optional. This gives people social permission to decline without guilt.

With organizational authority

Your job is to create cultural norms that make unproductive meetings unnecessary.

A radical but effective change is to establish "meeting-free days" or protected blocks. Shopify famously cancelled all recurring meetings with more than 3 people in January 2023, arguing that only 3 in 10 meetings add value. It was drastic, but it forced honest conversations about which meetings really mattered.

Another cultural lever is to train all managers in effective facilitation. Not as an optional course, but as an evaluated core competency. If you lead people, you need to know how to design and facilitate meetings.

You also need to create accountability systems. If someone schedules a meeting without a clear agenda, their manager can (kindly) ask them to justify why it is necessary. It is not punishment, it is accountability. Over time, the standard of quality rises.

And, again, pay attention to your own behavior. If you as a leader cancel meetings when they lose their usefulness, if you send pre-read documents instead of using the meeting to present, if you end meetings early when the work is done, you give others cultural permission to do the same.

The Uncomfortable Truth

Sometimes these problems cannot be solved from our position. If you work in an organization where constant urgency comes from executive leadership decisions, where the lack of strategy is systemic, or where the meeting culture is deeply rooted in how power operates, your individual or even team-level options are limited.

This is not defeatism, it is realism. As Kim Scott says, part of professional growth is recognizing when you are in an environment that does not allow you to do your best work, and when it is time to look for one that does.

Not every battle can be won, and recognizing that is part of professional maturity.

Is There a Common Pattern?

Treating both problems separately, we have found common patterns that lead us to wonder whether they have something in common or are connected in some way. Our hypothesis is that both may be symptoms of a deeper structural problem: organizations that replace strategic clarity with operational noise. When there is no clarity about what really matters, everything seems urgent and everything requires constant alignment.

If an organization has no clear prioritization criteria, every new request is perceived as potentially critical. That generates urgencies. And when everything is urgent, you need constant meetings to "align", "synchronize", and "decide". Meetings become the default mechanism for managing ambiguity.

In addition, both patterns may be symptoms of low organizational trust. In high-trust environments, people can make autonomous decisions without needing constant approval (fewer meetings) and can negotiate priorities openly (fewer false urgencies). When trust is low, both mechanisms serve as forms of control: urgency to force action, meetings to supervise.

They also share a common enemy: the fragmentation of deep work. Valuable work requires sustained concentration. Both the interruptions caused by constant urgencies and fragmented meetings destroy that capacity. And curiously, the loss of deep work can create a vicious circle: since teams cannot advance on complex work, they turn to more meetings to "coordinate" work that has necessarily become superficial.

But the connection is not clear. We can imagine organizations with real market urgencies (high competition, changing regulation) that maintain excellent meeting management. Or companies with cultures of excessive meetings due to cultural consensus but with robust prioritization systems.

In short, we do not have definitive answers about whether "everything needed yesterday" and "endless meetings" always share a common root. What we do know is that both are symptoms of deeper organizational dysfunctions, and that treating them as individual "time management" problems means staying on the surface.

The first step, always, is to make the problem visible. Document, measure, ask. And then, act from wherever you can act. With small experiments, if you have no authority. With team changes, if you have influence. With cultural transformations, if you lead at the organizational level. Or with the decision to look for a better context, if none of the above works.

In your organizations, do these problems appear together? Have you noticed that solving one helps with the other? Or are they completely independent in your context?

References

  • Brown, B. (2018). Dare to Lead: Brave Work. Tough Conversations. Whole Hearts. Random House.
  • Cagan, M. (2020). Empowered: Ordinary People, Extraordinary Products. Wiley.
  • Cutler, J. (2023). The Beautiful Mess: Notes on Strategy, Teams, and Product Management. Leanpub.
  • Edmondson, A. C. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
  • Forsgren, N., Humble, J., & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps. IT Revolution Press.
  • Gothelf, J., & Seiden, J. (2017). Sense & Respond: How Successful Organizations Listen to Customers and Create New Products Continuously. Harvard Business Review Press.
  • Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.
  • Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central Publishing.
  • Parker, P. (2018). The Art of Gathering: How We Meet and Why It Matters. Riverhead Books.
  • Perri, M. (2018). Escaping the Build Trap: How Effective Product Management Creates Real Value. O'Reilly Media.
  • Scott, K. (2019). Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. St. Martin's Press (Revised Edition).
  • Torres, T. (2021). Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value. Product Talk LLC.