What does it mean that information flow within teams?

The right information reaching the right people at the right time is a design problem, not an accident. Information flow is the circulatory system of team cognition — when it is blocked, restricted, or misdirected, the team's cognitive capacity degrades regardless of individual talent.

Example: A platform team at an e-commerce company had seven engineers and a product manager. When the product manager learned about a major customer complaint regarding checkout latency, she mentioned it in the weekly stand-up. The backend engineer who owned the checkout service was out sick that day. The information was noted in the stand-up summary, which was posted in a Slack channel with 47 other updates from that week. The engineer returned two days later and did not read the backlog. Meanwhile, a separate customer escalation reached the CTO, who asked the VP of Engineering why checkout latency had not been addressed. The VP asked the engineering manager, who asked the product manager, who said she had raised it in stand-up. The backend engineer, when finally informed directly, diagnosed and fixed the issue in three hours. The fix itself was straightforward. The information routing failure — the thirteen-day gap between when the problem was known by the team and when it reached the person who could solve it — cost the company an estimated $340,000 in lost conversions. The engineering manager, David, mapped the information flow and found seven handoff points between the customer complaint and the engineer's awareness, each with a probability of failure. The compound probability of successful routing through all seven points was less than forty percent.

Try this: Map one critical information flow in your team. Choose a type of information that matters — customer feedback, production alerts, requirement changes, or technical discoveries. Trace its path from origin to the person who acts on it. For each step, answer: (1) How does the information move from point A to point B? (Push or pull? Automated or manual?) (2) What is the latency at this step? (Immediate? Hours? Days?) (3) What is the probability of failure at this step? (What could cause the information to not reach the next point?) Multiply the probabilities of success at each step to get the compound reliability of the flow. If the result is below 80%, the flow has a design problem. Identify the weakest link and redesign it — either by removing a handoff, automating a notification, or adding a redundant path.