Why great ICs struggle as leaders

November 17, 2026

I'm in the process of transitioning one of my best engineers into the VP of Engineering at Distru. Doing so has helped me realize just how unintuitive leadership is in the beginning.

The expectations and reward systems that have been ingrained into you over years of being an IC are completely different from those of a leader. I believe, for any transition to succeed, the first step is to reframe what expectations and rewards look like for a leader.

Every other tactical skill builds off of this core reframing, because without it, you will lack the confidence and proper focus required to execute on anything else.

The need to operate horizontally

When I think of a great IC, I think of someone who can:

  • Be a subject matter expert in what they're working on
  • Own a piece of the puzzle and be responsible for its success
  • Communicate their thoughts and concerns to leadership frequently

This is because success at the IC level is measured by how well they can execute their piece of the puzzle. This requires someone to turn on blinders (to some extent) and operate vertically.

However, when I think of a leader, I think of someone who can:

  • Be an organization matter expert for an initiative
  • Own the whole puzzle and be responsible for its success
  • Gather thoughts and concerns from the org to build signal and conviction

Contrary to ICs, success at the leadership level is measured by how well the organization can execute the whole puzzle. This requires someone to remove as many blinders as possible, and operate horizontally.

A way to visualize this is the difference between a cop busting a drug dealer and the FBI taking down an entire crime syndicate. The drug dealer is only one piece of the puzzle, but the cop has no idea how important that piece is (or isn't).

Horizontal thinking is a skill that you must develop to cross this chasm from IC to leadership. This is a more involved topic that I've written about in Why new leaders solve the wrong problems: why you can't take the problems people bring you at face value, and how to run them through signals, context and conviction before you solve anything. Your vertical skills don't go away. A great leader does both, and knows when to use which. I highly recommend you read it if you want to reframe how to think and approach problems as a leader.

Delayed gratification as the new reward system

I think the same mechanism that keeps people hooked on IC work is the same one behind gambling and short-form content. It's the instant and very visible gratification you get from a clearly measurable success.

This is the hardest psychological step to overcome when you become a leader: the acceptance that leaders have very delayed, and sometimes no, gratification in the work that they do.

Here at Distru, we've transitioned a couple of people now into true leadership roles, and here are some direct quotes that they said to me during their transition experience:

"I feel like most days, I don't even know what I do. I'm just in meetings, talking to people all the time, and somehow that's moving the needle."

"My day has become about doing random little things everywhere, and I feel like there isn't any one thing that I'm actively making a difference on."

I've had these same feelings before, and it's taken me years to realize that these feelings were never the problem. The problem was me thinking that I should have felt differently, because I was so addicted to the instant gratification of IC work.

As a leader, you should measure your success by:

  • How much ROI your department is generating
  • How well your reports are able to execute, both independently and cross-functionally
  • How aligned your department is with the company's goals and vision

When you aren't doing these things well, there are clear signs, and quickly. However, if you are doing them well, it could take months or even years before you truly notice, and even then, it's hard to attribute it directly as a result of anything specific you did.

On any given day, my schedule could look something like this:

  • 8AM-9AM: Technical leadership alignment
  • 9AM-10AM: AI initiative leadership alignment
  • 10AM-11AM: 1:1 with a report about a specific project/problem/idea they have
  • 11AM-12PM: An interview with a candidate
  • 12PM-1PM: Eat, walk my dogs, reply to Slack
  • 1PM-3PM: Noticed an issue in Slack about a project, and started to talk to various people on calls to get their perspectives
  • 3PM-5PM: One of those calls revealed another misalignment, so I started to talk to more people to get perspective
  • 5PM-6PM: Gathering all my thoughts, distributing context to others, and setting next steps for myself

On a day-by-day basis, it's easy to feel like my days are scattered, random and unproductive. But enough of this over time allows you to build a god's-eye view and make decisions that could impact the org in ways that are hard to imagine in any given moment.

Leadership is a long game, and it requires you to do a lot of work with no clear and immediate outcomes. However, if you can accept this and execute in spite of it, you'll eventually realize that despite not having clear impact in every single moment, the sum of all your work and presence is what's moving the entire organization forward.


📧 johnny@johnnyji.com