At Riverton Supply, the operations team believed its calendar demonstrated how closely departments worked together. Purchasing met with finance every Monday, warehouse supervisors joined a daily planning call, and account managers attended a weekly service review. Yet customer orders still spent too much time waiting for decisions. The company was communicating frequently without making responsibility clear.

The problem became visible when a delayed shipment required approval from three managers. Each assumed another person owned the decision, so the order appeared on several agendas without moving forward. When the customer finally received an answer, the practical solution took less than ten minutes to arrange. The expensive part had been the uncertainty surrounding it.

Rather than remove meetings at random, the team reviewed how five common decisions travelled through the business. For each one, they identified the person who could make the call, the information that person needed, and the point at which colleagues should be consulted. They wrote the results on a single page and used actual orders to test whether the instructions were clear.

Over the next month, the company replaced its daily planning call with a shared exception log and two short meetings each week. Routine issues stayed with the people closest to the work. Problems that affected several departments received a named owner and a deadline. The aim was not to make every employee more independent, but to stop the same question from circulating without an answer.

This fictional example illustrates a useful management principle: meeting volume is a poor substitute for decision design. Before asking whether a recurring call should be shorter, ask what decision it exists to support. If nobody can explain who acts afterward, changing the duration will offer limited relief. A clearer agreement about responsibility may recover more time than another round of calendar restrictions.