Made for Engineering Managers
Address Underperformance Before It Becomes a Formal Crisis
Also useful for: people in Engineering Managers
75 min
Advanced
Engineering Managers
Engineering Manager
Become a Better Manager
Career outcome:
Avoid Professional Risk
Turn scattered performance concerns into a fair, evidence-based improvement plan with clear expectations, support, checkpoints, and escalation triggers.
Create a free account to save your progress and use this Playbook.
Use this when
A team member is repeatedly missing expectations, feedback hasn't produced enough change, or a concerning pattern is starting to affect delivery and trust.
You'll need
- Role and level
- Expected performance
- Evidence and timeline
- Prior feedback and support
- Impact
- Environment factors
- Policy constraints
- Improvement window
- Conversation date
You'll get
- Observed facts separated from interpretations
- Primary performance gaps tied to role expectations
- Skill, clarity, motivation, and environment hypotheses assessed
- Conversation opening and diagnostic questions prepared
- Improvement outcomes and measures documented
- Support commitments assigned
By the end of this playbook
You will have:
- Observed facts separated from interpretations
- Primary performance gaps tied to role expectations
- Skill, clarity, motivation, and environment hypotheses assessed
- Conversation opening and diagnostic questions prepared
- Improvement outcomes and measures documented
- Support commitments assigned
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
Role and level: Senior Software Engineer expected to lead medium-sized backend projects. Expected performance: Plan work independently, review dependencies early, escalate delivery risks, and provide reliable status updates. Evidence: Two projects missed internal milestones after known dependencies weren't raised until the final week. A design review also arrived four days late without rollback coverage. Prior feedback: Late risk escalation was discussed twice in one-on-ones. A planning template and staff engineer pairing were provided. Impact: A launch moved four business days, and two engineers paused other work to add missing safeguards. Environment: Priorities changed twice, ownership with the platform team is unclear, and on-call coverage is thin. Policy: HR review is required before any formal process. Improvement window: 30 days. Conversation date: June 18, 2026.
Sample assembled prompt
Primary assessment: A repeated planning and... Skill and clarity remain plausible causes. Motivation isn't supported by current evidence. Environment contributes through unclear platform ownership... Recommended response: Hold a documented coaching... Confirm the wording with HR before... Priority outcome 1: Surface material delivery... Measure: Risk recorded in the project... Support: Weekly 20-minute planning review for... Checkpoint: June 25. Sufficient progress: All known material risks... Opening: "I want to talk directly... On the last two projects, known... That contributed to a four-day launch... We've discussed earlier escalation before, so... Before we agree on the plan,...