The Paradox Nobody Prepares You For
You were excellent at the technical work. That's why you got promoted. And now the skills that made you excellent are, in certain ways, working against you.
The ability to solve complex problems quickly — invaluable as an engineer — becomes a liability when you jump in to solve problems your team should be solving themselves. The precision required for good code can turn into inflexibility with the messiness of human systems. The introverted focus that allows deep technical work can make the constant interpersonal demands of leadership feel depleting.
None of this makes you a bad leader. It makes you a technical leader at the beginning of the real work.
“The best engineering managers I’ve worked with didn’t stop thinking like engineers. They learned to apply that same rigorous curiosity to their inner world — to understand what was driving their behavior with the same precision they brought to a codebase.”
— Scott Friedman, Thought Coaching Practitioner
The 4 Ways Technical Excellence Creates Leadership Challenges
The Problem-Solving Default
Engineers are trained to solve problems efficiently. In leadership, that instinct becomes a problem when it means solving problems for your team rather than developing their capacity to solve them. Every time you jump in with the answer, you're buying a short-term win at the cost of long-term team development.
The Precision Preference
Technical work rewards clear right-and-wrong answers. Leadership is almost entirely ambiguous. Tech managers who need clarity before they can act struggle with the essential fog of leading humans. The work is building internal stability to act thoughtfully without complete information.
The Introversion Drain
Many tech managers are carefully managing their energy just to meet the extroverted demands of the role — difficult conversations, cross-functional relationships, ongoing emotional labor — with nothing left for the deeper inner work that would actually make them better leaders.
The Credential Gap
Technical credibility is objective. Leadership credibility is relational. Tech managers who still privately think of themselves as engineers in a management role often over-rely on technical expertise — which recreates the problem-solving trap all over again.
What Tech Managers Actually Need to Develop
Skill 1
The Art of the Good Question
The transition from technical expert to leader is largely a transition from answers to questions.
These questions feel slower. They are slower. They also produce something direct answers never will: a team that can function without you.
Skill 2
Thought Awareness Under Pressure
The moments that define tech managers' leadership reputations are almost never the technical decisions. They're the pressure moments — the production incident at 2am, the missed deadline conversation, the architectural disagreement that gets heated.
Learning to notice those thoughts before they become reactions — creating even a small gap between stimulus and response — is one of the highest-leverage developmental practices available to a technical leader. That gap is where leadership happens.
Skill 3
Emotional Intelligence as a Learnable Skill
The ability to read a room. To notice when a team member is struggling before they say anything. To deliver critical feedback in a way that's received rather than defended against. These are skills built through honest self-observation and consistent practice — not personality assessments.
Skill 4
Strategic Thinking
Technical managers are often tactically excellent and strategically underdeveloped — not because they lack the capacity, but because strategy hasn't been required before. Leadership requires holding the longer view and making current decisions through that lens. Most tech managers don't do this because the tactical demands are so immediate and so loud.
The Core Insight
A thought is a thought — and may or may not be true. The thought patterns that drove your technical success aren’t always the ones that will make you an effective leader. Seeing that distinction clearly is where the real development begins.
How Scott Works With Tech Managers
The Model
Phone or Video — Zero Upfront Cost
Scott works with tech managers by phone or video — fitting naturally into even the most demanding engineering leadership schedules. Sessions are 45–60 minutes, typically weekly. Most clients begin noticing real shifts in their leadership within 4–8 weeks.
And the model is unlike anything else: you pay nothing upfront. At the successful conclusion of coaching, you pay what you believe it was worth — and only what you can afford.
Ready to Grow Into the Leader Your Team Needs?
Start with a free discovery call. No pressure, no sales pitch, nothing upfront. Bring the specific leadership challenge you're facing and let's look at what's actually driving it — and what would change if it weren't.
You can also explore Scott's coaching services, read more about his background, or browse other leadership articles.