
A Project Premortem Makes Room for Risks Before the Plan Becomes Personal
Use a premortem to surface specific project risks, then turn the useful concerns into owners, early signals and practical responses.

Use a premortem to surface specific project risks, then turn the useful concerns into owners, early signals and practical responses.

Span of control counts direct reports, but team complexity and management duties determine what that count demands from a leader.

Review a recurring meeting by locating the decision it serves, then retire or redesign it with a clear handover instead of leaving a permanent calendar habit.

Use a visible work-in-progress limit to expose competing commitments, finish started work and make exceptions an explicit team decision.

Before collecting feedback, explain who contributes advice, who approves and who owns the decision so consultation does not become an accidental veto.

Review leave requests with a visible coverage plan so approval does not depend on an absent colleague quietly continuing to work.

Define the authority, end date and return handover for a temporary team role so short-term cover does not become an unclear permanent arrangement.

Give a team a simple way to distinguish urgent interruptions from questions that can wait, without making colleagues afraid to raise a real problem.

Prepare a skip-level meeting with a clear purpose, agreed confidentiality limits and a follow-up route that avoids conflicting instructions.