Leadership coaching that combines deep technical credibility with therapeutic insight to address the real blockers: conflict patterns, decision paralysis, and team dysfunction.
40+ years of software engineering experience. Licensed therapist. Real frameworks for Monday's one-on-one, Tuesday's architecture debate, Wednesday's difficult conversation.
Practical frameworks you can use immediately. Not abstract leadership theory—concrete tools for Monday's one-on-one, Tuesday's architecture debate, Wednesday's difficult conversation.
Coaching that understands both the technical challenges (architecture decisions, technical debt, scaling systems) and the human dynamics (trust erosion, unspoken resentments, fear masking as disagreement).
Development that addresses root causes, not surface symptoms. Most leadership training teaches frameworks but doesn't touch the psychological patterns driving the dysfunction—the avoidance, the need to be liked, the inability to hold boundaries.
40+ years of technical leadership experience combined with licensed therapy training gives your managers implementable strategies that work under pressure.
Most tech coaches have IT backgrounds but no training in human psychology. Most executive coaches haven't built distributed systems at 3 AM. I live in both worlds—and that's exactly where your challenges live too.
40+ years building software systems at scale. I've been the CTO making architecture calls under pressure. I understand distributed systems, technical debt, and the politics of refactoring. I speak your language.
Licensed therapist trained in human dynamics, emotional patterns, and relational conflict. I see what's happening beneath the surface: the trust gaps, the unspoken resentments, the fear masking as technical disagreement.
Not theory. Not fluff. Real frameworks you can use in Monday's standup, Tuesday's one-on-one, Wednesday's architecture review. Tools that work when you're stressed, understaffed, and under deadline.
Technical challenges often have emotional roots. Team conflict masks architecture misalignment. Career stuck points hide self-doubt. I help you see and address both dimensions because that's where lasting change happens.
I've spent 40+ years in software engineering—building systems, leading teams, making architecture calls, navigating organizational politics, and learning what actually makes technical leadership work.
But along the way I kept noticing something: brilliant engineers were crashing when they hit people problems. Technically excellent leaders couldn't influence peers. High performers burned out managing teams. The technical skills weren't the issue—the human dynamics were.
That led me to pursue formal training in therapy. I wanted to understand the emotional and relational patterns that shape how we lead, make decisions, and navigate conflict. Now, as a licensed therapist, I bring both technical and psychological expertise to my coaching work.
What's actually possible when you address both the technical and human dimensions:
Situation: Engineering Manager locked in weekly escalation loops with product leadership over architecture decisions. Couldn't influence peers, felt undermined in front of team.
Work we did: Separated technical disagreements from trust issues. Practiced specific framing for architecture conversations. Addressed underlying credibility concerns.
Outcome: Stopped escalation pattern within 3 weeks. Got buy-in on critical refactoring decision. Improved peer relationships across the org.
Situation: Senior Engineer promoted to Director, drowning in meetings, unable to say no, losing technical credibility while team morale declined.
Work we did: Identified hidden "should" beliefs about leadership. Built delegation muscle. Created clear criteria for meeting attendance and scope decisions.
Outcome: Reclaimed 10 hours/week. Delegated three major projects successfully. Team engagement scores improved 20%.
Situation: Engineering Manager ready for VP role but kept getting feedback about "executive presence." Technically strong but couldn't articulate strategic vision to senior leadership.
Work we did: Developed strategic communication framework. Practiced navigating ambiguity and influencing without authority. Built confidence in senior stakeholder conversations.
Outcome: Positioned for and landed VP-level role. Now leads architecture strategy for larger org with clearer executive voice.
All examples anonymized. Results vary based on individual context, commitment, and organizational factors.
In our 30-minute discovery call, we'll: (1) clarify what's actually stuck, (2) identify your fastest leverage point, and (3) decide whether a 3-month sprint or 6-month program fits your situation.
Schedule Discovery Call