IT leadership coaching — when the technical work has stopped being the hard part.

One-on-one coaching for engineering leaders navigating the part of the job nobody trained you for: conflict, credibility in technical decision-making, delegation that still feels like abdication, and the distance between being technically right and being institutionally heard.

This is coaching informed by therapy training, not therapy. We focus on your professional leadership challenges and effectiveness. For clinical mental health treatment, see my therapy practice.

Currently accepting a limited number of new coaching clients.

Schedule Discovery Call See Results

Two audiences.

You were promoted because you were technically excellent. The proof system that rewarded that excellence stopped compiling the day you became a leader. You now make decisions with incomplete information, manage people you used to be peers with, and navigate politics nobody taught you — and the old sources of confidence do not transfer.

Common Challenges

Former peers now question your technical decisions differently
Can’t get buy-in on architecture despite being technically right
Conflict you don’t know how to de-escalate
Delegation feels like abdication
Feedback conversations you keep avoiding
Losing technical credibility while gaining management responsibility

What You’ll Get

Frameworks for navigating conflict without escalation
Strategies for building credibility in technical decisions
Practical delegation approaches that actually work
Tools for difficult conversations you can use Monday
Ways to maintain technical respect while leading
Clarity on when you’re the problem vs. when it’s the system

Where this coaching goes deepest.

Three intersections where technical complexity and human dynamics keep colliding. Outside these, I work more broadly; inside them, forty years of engineering plus therapy training creates the most leverage.

Conflict and Credibility in Technical Decision-Making

You’re the most technically competent person in the room, but you can’t get buy-in. Architecture decisions turn into political battles. Peers undermine you in meetings. You’re losing credibility despite being right.

What we do: Separate technical disagreement from trust erosion. Build frameworks for high-stakes technical conversations. Address the credibility gap without compromising technical standards.

Typical outcome: Clear path to decision alignment. Stronger peer relationships. Executive-level influence on architecture.

Escalation Loops and Stakeholder Warfare

Weekly escalations to your boss or skip-level. Product and engineering at each other’s throats. You’re caught between competing priorities and broken trust. Every technical decision becomes a political fight.

What we do: Diagnose the real conflict beneath the surface. Build repair strategies for damaged relationships. Create frameworks for managing up when trust is broken.

Typical outcome: Escalation pattern stops. Stakeholder relationships stabilize. You regain agency in decision-making.

Leading Through Change Without Burning Out

Org restructure, merger, major platform migration, and you’re supposed to keep the team motivated while everything’s on fire. You’re drowning, your team senses it, and you can’t show weakness.

What we do: Build sustainable leadership practices under pressure. Navigate team dynamics during uncertainty. Separate your anxiety from your team’s needs.

Typical outcome: Team stability maintained. Personal burnout avoided. Clear leadership through transition.

I also work with clients on executive presence, career transitions, and team dynamics. But these three intersections are where the combination of technical depth and therapeutic training creates the most leverage.

Research supports the impact of leadership development on outcomes: Harvard Business Review and the Center for Creative Leadership document how coaching and development improve leader effectiveness and retention; the U.S. Bureau of Labor Statistics notes the role of leadership skills in career advancement.

Recent cases.

Three recent cases. Each addresses both the technical substance and the human dynamic underneath — which is where most leadership problems actually sit.

Weekly escalations to architecture buy-in

The situation. An engineering manager locked in weekly escalation loops with product leadership over architecture. The team was watching their leader get undermined. Technical arguments kept turning into political ones; every exchange widened the trust gap.

The work. We separated the technical disagreement from the trust erosion underneath — two problems layered together that were being debated as one. Practiced specific framing for architecture conversations. Addressed the underlying credibility gap without compromising on technical standards.

The outcome. The escalation pattern stopped within three weeks. Got buy-in on a critical refactoring decision that had been blocked for months. Peer relationships improved across the org, not just with the one counterpart.

Drowning in meetings to strategic director

The situation. A senior engineer promoted to director. No time for technical work. Every meeting felt mandatory. The team’s morale was declining and their technical credibility with it. The pattern had a name the director couldn’t yet see: "should" beliefs about what leadership required, inherited from nowhere in particular, blocking every delegation attempt.

The work. Identified the hidden beliefs about what a director "should" do. Built the delegation muscle — not as a time-management technique, but as a trust practice. Created a working criteria framework for meeting attendance and scope decisions.

The outcome. Ten hours a week reclaimed. Three major projects successfully delegated. Team engagement scores up twenty percent within the quarter.

