From Busy to Flow: How to Find and Remove Friction in the Way Your Team Works

Think about your last five working days. How often did you stop something important because something else suddenly became urgent? And who decided it was urgent?

Sometimes urgency is real: a customer is blocked, production is down, a deadline cannot move. Often it is inherited, assumed or created because context was missing. That difference is where most lost productivity hides. At Brand Guarde we spent an all-team session on exactly this question, and these are the ideas we are putting into practice.

Busy is not the same as progress

Modern work is fragmented, and the numbers confirm what most teams already feel.

The fragmented workday

• 275interruptions in an average workday, about one every two minutes
• 48%of employees say their work feels chaotic and fragmented
• 52%of leaders say the same
• 20%global employee engagement in 2025, the lowest since 2020

The problem is usually not effort. Teams already have effort. The problem is friction: interruptions, hidden queues, unclear decisions, priority churn, too much work in progress and constant context switching.

So the useful question changes. Instead of asking who is busy, ask: where does work spend more time waiting than moving?

Most of the time, work is waiting

Picture a familiar day. You start on planned work. A quick question arrives. Then a new urgent request, then a meeting. Later you return to the original task and spend time reconstructing where you were, only to find it now needs an approval. You were active all day, but the work barely moved.

Zoom out to a single piece of work and the pattern is even clearer.

One request, start to finish

Actual work11 hours

Elapsed time4+ days

1. Request 0.5 h
2. Wait 1 day
3. Prioritise 0.5 h
4. Wait 4 h
5. Work 8 h
6. Wait 2 days
7. Review 1 h
8. Wait 1 day
9. Deliver 1 h

The work itself is not slow. The waiting is. That is why asking people to "work faster" so often misses the point.

Five types of friction

Name the friction, not the team. Most delays fall into one of five patterns:

1. Waiting: work is held up by an approval, a review or a reply.
2. Too much work in progress: too many things started, too few finished. Unlike a backlog, work in progress consumes attention right now.
3. Priority churn: work resets because something else became urgent.
4. Handoffs: context or inputs get lost when work changes hands.
5. Rework: feedback arrives late, or "done" was never clearly defined.

The same patterns appear in every function. In operations, a case waits for approval. In sales, a proposal waits for pricing validation. In development, code waits for review. In any team, a decision waits for an owner. The domain changes; the queue does not.

Match the fix to the friction

Small system changes can outperform heroic effort, but only when the fix fits the problem. The common mistake is adopting a practice because it is fashionable (a new meeting, a dashboard, an automation) before diagnosing the friction.

Choose the lever that fits

If the friction is…	Try this lever	Because it…
Too much work in progress	Limit work in progress	Finishes more by starting less
Large work items	Split work smaller	Gets review and delivery happening sooner
Hidden negotiation	Make policies explicit	Agrees who decides, what needs review and response times
Status meetings	Move status updates async	Protects focus time for real work
Repeatable handoffs	Automate the handoff	Removes repeatable toil, once the handoff is understood

For example, if work keeps waiting for review, the answer is not automatically another meeting. Define who owns review, agree a response time, limit how many items can sit in review, or split work so reviews are smaller. Then check whether it helped: did items spend less time in review, and did people need to chase status less?

Protect attention without reducing collaboration

Async does not mean silence. It means information can move without interrupting everyone at once.

• Use async for status updates, FYIs, pre-reads, one-way demos and routine handoffs.
• Meet live for conflict, high ambiguity, creative divergence, complex decisions and building trust.

Chat tools make it easy to blur the two. A message with a mention feels like it needs an answer now, even when the sender meant "whenever you can". Two habits help:

• Say what kind of urgency you mean. Use shared signals such as blocking now, needed today or when you have space, and add a due date to requests.
• Give people permission to focus. Announce a focus block, turn notifications off, and save or snooze messages to handle later instead of dropping everything.

Every meeting should earn its place with a purpose, a decision owner, a pre-read, a timebox and a short recap.

Diagnose the work, not the people

Most friction is rational behaviour inside a system that makes that behaviour likely. If the system rewards instant replies, people interrupt. If priorities are unclear, work gets reshuffled. If too much is started, people chase status.

That does not remove responsibility. It changes where you look, at three levels:

• Me: how I interrupt, clarify, prioritise and review.
• Us: the agreements we can change, such as work-in-progress limits, response norms and decision rules.
• The system: the queues, approvals, tools and ownership that create friction.

We all experience friction, and we all create it: sending a "quick question" without context, marking something urgent because we want it now, starting new work before finishing what is in progress, or inviting people to a meeting "just in case". Noticing these patterns is the goal. Blame is not.

Turn one friction point into a two-week experiment

You will not fix a whole organisation in one session. Pick one recurring friction you can influence and test a better agreement:

1. Friction: what keeps recurring?
2. Hypothesis: what might improve it?
3. Change: what exactly will you try?
4. Signal: how will you know it helped?
5. Decide: after two weeks, keep, modify or stop.

Keep the commitment small and specific. "I will improve communication" is too broad. "For the next two weeks, I will batch non-urgent questions instead of sending them as they occur" is testable. So is "I will finish one task uninterrupted each morning before opening chat" or "I will say whether a request is blocking or just needs a reply this week."

A commitment is only useful if you revisit it. Check in after a week and review after two, otherwise insight becomes another forgotten conversation.

The same idea applies to brand protection

Enforcement work has queues too: a violation waiting for a decision, a notice waiting for approval, a seller waiting to be researched. The fastest teams we work with do not work harder. They make the queue visible and remove the waiting. That is the thinking behind how we built MAP Control and Seller Removal: fewer handoffs, clear next steps, and work that moves.

Before asking people to go faster, look at where the work is waiting. Before asking for more effort, look at the friction.

Further reading: Microsoft Work Trend Index: Breaking down the infinite workday, Gallup State of the Global Workplace, The Open Guide to Kanban and Atlassian on working agreements.