
Start an incident review with a shared timeline before assigning explanations
Build a shared incident timeline from evidence before deciding causes, then turn the review into owned actions with clear checks.

Build a shared incident timeline from evidence before deciding causes, then turn the review into owned actions with clear checks.

Make feedback to a manager more useful by describing an observable decision, its work impact and a specific request for the next situation.

Cancelling a project does not automatically close its orders, access and obligations. Give the team a short, explicit plan for the remaining work.

Define when a project issue needs escalation, who receives it and what information helps them make a decision.

Identify project dependencies by naming the input, owner and acceptance condition, then distinguish them from ordinary tasks that can proceed independently.

Use a meeting parking lot to preserve off-agenda questions with an owner and review route, instead of letting deferred issues disappear after the call.

Prevent two teams from owning the same live queue by agreeing a cutover time, a shared work list and a route for late updates.

Calling a decision reversible is useful only when the team knows how to reverse it. Define the scope, review point and exit cost before experimenting.

Use leading indicators to examine activities that may influence results, while keeping the actual outcome visible and avoiding easy-to-game targets.