There is a sentence many leaders use because it sounds responsible. “Just keep me in the loop.”
It sounds like support. It sounds like good leadership. It sounds like trust.
It is also one of the fastest ways to turn Microsoft Teams into a running commentary on work.
Most leaders do not say it because they want more noise. They say it because they are trying to prevent surprises.
They are trying to protect outcomes, stakeholders, customers, budgets, reputations.
The problem is that “keep me in the loop” rarely comes with a definition of what the loop is.
So, teams guess.
They add you “just in case.”
They forward messages “so you have context.”
They narrate progress because silence can be misread as risk.
And suddenly, collaboration tools are not supporting work. They are hosting a performance of work.
Visibility is not free
When leaders ask to be kept in the loop, they are asking for visibility inside a system that already interrupts people all day.
That request does not land equally.
It lands on the people doing the work, who now also need to explain the work while doing it.
The loop request is often a fear response
Leaders are navigating real uncertainty.
Projects move faster than governance.
Risks appear late.
Stakeholders want answers before teams have them.
Hybrid work reduces informal observation.
In that environment, “keep me in the loop” becomes reassurance.
If I see everything, I can act early.
If I am copied, I am safe.
If I know first, I can prevent escalation.
But reassurance is not the same thing as leadership.
Leadership is deciding what information you truly need, when you need it, and what you are willing to let your team handle without you.
When “in the loop” becomes “on the hook”
Here is what teams often hear when a leader says, “keep me in the loop,” even if the leader does not mean it.
If something goes wrong, I will ask why I was not included.
If you make a decision without me, it may not count.
If I do not reply, you still need to know I saw it.
That is not collaboration. That is a shifting of risk.
Leaders do not usually intend this. But people adapt quickly to what gets questioned later.
If leaders challenge decisions after the fact, people copy them in advance.
Why this turns into digital overload, fast
Once a workplace gets used to constant visibility, a predictable thing happens.
Message volume rises.
Search gets harder.
Decisions get buried in threads.
Teams spend more time locating “the latest” than moving the work.
Then, in the middle of that frustration, someone suggests a new tool. Often an AI tool.
It sounds logical.
If the problem is information overload, maybe a new layer of technology can sort it.
But adding another tool usually adds another place to store work, another place to make decisions, and another place for people to feel they must keep up.
If your teams are still not using the tools you already pay for in a consistent way, tool stacking rarely reduces overload.
It multiplies it.
What leaders can do instead
Leaders need a replacement for “keep me in the loop” that still manages risk.
Here are four behaviours that change the conditions that create the habit.
- Replace “keep me in the loop” with a trigger list
- Name what requires escalation. Keep it short. For example:
- “Pull me in if this affects a customer, a deadline, legal or compliance, or spend over X.”
- “If it does not, post it in the project channel update thread.”
- Put decisions in one visible place, with one owner
- If decisions live in chat, people will keep asking. Create a single home for decisions, with owner and next step.
- Agree response expectations by message type
- Not everything is urgent because it arrived in Teams. Define what “urgent” means and what timing looks like for everything else.
- Create a pull update so people stop narrating work
- If leaders review updates at a set time, teams stop chasing attention through pings.
None of this is complicated. It is also not automatic.
It requires leaders to choose what they will no longer ask for.
It requires leaders to tolerate not knowing every detail in real time.
It requires leaders to reward ownership, not constant visibility.
A leader’s loop is a design choice.
You can design it to reduce noise. Or you can keep feeding the stream.