A deadline is missed. A customer issue remains unresolved. A project has been sitting for two weeks. Leadership asks what happened, and everyone has an answer. Operations thought Project Management was driving it. Project Management was waiting for the department manager. The department manager believed the team had it. The team was waiting for a decision from leadership. Everyone was involved. Nobody owned the outcome. That is not a people problem. It is an accountability pr

When critical information is missing, leaders usually hear some version of the same explanation: “We need better communication.” Sometimes that's true. But when the same problem happens repeatedly—across projects, departments and teams—I would look deeper. The organization may not have a communication problem. It may have an information-flow problem. Information gaps often appear when critical context fails to survive the handoff between teams. There is an important differenc

Most leaders know what new work is costing them. They can see labor hours, project budgets, schedules, overtime, utilization and headcount. What is harder to see is how much capacity is being spent completing work the organization already paid for once. A drawing gets revised after release. A request gets returned because information was missing. A report is rebuilt after the requirements change. A purchase has to be reapproved. A team completes work against one assumption an

A process takes five days from request to completion, so naturally we call it a five-day process. But when you actually follow the work, you might find that people only spent four or five hours working on it. The rest of those five days? The work was sitting somewhere. It was waiting for another department to review it. Waiting for information that didn't come with the original request. Waiting for someone to answer a question. Or simply sitting in a queue until the next pers

When work stalls, leaders usually look for the department causing the delay. Procurement is waiting. Engineering hasn't released the information. Finance hasn't approved it. Operations hasn't finalized the plan. Sometimes one of those departments really is the problem. But often the delay sits somewhere else entirely. It sits between them. That distinction matters because a company can have capable leaders, strong departments and clear internal procedures while still struggli

There is a point in some decisions when collaboration stops improving the decision and starts preventing one from being made. Most experienced leaders know the moment. The important perspectives have been heard. The risks are understood. Nobody has uncovered a fatal flaw. There may still be disagreement, but there probably isn't another meeting, email or analysis that's going to make everyone see the issue the same way. And yet the decision doesn't move. Someone wants one mor

Most leaders have sat through a meeting and wondered why half the people in the room needed to be there. The issue gets discussed. Everyone gives their perspective. Questions are answered. Someone takes notes. Then, just when it seems like the group is ready to move forward, someone says: “We should probably run this by leadership.” And there it is. The meeting wasn't really the problem. Unclear decision authority was. The people in the room didn't have the authority to fini

Research found that only 20% of respondents believed their organizations were good at decision-making. A majority also said much of the time spent making decisions was used ineffectively. It would be easy to blame bureaucracy or overly cautious leadership. But there is another explanation that is less obvious: Organizations teach people where decisions belong through everyday habits. It can start innocently enough. A supervisor encounters something unusual and asks a manager

Research found that executives spend nearly 40% of their time making decisions. Yet fewer than half believe their organizations make decisions quickly and effectively. That statistic shouldn't surprise anyone responsible for leading work across multiple teams. Most organizations that have noticed a bottleneck don't have a shortage of ideas, talent, or effort. They have a decision flow problem. Decision bottlenecks form when work is ready to move but the decisions required t

As organizations scale beyond 75 employees, growth creates a new challenge that many leaders don't anticipate. The problems are no longer obvious. Revenue may be growing. Customers may be coming in. Teams may be busy. Yet somehow projects move slower, communication becomes harder, and leaders find themselves spending more time solving internal issues than driving the business forward. The assumption is often that the organization needs more people, better technology, or stron