Fix the Coordination Bottleneck Before Adding Another Tool

A client asks whether the revised packaging artwork is ready. The account lead checks email for feedback, chat for the designer’s latest note and the project platform for a due date that has not changed. Nobody is idle, yet nobody can give a confident answer. That is a coordination bottleneck, and adding a fourth place to look is unlikely to remove it.

Small teams often mistake status-chasing for a software gap. The work may already have adequate places to live; what is missing is an agreed route for decisions, updates and exceptions. Research from Asana found that surveyed knowledge workers reported spending 58 percent of their day on coordination rather than skilled work. Microsoft WorkLab also reported that its activity data showed people spending more time communicating than creating. Those findings make the hidden cost of chasing an answer harder to dismiss: each extra check interrupts the client work the team was hired to do.

Start with the work that is waiting, not the tool menu. Follow one live client deliverable from brief to approval and mark every pause. Is the designer waiting for a consolidated client comment? Is the account lead waiting for a creative director to choose between two options? Is a task marked complete while a change request sits in chat? A wait is useful evidence. It reveals the moment when responsibility, information or authority became unclear.

The next question is more precise than “who is involved?”: who owns the decision that releases this item? Contributors can advise, review and execute, but one named person should be accountable for deciding whether the work moves forward, returns for revision or needs escalation. That owner does not need to make every creative choice alone. She does need to prevent a draft from lingering because several people assume someone else will resolve competing input.

Then establish one home for current status. This is not a demand that every discussion, file or idea live in one system. Email may remain the channel for a client approval, chat may handle a quick clarification and project software may hold the workflow. The team needs one agreed record that answers the operational questions: what is the current version, what is waiting, who owns the next move and when is it due? If a chat exchange changes any of those answers, someone updates the record. Status becomes a shared fact rather than a scavenger hunt.

Consider a clearly illustrative packaging studio preparing a label refresh for a food client. Client comments arrive by email. The account lead pastes selected points into chat for the designer. The designer posts a revised file in the project platform, where the creative director adds a note but does not state whether the direction is approved. Meanwhile, the account lead tells the client that revisions are underway. Approval time disappears between three channels because the team has no single release point.

The studio redesigns the handoff around the approval decision. The account lead collects and consolidates client feedback before it reaches design, separating requested changes from questions that need a client answer. The creative director becomes the named decision owner for internal creative approval. The project record becomes the current-status home, with a field for version, decision owner, next action and client dependency. Email remains the client-facing channel, but the account lead records the client’s response in the project item. Chat is reserved for short clarifications, not final approval.

This redesign also defines what deserves synchronous discussion. A decision may need a live conversation when feedback conflicts, a client deadline creates a trade-off or reviewers disagree on the direction. A simple status update, a file link or an unambiguous approval does not. The distinction protects focused work while making the consequential conversations easier to identify.

Slack and Qualtrics reported persistent alignment and productivity obstacles among surveyed desk workers and executives. For a client-services team, alignment is not an abstract culture issue; it is the ability to tell a client what is true without opening three applications. Before purchasing another platform, test whether the team can answer four questions from one current record: What is waiting? Who decides? What happens next? What requires a real-time conversation? If those answers remain fuzzy, a new tool may simply give the bottleneck another address.

Sources

• Microsoft WorkLab (published 2023-05-09; accessed 2026-09-13)
• Asana (published 2023-03-08; accessed 2026-09-13)
• Slack (published 2023-06-23; accessed 2026-09-13)