If I had to highlight one quality that can influence the success or failure of a product manager, communicating effectively with your engineering team would be high on my list.
In today’s article, we will see some tips that I have been learning throughout my career and that I think can be helpful to get the most out of that relationship.
Are you interested? Well, let’s get to it!
Understand your position
The first step in communicating effectively with your engineering team is understanding your position as a Product Manager. Engineers don’t work for you; they work with you.
Engineering is not there to blindly comply with your demands. They are there to conceive and implement the best possible solutions to the problems and opportunities that you present to them.
You are a guide, not a foreman.
Read Simón’s previous article on how Overengineering can kill your product.
Understand your situation
Your engineers have their own problems, aspirations, and fears. Sit down with them, together and individually, and make an effort to get to know and bond with them.
The information you get from that relationship will help you understand the team’s level of maturity, which will help you find the best way to interact with them and show where you will probably have to focus your time.
For example, with a junior product team, you may have to spend more time than desirable on the execution side. In contrast, a senior team can perfectly organize itself, which should free you up to focus on the more strategic part.
Start with the problem
This point may be the most important one in the whole article. You don’t present a solution to an engineering team; you bring them a problem to solve.
The best engineers won’t willingly accept implementing a solution if they have not participated in defining it. The engineers who do it are usually in consulting firms, not in product companies. And if you treat them like in a consulting firm, they will soon stop being your engineers.
Do your homework
Your mission as a Product Manager is to understand the problem so profoundly that you can introduce it to the team as clearly as if you suffer from it.
Do your homework. Get loaded with qualitative and quantitative information. Engineers have a sixth sense for detecting bullshit. If they feel that you don’t understand the problem, you will lose their confidence and involvement in the initiative.
Explain the why
At the beginning of the 20th century, Carl Braun was a successful engineer running a 6000 people company.
In a Farnam Street post, Carl Braun on communicating like a grown-up, we read how he could fire you on the spot if he found out you had given an order without explaining why.
Starting with the problem is not enough. You have to demonstrate how solving this problem fits with the vision and strategy of the company. Your team also has to understand why you want to solve this particular problem and not any other.
Your team will do a better job the more they believe in it. Make sure you can argue your decision and create an inspiring narrative.
Your engineers want to know if their work impacts the organization. A huge smell that they are working in a feature factory rather than as product engineers is when you don’t define how to measure the success of an initiative.
We don’t measure success by the number of story points that the team manages to get each sprint or the number of functionalities that go out the door. We measure success by moving the needle on the metrics that matter to the business.
If you don’t obsessively communicate the importance of these and can’t get your team interested in them, you’re losing much of their value.
Get them involved early
Invite your engineers to phases of discovery that can be useful to understand the problem we want to solve. Keep them abreast of your ideas and listen to their opinions about them.
If your engineers hear first about an initiative when it is 100% defined, you are not doing a good job. The sooner you involve them in the problem, the easier for them to build the best possible solution.
Don’t isolate them from the outside world
We may think that part of our job as Product Managers is to protect the team from outside influences. It is not.
Facilitate meetings with the stakeholders involved in the initiative so that the team can do the best job possible. Avoid becoming the bottleneck that everything has to go through.
If an engineer needs to speak to User Research, let her do so. If a member of the organization interested in the initiative wants to talk directly with an engineer working on it, let her do so.
If you’ve done your job explaining the problem and why it’s important to solve it, your team should be able to manage itself and decide which meetings are essential and which are not. Only intervene if they ask you to do it.
Respect their time
Like you, engineers need long periods of uninterrupted work to be effective. Don’t interrupt them if it’s not strictly necessary.
If you work in an Agile environment, you probably have a daily meeting to meet and catch up. It will be strange that something is so urgent that it can’t wait until the next day.
In the same way, don’t create meetings from one hour to another unless it is to attack a fire. It is a strong smell of improvisation and not knowing what you are doing very well.
Take the time to think about whether it makes sense to bother the team. Many times these types of meetings come because someone above your rank has had a happy idea, and you want to be proactive in responding to it.
Your job is not to make managers happy. It is to make the team’s work impact the business.
Don’t hide anything from them
Sometimes plans go awry and don’t go as we would like. When that happens, we can urge to try to sweeten the situation and protect the team, trying to keep motivation high.
But people are not idiots and are perfectly capable of intuiting when something isn’t going well. If your team perceives it, but you act as if nothing is wrong, you will lose their confidence.
Remember, your engineers don’t work for you; they work with you. Listen carefully to their opinions and consider their point of view.
You start with the advantage that you have been able to dedicate much more time to the problem than they have, but that does not give you the power to dismiss their ideas automatically. Furthermore, your team has a lot more context of how your product works internally and what is possible and what is not.
Listen, process the information, and argue why an idea may or may not work. Time spent listening to the team and answering their questions is well spent.
Learning to communicate effectively with your engineering team is undoubtedly one of the skills that you will get the most out of in your career as a Product Manager.
In today’s article, we have seen up to 11 different tips that you can apply to grease this communication:
- Understand your position
- Understand your situation
- Start with the problem
- Do your homework
- Explain the why
- Define success
- Get them involved early
- Don’t isolate them from the outside world
- Respect their time
- Don’t hide anything from them
- Be humble
And not just with software engineers. We can apply any tips we discussed here to engage with other organization members.
From here on, it is up to you. Apply them and be successful, or ignore them and suffer the consequences.