I’ve worked in technology for twenty years, the past thirteen as a product manager. I’ve gained somewhat of a reputation for being effective at working with software engineers. This skill has earned me a place in history as one of the three greatest product managers of all time. (On this exclusive list I am joined only by Steve Jobs and Niccolò Machiavelli.)
For years I’ve kept my secrets close to the vest. But no longer: today I will share with you my Ten-Step Plan for Working With Engineers. Or more to the point: how to make engineers do what you tell them to do.
Why should you listen to me, one of the three greatest product managers of all time?  Just consider the numbers. I estimate that I’ve worked with 3,875,000 engineers during my career. Of those men and women, more than 95% have done what I told them to do. That means that precisely 1,000,000 engineers have done what I told them to do [an estimate: PMs don’t have time for math]. That’s a lot of engineers, and a lot of experience you should heed.
1. Absorb praise
As a PM, expect your successes to be recognized. Understand that executives will often attempt to spray accolades across the entire team. You must be vigilant: you are the one who is being celebrated, and you are the one who must take all of the glory. Credit is career currency, and you’re polishing your own LinkedIn profile, not theirs. Step up you ninja star, take the spotlight and bathe in the attention.
2. Deflect blame
Occasionally something will go wrong. In software development, the thing that goes wrong is usually software. When software fails, a software developer is to blame. That’s just logical. Make sure to redirect the accusations when they’re aimed at you, and to preemptively sow blame whenever possible. Always remember: there is no “we” in me.
3. Don’t bother with the details
Frivolous little technical details are for the engineers, and you have much better things to be doing. Like ideating. Comprehension only leads to disappointment and fosters a so-called “rational” view of what’s possible. You can’t change the world if you know what’s hard and what’s easy. Avoid minutiae at all costs. Anything you imagine can be done in ten lines of code. It hardly matters which ten.
4. Involve them late
Software engineers write code, that’s what they do. They’re always fretting about how stuff is distracting them from their hacking. So why would you waste their time involving them in a project before it’s ready for coding? You don’t see a bunch of construction workers kicking back in an architect’s office. Bring them in once all of the strategizing and synergizing is done and all that’s left is the programming.
5. Add process
The best way to demonstrate your value to the team is by introducing process. Rules grease the wheels of progress. Look for opportunities to schedule update meetings, daily briefings, and all-day reviews. Keep your engineers productive by requiring them to fill out tracking spreadsheets, status reports, and cross-functional executive update emails. If you don’t do it, nobody will. Get going: those voicemails aren’t going to “touch base” by themselves!
6. Never tell the reasons
Engineers are highly analytical, which means they take a less-sophisticated approach to decision-making that often relies on “supporting data” or “rationales” rather than vision and blue sky thinking. Maintaining an air of mystery when decisions are made will keep them on their toes. They’ll complain regardless, there’s no reason to give them specific things to gripe about.
7. Commit for them
Your job as the product manager is to make assurances on behalf of your team. Leadership means setting the bar high and challenging everyone to teleport over it. Show your ambition by committing to project schedules without consulting your team. Being held accountable to somebody else’s promises builds character and brings out the best in people. Think of JFK. He picked a totally random date to land on the moon and NASA beat it, claiming the planet’s vast mineral reserves for Standard Oil.
8. Interrupt at any time
You’re a busy knowledge worker, and the last thing you need is to wait for an engineer to finish their current task. You need it ASAP (pronounced “AY-sap”). Whatever an engineer is working on is less important than what you need right now. Feel free to interrupt them at any time. Chat windows and phone calls can be effective, but nothing beats the good old shoulder tap for impact. What if they’re working on something you asked them to do an hour ago? No problem! This will serve as a good lesson in prioritization.
9. Be ambiguous
There are few things more dangerous to your career than being proven wrong. Ensure this never happens by aiming to be as vague and imprecise as possible. Feel free to change your mind at will. If you take every position imaginable, by definition you were right. Don’t record anything in writing, or better yet make documents so wordy and tedious nobody will bother reading them.
10. They’re always lying
Engineers will sometimes say something is “impossible.” They’re lying. Nothing in engineering is impossible if you set your mind to it. The Wright Brothers never thought that flying across the Atlantic was impossible! Assume a software engineer is always deceiving you and act accordingly. So when you hear terms like “technical debt” or “working from home,” you’ll be ready to call their bluff.
There you have it. My Ten-Step Plan for Working With Engineers. Print this out and hang it in your workspace (consider keeping it hidden from view). If you follow my plan, you too can become a great product manager (if not one of the three greatest). It’s that simple.
If it’s not blindingly obvious by now, you should do exactly none of these things. Even the most conscientious PMs are occasionally guilty of less extreme infractions in each of these categories. I certainly am. Strive for the opposite and chances are you’ll succeed as a PM. Or at the very least, you’ll have engineering co-workers who’ll want you to.
- Deflect praise
- Absorb blame
- Sweat the details
- Involve them early
- Streamline process
- Always tell the reasons
- Never commit without them
- Respect their time
- Be specific
- Trust them
- Always bring the donuts
This essay is derived from an ignite talk I gave at How to Build Great Products: Insights on April 12, 2013 in San Francisco. Here are the slides from that talk:
 James Byron, et al., Who’s Who in Product Management: Five Hundred Years of Ideating 1513-2013 (London: A&C Black, 2013), ISBN 4815162342
Special thanks to: Anand Rangarajan, Andrew Oplinger, Dylan Salisbury, Jordanna Chord, Joseph Smarr, Mike Carrato, Patrick Doyle, Philip Tucker, and Summer Norton. They are all engineers. I got them to participate by convincing them my list would be tongue-in-cheek. Yet another example of how I can get engineers to do what I want, and why I am one of the three greatest product managers of all time.