Fix it in two weeks: Your team is drowning in information

Situation

Your team receives updates throughout the day. Some help people move their work forward. Others repeat what has already been said, while important decisions are hard to find. How do you know what your team really needs to hear?

TL;DR

Start a two-week trial to make information easier to find and use. Agree which updates matter, where decisions are recorded and how urgent concerns are raised. Review what works with the people who rely on the information, then decide what to keep or change.

Who this is for: Department leaders whose teams receive so many updates that important messages get missed or people spend too much time searching for information.

Aim: Help the team reduce duplication and find the information it needs to act.

Time: Two weeks to start the changes. Finding the right approach may take longer.

Core question: What information would help your team act with greater clarity this week?

Why this happens and why it matters to fix it

Updates often multiply for understandable reasons. People want to keep colleagues informed, respond to changes and make sure nothing is missed. When responsibilities are unclear or information is spread across several places, sending another message can feel like the safest option.

Finding a simpler way takes conversation. Ask colleagues what helps them do their work, what they struggle to find and what they worry about missing. Consider the needs of people outside the team too, especially those waiting for a handoff or decision.

In a study of 40 information workers over 12 working days, more time spent on email was linked with lower reported productivity and higher measured stress (Mark et al., 2016). The study offers a useful reason to look at how information reaches your team.

A clearer flow of information can help:

  • Team members find what they need and spend less time searching.
  • The department share a clearer picture of priorities and decisions.
  • The business keep work and handoffs moving with fewer missed updates.
Your two week action plan

Days 1–2: Understand the situation

  • List recurring updates, where they appear and any obvious duplicates. Ask colleagues what they have missed, where they search and which updates help them do their work.
  • [ ] Consider what the team needs to deliver and the quality standard it needs to meet. Identify people outside the team who depend on its updates, handoffs or decisions.
  • [ ] Ask whether workload, unclear responsibilities or difficult-to-use systems are adding to the problem, and who is carrying the extra work.

Day 3: Agree a simpler approach

  • [ ] With the team, agree which updates are essential, who needs them, how often and what level of detail and accuracy is needed. Name an owner for each update.
  • [ ] Choose an existing shared place for decisions that everyone who needs it can access. Agree who decides what and who will keep the record current.
  • [ ] Agree how to raise urgent issues and safety concerns without asking permission first. Offer a workable route for quieter and less senior colleagues to raise concerns or challenge a decision.

Days 4–5: Start the trial

  • [ ] Stop or combine duplicate updates where it is safe to do so. Record decisions in the agreed place, including what was decided, who is responsible and what happens next.
  • [ ] Check that people can find the information and know how to use the urgent route. Share the agreement with affected colleagues and teams.
  • [ ] Notice the time and attention needed to use the new approach. Adjust priorities if the change places an unfair burden on the same people.

Days 6–9: Keep learning

  • [ ] Continue the trial and keep the decision record current. Ask people to note duplicate messages, information they could not find and anything important that was missed.
  • [ ] Check whether people know what matters, who to go to and whether the work still meets the agreed standard. Respond calmly when someone raises a concern or gets something wrong.
  • [ ] Address urgent or safety concerns straight away, and involve the right leaders or specialists in technical issues.

Keep in mind: Check workload, privacy and accessibility as you go. Keep sensitive information in approved places, and make sure any changes work for the people who need the information.

Day 10: Review together

  • [ ] Ask the team: What information did you need that you did not see? What was easier to find? What still feels noisy?
  • [ ] Compare what you hear with your starting notes. Look for changes in duplicate updates, access to decisions and missed messages.
  • [ ] Agree what to keep, change or stop. Name an owner and review date, and ask what you could do differently as a leader to support the team.

When to ask for help

If you are unsure where to start, important information keeps getting lost, communication between teams creates recurring friction, or people find it difficult to raise concerns, you do not have to work it out alone.

Scroll to Top