Proactive retention check-in with Alex after Ian's departure

April 14, 2026 at 4:07 PMpeoplemedium

Situation

Peter initiated a skip-level check-in with Alex de Wergifosse to assess retention risk after Ian's unexpected departure from the Fuzzball team. Committed to recurring check-ins every 3-4 months and established a mutual transparency pact — Peter will warn Alex of any job security issues, Alex will discuss external offers before accepting.

Reasoning

Ian's departure was a wake-up call about being surprised by key talent leaving. Rather than waiting for exit signals, Peter proactively identified at-risk contributors and built direct relationships. The mutual transparency pact creates an early warning system. The meeting also built trust through sharing management philosophy (autonomy, AI strategy, career growth).

Additional Context

Alex is a full-stack generalist with ~10 years experience, building the new product discovery experience in the Portal. The UI/UX team split (Alex to RAT, Jesus to Fuzzball) initially confused him but he now sees it as beneficial for broader technical exposure. Alex praised Justin's management style highly.

Observed Evidence

Fathom recording shows Peter initiated the meeting explicitly to address retention risk. Committed to recurring 3-4 month check-ins. Established mutual transparency pact. Also shared AI strategy (unlikely to hire junior engineers) and career growth philosophy (internal role changes with 1-year commitment).

Matching Patterns

35%
Three-Lever Talent Management(keyword match on retention, same category (people))
30%
Proactive Talent Pipeline Investment(same category (people))

Confidence Breakdown

30/35
Evidence
15/30
Pattern
18/20
Source
5/15
Corroboration

Reasoning Depth Analysis

Org Signal:CTO investing time in IC-level talent signals leadership cares about individual contributors, not just managers
Who Affected:Justin Haynes (validated as strong manager), Jesus (collaboration partner), broader team morale
Precedent:Sets pattern of skip-level retention conversations that could be replicated across org
Consequences:Builds early warning system for departures; surfaced positive feedback about Justin's management
Timing:Triggered by Ian's recent departure — acting while lesson is fresh

Source

reflection

AI Confidence

68%

Related Context

🎥
Alex <> Peter 1:1

fathom

Peter initiated the meeting to proactively address retention risk after Ian's unexpected departure, identifying Alex as a key contributor.

Outcome

No outcome recorded yet.

Decision ID: e5a14f29-ec4c-49d9-a369-c84c0ba84001