Professional Documents
Culture Documents
90 Day Plan
By Jeff Perry
More Than Engineering
Page |1
It’s hard to transition from all-star engineer to new team leader. Many of us have been
there and failed hard. Much of that failure comes because we neglect to plan out how
to take on this new, unfamiliar role. This guide intends to help fix that. Experienced
technical leaders will also find this guide useful to revisit their approach and consider
how they can improve. As a senior leader/executive, you can share this guide and with
those you are trying to grow into leadership positions.
On the other hand, it’s an opportunity for you as a new technical manager to be
introspective and ask if leadership and management is really something you want to do.
Sometimes leadership opportunities get sprung on individuals with no desire to manage
others, or at least little understanding of what challenges leadership will bring. Leading
people means dealing with uncertainty, subjectivity, and feelings – things many
engineers went into their profession to avoid. So as you enter this new chapter of your
career, you’ll have to consider how willing you are to embrace these factors.
Rarely do new engineering managers receive any formal management training. They
often simply learn through observing others or by trial and error. While the school of
hard knocks is a good teacher, it often works slowly.
So I created this 90-day guide to help new technical leaders get through the first three
months by splitting it up into three, one-month phases: Dive into Learning (Days 1-30),
Get Your Groove (Days 31-60), and Personal Assessment (Days 61-90). Before we jump
into the actual process, let’s address some critical things to consider.
Now, that’s not to say that you won’t be involved in technical work, but as a manager
it’s much more important to review, give feedback, and coach rather than create. It’s
okay and important to get into it enough that you know what people are working on
and can assess their work, but you’ll need to resist jumping in and doing a bunch of
projects yourself, especially to escape your management responsibilities. This may be a
tough transition, and a bigger change than you expect. You may miss the technical
creation and design aspects of your work, and desire to move back into a role as an
individual contributor. That’s fine, and the earlier you can decide what’s best for you the
better.
You’ll want to support and help your team, and that’s great. Yet it’s important to
recognize the difference between being helpful and removing an opportunity for
someone else to learn. Often the “trust but verify” approach works well – not needing
to see every detail but paying attention to critical project details and providing
appropriate feedback.
Very important: You’ll need to trust members of your team enough to let them run with
ideas that you may not agree with. This is very hard to do for most new leaders but
extending this confidence in someone can be extremely motivating. It may not work
out, but it will turn into a great learning experience for both of you no matter what
happens.
For those that you lead, this will need to include frequent career conversations. Asking
questions about career goals and what people are trying to accomplish gives a great
context for how to nurture, lead, and provide chances for them to show their value.
Figure out where people are trying to go and check in regularly about it. If they don’t
know what they want to grow into, this is an opportunity to help them chart a path that
is right for them.
To appropriately manage and communicate with your own manager, you’ll need to be
able to give clear updates on project progress and be able to tactfully push back if you
disagree with your leader. Putting it all together – managing up to the boss, down to the
team, and across to peers should be a high priority to get in place during the first 90
days.
Drive by Dan Pink. He covers critical sources of motivation for employees that you can
utilize to invite the best out of others.
Five Dysfunctions of a Team by Patrick Lencioni. This book is also a fictional narrative,
taking you through the development and growth of an executive team from
dysfunctional to high-performance.
Dare to Lead by Brene Brown. Brown’s work is all about how to unlock the great power
of vulnerability, and this book applies it specifically to how important it is in the world
of leadership. It might suggest you do some things that are uncomfortable, and that’s a
good thing.
Don’t be afraid to reach out to someone you really admire that you think can give you
great advice. Direct requests work best and are most personal. You may be surprised by
how willing and helpful experienced leaders will be. Make sure, however, to be a
contributor in these relationships – don’t just be a “taker.” Take personal ownership for
the frequency and the quality of the meetings you have with your mentors, as they are
giving you their time freely.
If you are trying to stay fully technical, often organizations have tracks to continue that
path rather than people management. You can become a senior technical contributor
and often still have opportunities to mentor and help junior employees without direct
management responsibility. You should still have plenty of opportunities to grow and
develop yourself, gaining further mastery of the craft you have grown to love.
Page |9
Encourage Truth
It’s important to make sure that people on your team can be honest about giving you
feedback. As individuals we often have blind spots. Others help us see them, so do all
you can to invite others to help you see what you can’t. Encourage this by being
gracious when you get it, not by acting defensive. Not everyone is willing to do this, so
sometimes you may need to find just one or two people on the team who can really
give it to you straight.
Enjoy the journey and reach out if I can help in any way.
Jeff Perry
jeff@morethan-engineering.com
www.morethan-engineering.com
P a g e | 10
Subscribe to the blog!