Manage Wesley via Greg; set boat-anchor trigger with Chris (preserve optionality)

Situation

In the Chris W 1:1, Peter decided to manage Wesley's performance situation through his Greg relationship rather than moving Wesley onto a PIP or active weekly-1:1 performance track like Cole and Thomas Chin. Assessment: Wesley is capable but slow, requires handholding, won't operate at senior/principal level, but is not a net negative. Chris asked to proactively flag if Wesley becomes a boat anchor on team productivity — that is the threshold for escalation.

Reasoning

Different diagnosis → different treatment. Cole and Thomas Chin have active perf management (weekly 1:1s, owned epics with May exit triggers) because their underperformance is addressable. Wesley is not in the same bucket — capable but slow is a structural level cap, not a fixable gap. A PIP would be the wrong tool and would damage trust with Greg for no net benefit. Greg channel matters (likely Greg-sourced or Greg-adjacent hire, so performance discussion belongs there not in standard ENG perf management). Trigger-based escalation preserves optionality: can always move Wesley to active PM later if Chris flags a boat-anchor effect, but committing now would be premature and wasteful of Chris's bandwidth.

Additional Context

Chris surfaced Wesley during the same 1:1 where he also covered Cole/Thomas Chin and the two-week Jira hygiene commitment. Peter explicitly distinguished Wesley from the Cole/Thomas track rather than treating all three the same.

Observed Evidence

Fathom next-steps section explicitly assigns Manage Wesley’s status with Greg to Peter, and the decision sentence attributes the call to Peter. Chris's AI is Decide Wesley placement w/ Greg; update Peter — confirming the Greg channel was the agreed path.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis