Thoughts on product management: are developers part of the product team or not?

Mõtteid tootejuhtimisest: Kas arendajad on osa tootetiimist või mitte?

Although developers and product managers seem to work towards a common goal, I often notice that psychologically they belong to different teams. They have separate managers and tasks, communication channels, success metrics, worries and joys. In reality they work in silos. A structure like that often makes the relationship transactional - one side demands, the other complies. And in the end, someone is always to blame.

I’ve always found it really hard in teams like that. At first I thought the problem was me, that I should take my work less emotionally. But over time I’ve come full circle back to the understanding that the most effective teams tend to be the ones where everyone is empathetic towards each other and the customer, and genuinely invested. In those teams, developers solve the problems identified in user research together with me, and help think through how our product could be commercially successful and offer a great user experience. In those teams there’s no “you” and “us”, because everyone feels equally responsible for the product’s success.

So when someone recently asked me whether developers really need to be in the product channel on Slack, my answer was a firm “Yes, of course - they’re part of the product team!” No, what happens there isn’t excess noise, it’s context.

But how do you achieve that kind of synergy, where developers are part of the product team? My favourite approach is simple - keep everyone in one shared information space, encourage thinking along and discussion, and tie everything to customer-centric business goals. Working in one shared space, developers continuously get information about the customer, the market, stakeholders and business opportunities, and the product manager takes part in technical conversations, bringing in the customer’s perspective. That way everyone always has the full context, far less important information gets lost, and the decisions made are of better quality.

So - no to functional silos, ever, and yes to teams that work as one unit, building on each other’s strengths and weaknesses towards one goal (in one Slack channel).

Want to know more?

Follow me on LinkedIn or get in touch!