antimeme.ai

Often Misunderstood: IC → M Transitions

essay

Some thoughts on management transitions in the form of how I usually support my people in doing so--or not, toward shedding light on the moment.

This has come up frequently in my recent past so I've generalized the advice I've been giving to folks interested in transitioning into management into this little essay. My experience with this is rooted in software orgs in tech companies--your mileage may vary in other contexts.

These are just my opinions--certainly not those of my employer. I don't claim to have career transitions all figured out by any means! That said, I do hope that some of you may find some of this useful.

I will use software engineer to software manager on my team as the example for the following. We'll also assume that the other factors for this person--performance, lived company values, org culture, viable opportunity, and so forth are unimpeachable.

So, you want to be an engineering manager.

My first question is:

"Why?"

There are as many valid answers to this as their are aspirants. As a leader considering whether and how to assist you in realizing your goal, I need to see that you have a "why," and that it is thoughtful and carefully considered. To me, the character of someone's "why" is far and away the most important ingredient.

Flavors of "why" that signal to me that you need more time and more coaching include:

  • If I was the manager, everything would go well/great/perfect/etc.

  • I'm sick of how people do things and want to set them straight.

  • I have done an outstanding job as a senior engineer and this is the next step, right?

  • Managers make more money than equivalent-level engineers and do less work (spoiler alert: Not true true anywhere I've been on either point).

  • No one wants to do the work I think is most important, so I want to take over so I can make them.

These are all variations of answers to "why?" that I've gotten from folks in such conversations. There are others, but I picked these because they center around control, misunderstanding what a manager does, and seeking power to prevail in conflicts. I still love having these conversations though, because they provide a nice gateway into their next stage of coaching and development (maybe a good topic for a future post).

Flavors of "why" that, to me, motivate a thorough exploration of a management transition for someone in my org:

  • I've come to realize that enabling others is my primary motivation at work.

  • I enjoy the puzzle of aligning work and priorities with our sister teams to get bigger things done.

  • I'm reaching the limits of my interest in developing myself as an engineer but I still love delivering software, in particular through making others better.

  • I love earning buy-in and building consensus--and have come to value those moments far more than shipping my individual tasks.

Similarly, these are all answers that I've heard--I picked these as examples because they demonstrate putting others first, mature introspection, and a recognition that manager is a completely different job.

In cases where the person's "why" is thoughtful and some flavor of motivating, my next phase is laying out, as best I can, what this person is getting themselves into if they do realize a transition to management.

"What."

Every company is a little different, however I've come to believe that a technical manager, broadly construed, has four technical competency areas: People, Product, Program, and Technology. We also have a fifth column, which is by far the most important: Leadership. I've found that this formulation works regardless of the company's particular style in written role guidelines.

[N. B. The difference between management as set of techniques and leadership as a concept is a deep topic that I won't treat in this post--please accept the distinction for our purposes here. P.]

At the very earliest stages of coaching an employee through a potential management transition, I sit down with them for a series of long one-on-ones in which I go through my view of what the manager's responsibility is. The goal with this is to impress upon them that it is a completely different job than the one they've already found success in doing and to start a broad conversation about the kinds of professional development that the org will need to provide to them toward success.

Here's a lite version:

People.

People management is a basket of difficult and uncomfortable tensions that a manager is constantly adjusting. For me personally, and what I teach, the fundamental theorem of people management is:

Your reports rely on their jobs to feed their loved ones, stay warm in the winter, and make a life for them and theirs. The success or failure of your team has massive implications for their real life outcomes.

Internalizing and recognizing the gravity of management actions on material outcomes for fellow human beings is non-negotiable for leaders in my org.

From this, compassion and empathy as the cornerstones of people management follows. The first tension, then, of people management is balancing investment in an individual with uplifting the team as a collective. This is a rich topic worth a post of its own. When engaged in performance management, including termination, the manager is absolved of neither the gravity nor the necessity of decisive, compassionate, and thoughtful action.

On a lighter note, I then sketch earning, maintaining, and troubleshooting daily, weekly, etc. buy-in from the team. The manager must find ways to weave the team's work today into each individual's dreams, hopes, and goals to build individual motivation on the one hand, and framing the same coherently with the long-term, big picture for the company and our customers on the other.

Other topics for the People pillar include the character of one-on-ones, career conversations, retention, performance reviews, and so on. Each of these deserve a deeper look than we can give them here.

Product.

Abusing the word "product" here, the manager owns the vision, strategy, and narrative underpinning everything in their space whether they run an actual product team or are down deep in the infrastructure. This means developing a deep understanding of where you are such that you can think sensibly about where you want to go. Which is only the beginning of the effort--from there you have to sell your vision to your leadership, peers, partners, and, most critically, your own team.

One primary tension here is between advancing a vision that you believe in, that you've developed depth of conviction for, and integrating the views of others toward earning buy-in and the practical ability to pursue delivery. This is, again, quite a rich topic! I usually teach the importance of seeking to disconfirm one's beliefs as an abstraction to use in negotiating coherence and consensus.

Another is between what you want to do in your org toward your incentives and what matters for the company during a given season. Ultimately, the business success of the company underwrites everything else--and I expect to see that reflected over time in well-developed strategies. Sometimes you can restructure your existing vision to meet the company's present moment, sometimes you can't. In all cases, how you talk about change--real or perceived--is critically important to maintaining the faith of your team.

Here also is where I call out writing as the single most important technical skill for leaders--and invite the employee to start thinking about storytelling as a central function of the manager's role. That their audience is everyone from their most junior reports up through the most senior leaders--the story must become coherent at every level over time.

Program.

Whether you have PM/TPM support or not, delivery and operations are the ultimate responsibility of the manager. This is where things get real--and without it, excelling in the other areas tends to not matter very much. No matter how it's done, you have to understand and direct the efforts of your team in a way that is increasingly predictable, meets or exceeds expectations (that you should be actively managing), and most importantly, delivers results that matter.

A well-run program resulting in achieving all stated goals ahead of schedule and below budget means literally nothing if you've chosen the wrong goals. This is where Product and Program tie together.

Further, you have to know what your people are doing on any given day and to some degree how that is going--without becoming overbearing to them or impeding their progress. And that doesn't mean what you think is overbearing, it's what they think is overbearing. Micromanagement doesn't work, just don't do it.

I don't subscribe to project or program management systems and only require that my leaders provide inputs that are compatible with my reporting. What I start them thinking about is how to best approach organizing, assigning, and managing execution within the context of their team. Each group is a little different and I'm a strong proponent of using the techniques most effective for a particular team.

Most importantly here, on my view, is building a habit of frequent communication up, down, and sideways. Own mistakes, learn from them, adjust fire, and keep going. There is no magic bullet for delivery. Operations is a different beast, which I may do a dedicated post on in the future.

Technology.

The manager need not, and indeed over time should not, be the technically deepest person on the team. That said, you must be sufficiently deep such that your deepest folks respect your input in technical designs, tradeoff decisions, and troubleshooting. You must continue to learn the technology relevant to your teams after transitioning to management.

This looks like different things for different people and teams. Some managers like to remain somewhat hands on, others lean more into the political and administrative side. I have no issue with any approach so long as the manager keeps themself off of the technical critical path for delivery.

I also extol the virtues of an engineer-driven technical vision, design process, and estimations. Management driving these and similar things by fiat is almost always a pathological sign. You can and should understand and pressure test everything--however trusting your team, especially with estimation, and improving together is almost always the right way to move forward.

This is another topic worthy of a dedicated post, so I'll wrap it up here by saying that the key fact, beyond earning and keeping the respect of your team technically, is that you don't substitute management results with doing IC tasks. In normal conditions, this just hurts your team's development and undermines you.

Leadership.

Leadership means a lot of different things to different people, and even with respect to what it means to me, this post isn't sufficient for the topic. For now I will suffice by calling out the bottom line I put forward to potential new managers:

If your team succeeds, it's their fault. If your team fails, it's your fault. Good, bad, or ugly, everything your team does or fails to do falls on you.

Now this isn't exactly true, managers definitely should be taking credit for the accomplishments of their teams! And, if one of my teams fails that falls on me as squarely as it does their direct leader.

That said, this is the spirit of the thing on my view. This then becomes a call to not only accept the burden, but be willing to take personal risk toward making good on outcomes for your areas of responsibilities. More on this another time.Now what?

Having gone through all of that much more deeply, done several rounds of "homework" for the potential manager to do some writing or talk to certain people, and let a little time go by to digest it all, have followup conversations, and so forth, I ask the next question:

"Based on everything discussed, do you still want to do this?"

For some folks it's yes, for some folks it's no. Both are completely honorable answers. For those who want to proceed, I then design a role transition plan for them--which tend to be so context and company specific that I don't see much profit in explicating the details here. Instead, a couple notes:

  • Try before you buy is very important. I always build in an explicit, graceful, no harm way for the potential manager to back out especially right at the end of the transition before making the role change permanent. I don't want leaders who don't want their roles--and I don't want to lose a good IC over career exploration.

  • The exploratory or transition period is a couple things: the person demonstrating aptitude and sustained interest, the org demonstrating support for new leaders, and the senior leader going the extra mile to enable exploration while back stopping harm on the line team.

OK, that's your team--how does this help me in my journey?

I can't speak to your company, leadership, and specific personal context. My goal here is to outline how I think about helping people who are considering management--and sketch a little bit of the kinds of questions and ideas I put in front of them. I hope that you can find something above helpful to you as you chart your own path.