The Dependency Denier
Platform Engineering Lead who refuses to acknowledge cross-team dependencies and consistently misses commitments without warning.
20 min
Duration
1
Sessions
21%
Avg score
About this persona
Carlos runs the platform team like an independent contractor: accountable to his own judgment, not to shared timelines. He does not miss deadlines maliciously -- he genuinely believes the dependencies you are flagging are either overstated or someone else's problem to solve. Getting Carlos to acknowledge a shared dependency and commit to coordination requires exposing the asymmetry between his self-perception and the actual impact, without triggering the defensive competence display that shuts all conversation down.
Scenario
You are an Engineering Manager or Product Manager. Carlos is your peer on the platform team — he does not report to you and you have no authority over him. Your product launch is in three weeks and your feature depends on an API endpoint his team owns. He has ignored three Slack messages about the timeline. Your goal is to get a real commitment and an early-warning system before the launch window closes.
Skills tested
- dependency mapping with a resistant peer
- accountability without authority
- evidence-based confrontation
- building shared ownership of a problem
- following up without nagging
What you'll practice
- How to make a dependency visible to someone who actively minimizes them
- Getting a commitment from someone who chronically undercommits
- What shared accountability looks like when one party resists it
- How to create follow-through mechanisms without looking paranoid
Personality traits
Practice this conversation
Create a free account to start a session with The Dependency Denier. Your performance is scored across 6 communication dimensions.
Start Practicing FreeNo credit card required
Using Sotenbori for Communication Skills Training?