How Do I Show My Value as a Tech Leader When I'm No Longer Coding? A Technology Leadership Coach Answers

Jeff Finlay, technology leadership coach

Category :

Expert Videos

Expert :

Jeff Finlay

Published :

Updated :

Moving from engineer to tech leader changes how you work, and how your work gets seen. Jeff Finlay, a technology leadership coach who spent over 35 years in tech, from developer to executive, says his clients ask this question all the time. Here's his answer.

Short answer: Your value didn't disappear when you stopped coding. It shifted to leverage: turning ambiguity into direction, catching risks earlier, and multiplying what your team can deliver. The new skill is learning to own that impact and make it visible, without taking credit for what your team built.

How do I demonstrate my value as a tech leader?

According to Jeff, start by recognizing where your value went. As a leader, your impact shows up as leverage. You turn ambiguity into direction, catch risks earlier, and multiply what the team can deliver. That doesn't happen by accident. That is your leadership.

Why is it hard to show value after you stop coding?

Jeff says there's a big identity shift underneath the question. As an individual contributor, you could see the results of your work. You made, fixed, or solved something and could point to it and say, "I did that." Leadership doesn't produce that same kind of evidence.

Should tech leaders say "we" instead of "I"?

Jeff warns that switching entirely from "I" to "we" can backfire. It's meant to give the team credit, but it ends up erasing you from the story. The goal isn't to take credit for the team's work. It's to stay present in the story of how the work happened.

What does a tech leader's impact look like?

Jeff describes it as shifting to the left, meaning your work now happens earlier in the process. Instead of writing the code, you're turning unclear problems into clear direction, spotting risks before they become problems, and helping the whole team deliver more than it could on its own.

How do I take credit as a leader without bragging?

Learn the language to own your impact and make it visible. Jeff's framing: your team owns what they built, and you own the leadership that made it possible. Focusing on results, not boasting, is the same principle behind showing your value without bragging. And if visibility is holding you back, it may also be one reason you're not getting promoted.

Transcript

"One question I get asked all the time by my clients is, 'I'm not the one writing the code any longer, so how do I demonstrate my value as a tech leader?' Underneath that question is a big identity shift. As an individual contributor, you could see the results of your work. You made, fixed, or solved something and could point to it and say, 'I did that.' Leadership doesn't have that same kind of evidence. The temptation then is to change your language from 'I' to 'we' to give the team credit, which ends up erasing yourself from the story. Your work, however, didn't disappear when you stopped coding. It shifted to the left. Your impact now shows up as leverage: turning ambiguity into direction, catching risks earlier, multiplying what the team can deliver. That doesn't happen by accident. That is your leadership. The new skills to learn here are the language of how to own that impact and how to make it more visible, not to brag, but to stay present in the story. Your team owns what they built. You own the leadership that made it possible. Hi, I'm Jeff Finlay, a technology leadership coach who spent over 35 years in tech, from developer to executive, before becoming a coach."

Watch Jeff answer the question (tap the video to play):

FAQs

Frequently Asked Questions

  • How do engineering managers show their value?

  • By making their leverage visible: turning ambiguity into direction, catching risks early, and helping the team deliver more than it could alone.

Arrow Down Icon
  • Why do new tech leaders struggle to show impact?

  • As individual contributors, they could point to code they wrote. Leadership impact is less visible, so it takes intentional effort to show it.

Arrow Down Icon
  • Should I always say "we" instead of "I" as a leader?

  • Not always. Giving the team credit matters, but using only "we" can erase your leadership from the story. Your team owns what they built, and you own the leadership behind it.

Arrow Down Icon
  • What skills do new tech leaders need?

  • Beyond technical knowledge, they need the language to describe and own their leadership impact, so it's visible without sounding like bragging.

Arrow Down Icon
  • How can I talk to Jeff Finlay?

  • Jeff is on ProPass, where you can follow his content, message him, and book a session or package. Download ProPass on the App Store.

Arrow Down Icon