"Executive presence" feedback to a VP role

The situation. An engineering manager was ready for a VP role on substance but kept getting feedback about "executive presence." The technical work was strong. The strategic vision existed. It just wasn’t landing with senior leadership — and nobody could explain what exactly to change.

The work. Developed a strategic communication framework for speaking upward. Practiced navigating ambiguity and influencing without direct authority. Built the confidence to have real conversations with senior stakeholders — not polished performances.

The outcome. Positioned for and landed the VP role. Now leads architecture strategy for a larger organization with a clearer executive voice. The feedback stopped.

All examples anonymized. Results vary based on individual context, organizational support, and sustained effort.

Why the combination helps.

Deep technical credibility: Forty years building systems, leading teams, making architecture calls under pressure, navigating organizational politics. I’ve lived in your world. I speak the language without translation.
Therapist’s lens on leadership: Licensed therapist trained in emotional patterns, conflict dynamics, and relational complexity. I see what’s happening beneath the technical debate: trust gaps, unspoken resentment, fear masking as disagreement.
Practical strategies, not theory: Frameworks you can use in today’s standup, tomorrow’s one-on-one, next week’s architecture review. Strategies that work when you’re stressed, understaffed, and under deadline — because those are the conditions that produce the most leadership problems in the first place.
Confidential and safe: What we discuss stays between us. No judgment. No impact on your professional reputation. A space to examine your doubts, fears, and blind spots without the performance leadership usually requires.

Leadership development is linked to better team and organizational outcomes (Harvard Business Review; Center for Creative Leadership; BLS).

How coaching works.

Discovery call (30 minutes)

We identify what’s stuck, your fastest leverage point, and whether coaching is the right fit. Honest assessment, not a sales pitch.
Initial sessions

The first two or three sessions focus on understanding the patterns at play, clarifying goals, and building practical frameworks you can start using immediately.
Ongoing work

Biweekly or monthly sessions, your choice. We address challenges as they emerge, refine strategies, and build the leadership practices that hold up under pressure.
Integration

Between sessions, you apply frameworks, test strategies, and gather data from real work. Sessions become the lab where we debrief, adjust, and deepen the work.

Frequently Asked Questions

What is IT leadership coaching?

IT leadership coaching is 1-on-1 development for engineering managers and technical leaders. It combines technical credibility with therapeutic insight to address conflict, credibility in technical decision-making, delegation, and the gap between technical expertise and executive influence—without being therapy.

Who is IT leadership coaching for?

It serves two groups: (1) New or struggling managers—former peers who now question your technical decisions, can’t get buy-in on architecture, face conflict you don’t know how to de-escalate, or avoid feedback conversations. (2) Senior leaders developing teams—managers who are technically strong but struggle to lead, escalate too often, or lack executive presence.

How does IT leadership coaching work?

We start with a 30-minute discovery call to identify what’s stuck and whether coaching fits. Then 2–3 initial sessions build frameworks and clarify goals. Ongoing work is biweekly or monthly; between sessions you apply strategies at work and we debrief and refine. Sessions are confidential and focused on professional leadership, not clinical treatment.

How long does coaching take?

Many clients see meaningful progress in 3 months; others choose a 6-month program for deeper change. Session frequency (biweekly or monthly) is your choice. We focus on practical frameworks you can use immediately while building sustainable leadership practices.

Is this coaching or therapy?

This is coaching informed by therapy training, not therapy. We focus on professional leadership challenges, decision-making, conflict, and effectiveness. For clinical mental health treatment, a separate therapy practice is available—see the Therapy page.

About your coach

Rebecca Sutter

IT Leadership Coach & Licensed Therapist

40+ years in software engineering and technical leadership
Licensed Therapist (LGPC/LMHCA)—active clinical practice
Certified Professional Coach
Specializations: Technical leadership, conflict resolution, executive presence, organizational dynamics

I’ve built systems, led teams, and made architecture calls under pressure. I’m also trained to see what’s beneath the technical debate: trust gaps, unspoken resentment, fear masking as disagreement. That combination is what makes this coaching different.

Practical Tech Leader, a book on the discipline of leading engineering organizations, is in final production — read about the book.

A half-hour to see if it fits.

The discovery call is thirty minutes. We identify what’s actually stuck, find the fastest point of leverage, and decide together whether a three-month or six-month engagement fits — or whether coaching isn’t the right tool for what you’re facing.

Schedule Discovery Call