Skip to content

Team Lead / Engineering Manager perspective ​

Lens: Team health and throughput — sustainable pace, review capacity, hiring/onboarding, and escalation when gates stall.

Phase by phase ​

PhaseYour jobKey artifactsGuides & SOPs
PlanCapacity vs commitmentSprint/PI capacitySOP-001
DefineEnsure ARCH bandwidth for ADRsARB queueGovernance
BuildProtect focus; AI tool complianceTeam conventionsAI coding tools · SOP-010
VerifyReview assignment; stale PR SLAReview rotationSOP-005
ReleaseT1 deploy approval (with SRE)Deploy calendarSOP-006
OperateOn-call fairness; burnoutRotation scheduleSOP-007
LearnPostmortem culture; action closureTeam retro themesSOP-008

Metrics you own ​

MetricTarget direction
PR cycle time (median)Down
Main branch CI pass rateUp (>95%)
Review queue ageDown (<1 day)
ADR/spec block timeDown
Escaped defectsDown quarter-over-quarter

Escalation paths you own ​

IssueAction
Review bottleneckAssign reviewers; reduce WIP
Gate bypass pressureReinforce G1/G2 with leadership
Non-security exceptionApprove via SOP-012
Repeat incidentsResource postmortem actions

Onboarding ​

New engineers: SOP-011 · Developer workflow

Pitfalls (Team Lead view) ​

PitfallMitigation
Hero culture on incidentsRotate; blameless postmortems
Unlimited AI tool sprawlStandardize + SEC policy
Skipping onboarding on AI policyDay 1 acknowledgment
Measuring output by commitsOutcome + flow metrics

← All roles

Reference template only — no production code. Adapt in your own project.