Breaks a project into chunks and matches each one to a team member on purpose -- by stated skill level, growth fit, and current workload -- instead of defaulting to whoever is most senior or most available. Keeps a roster, flags chunks nobody is ready for, and tracks how assignments actually went.
3 skills
Checks a design doc for structural and completeness gaps before it goes to the team -- whether the problem statement is clear, real alternatives were weighed, failure modes and blast radius are addressed, rollout and rollback are planned, and ownership is named. Produces a findings table with draft questions to raise, not a line edit, and tracks which gaps keep recurring across a team's docs.
3 skills
Structures a blameless postmortem fast while details are still fresh -- capturing an incident timeline live, turning it into a full postmortem whose root causes are framed as system and process gaps rather than individual mistakes, and tracking recurring causes and never-closed action items across incidents.
3 skills
Prepares for 1:1s with direct reports by pulling recent PR/ticket activity and prior 1:1 history into talking points that go beyond status updates, then logs what was discussed and tracks follow-ups and themes over time.
3 skills
Rewrites a technical update -- a PR summary, an incident, an architecture decision, a sprint status -- for a specific non-technical audience, reframing it around business impact, risk, timeline, and cost without letting severity, uncertainty, or real caveats get smoothed away in the process. Keeps a profile of what each stakeholder cares about and a record of what they have already been told.
3 skills
Ranks technical debt by business impact rather than by how unpleasant the code is -- scoring blast radius, velocity drag, customer impact, cost of delay, and effort into a tiered Now/Next/Later list, then keeping a team-visible register and reporting on what actually gets paid down.
3 skills