Risks, blockers, and tradeoffs belong in the room because they are usually what require leadership attention.
Teams often sanitize operating reviews before leadership sees them. Risks become watchouts. Blockers become dependencies. Tradeoffs become “alignment needed.” The language gets softer as the stakes get higher. By the time the packet reaches the review, decision material has been converted into presentation material.
This is backwards. The operating review should be one of the safest places to say the hard thing clearly. We cannot hit the date without cutting scope. The customer promise exceeds current implementation capacity. The metric target is creating bad behavior. The hiring plan assumes managers have capacity they do not have. The product bet is consuming more attention than its evidence justifies.
A risk is a forecast of where the system may fail. A blocker is a request for a decision, authority, sequencing, or resources. A tradeoff is the choice the team has been avoiding or absorbing quietly.
The chair has to protect this standard. If bad news is punished, bad news will arrive late and decorated. If every blocker turns into a blame session, people will hide blockers until they become crises. If tradeoffs are treated as lack of creativity, teams will pretend to do everything.
The packet should force precision. For a risk: probability, impact, trigger, owner, mitigation, and decision needed. For a blocker: what is blocked, by whom or what, since when, and what authority is required. For a tradeoff: the actual choice, such as speed versus quality, growth versus margin, customer promise versus roadmap, scope versus date, or centralization versus local autonomy.
Clean reviews do not avoid tension. They make it usable. The room should leave with fewer hidden tradeoffs than it entered with.
