Insights · Workplace guidance · 4 minute read

What Information Deserves the Team’s Attention?

Before sending an update, ask what someone can do with it. The answer tells you what to put first, who needs it, and when.

By Vitaver Staffing ·

The update that matters is easy to miss

A team receives a page of notes about meetings held, tickets closed, and work in progress. Near the bottom is one sentence. Last night’s backup failed, and the next scheduled run comes after a planned software release. That fact could change the release decision. It belongs where the person responsible will see it in time to act.

In his 1971 essay “Designing Organizations for an Information-Rich World,” Herbert A. Simon observed that information consumes the attention of the people who receive it. Every item in an update asks those people to spend some of that attention. Give it to information that can change what someone decides, does, checks, or deliberately leaves alone. A detail that changes none of those things has little claim on the team’s time.

Ask what the recipient can do with it

In The Vitaver Playbook, Signal vs. Noise asks which facts, commitments, and questions can change the decision. Apply that test before sending a message. A fact can be accurate and interesting while being irrelevant to the choice in front of the reader. Conversely, one verified detail can matter more than a full page of background.

Consider two updates. “We met with infrastructure and reviewed the backup status” tells a reader what the team did. “The backup failed at 2 a.m. Please hold the release until the infrastructure lead verifies a usable recovery point” gives the release owner a decision. Add where to verify the failure and when the next update will arrive. Put supporting detail within reach so the owner can check the claim quickly.

The U.S. Government Accountability Office makes a related point in its work on performance information. Managers need to use it to identify problems, improve results, and make decisions. A report finds its purpose when someone can say what they would do differently after reading it.

Give early warnings a place

Useful information can arrive before a decision is due. A supplier’s notice that a component may be discontinued next year deserves a different response from a failure tonight. Assign someone to verify the notice, identify the work that depends on the component, and set a date to review the options. Agree on what would bring that review forward, such as a confirmed end-of-support date that leaves too little time to replace it.

Incomplete information can be important. State what is known and what remains uncertain. If someone reports a possible serious problem, decide who will check it and how soon. Records needed for audit, continuity, or future investigation also have a purpose. Keep them where the people who need them can find them. An immediate alert should reach the people whose decision may change.

Give the reader enough to act

  1. Say what changed. Lead with the new fact and show where it can be checked.
  2. Explain what it affects. Name the decision, commitment, or risk that makes the fact matter.
  3. Make the request explicit. Ask a named person to decide, act, verify, or watch for a defined trigger. State when you need the answer.
  4. Keep the necessary context available. Include evidence that could change the decision, including caveats and contrary facts. Put supporting records where the reader can find them.

Take the next message you are about to send and ask which sentence earns the reader’s attention. If it tells them what deserves a decision, put it first. If you cannot identify a useful decision, action, or future trigger, the team may be better served by leaving the message unsent.

← All Insights