
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.
Practical notes on leading a team, sharing responsibility and turning a discussion into a decision people can use.
Record the next decision →

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.