Made for Engineering Managers
Intervene When Team Friction Threatens Delivery
Also useful for: people in Engineering Managers
20 min
Beginner
Engineering Managers
Engineering Manager
Improve Team Performance
Career outcome:
Avoid Professional Risk
Diagnose team friction from observable facts, measure its sprint impact, and prepare the smallest intervention likely to restore effective delivery.
Create a free account to save your progress and use this Playbook.
Use this when
Two or more team members are clashing, avoiding each other, withholding information, reopening settled decisions, or slowing active sprint work.
You'll need
- Friction summary
- Observed behavior
- Delivery impact
- Private context
- Current urgency
You'll get
- Observed facts separated from assumptions
- Delivery risk rated with supporting evidence
- Proportionate intervention lane selected
- Opening talking points and neutral questions prepared
- A 48-hour follow-up checkpoint defined
By the end of this playbook
You will have:
- Observed facts separated from assumptions
- Delivery risk rated with supporting evidence
- Proportionate intervention lane selected
- Opening talking points and neutral questions prepared
- A 48-hour follow-up checkpoint defined
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
Situation: Two senior engineers disagree about whether to refactor authentication before release. The argument now affects stand-up and pull request reviews. Observed behavior: One engineer interrupted the other three times. A critical pull request has waited two days because each expects the other to act first. Delivery impact: Mobile login testing is blocked, putting the sprint goal at risk by Thursday. Private context: One engineer believes earlier security concerns were dismissed, but that connection isn't confirmed. Urgency: Action needed today
Sample assembled prompt
Facts versus assumptions Facts: - The... - One engineer interrupted the other... - A critical pull request has... - Mobile login testing is blocked. Assumptions to verify: - Either engineer... - The current conflict is caused... - The disagreement is personal rather... Delivery risk: High Reason: A current... Recommended intervention: Separate private conversations, followed... Opening talking points: 1. "The authentication disagreement is now blocking... "I want to separate the technical... "My goal is a clear decision... while the technical lead records the... 48-hour checkpoint: - Improvement: The review... - Escalation sign: Reviews remain withheld,...