Personnel action plan from effort/impact matrix review
Situation
Conducted comprehensive effort vs. impact performance review of ~20 engineers across kernel and platform teams, resulting in specific personnel actions: underperformers on short improvement timelines or face replacement, one engineer to be replaced with a high-impact hire, one engineer requires direct performance conversation about ownership and visibility, one to be reassigned to simple packaging tasks.
Reasoning
The 2x velocity mandate requires removing drag — can't double output while carrying underperformers. The 'super senior guy in the corner' archetype (high depth, low effort) is about to be obsoleted by AI, collapsing the economic argument for tolerating low-effort seniors. Single points of failure (Secure Boot, STIG) are unacceptable risk requiring cross-training before any exits. The effort/impact matrix provides an objective, data-driven framework for personnel decisions.
Additional Context
Full-day in-person Linux Leadership Sync in San Jose with Nathan, Justin, Max. Part of operationalizing the 2x engineering velocity mandate set the day before.
Observed Evidence
Fathom Pt 1: Detailed effort/impact matrix review of kernel and platform teams. Specific action items assigned to Peter: 'Initiate a direct performance conversation with Michael', 'Replace [engineer] with a high-impact engineer'. Nathan assigned: 'Set a short-term improvement plan for Jason and Brett', 'Reassign Fathom to simple packaging tasks', 'Cross-train Joseph, Skip, and Andrew on Secure Boot'.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
Related Context
fathom
Performance review using effort/impact matrix; critical underperformers identified with short timelines to improve or face replacement
fathom
Debate between 'hard reset' via staffing changes vs 'North Star' vision document approach
Outcome
No outcome recorded yet.
Decision ID: 3d18c389-6763-47b0-9f58-609ba644ea01