Debunking the Myth: Software Developers are NOT Product Order Takers

As a Product Manager, one of the most important partnerships you’ll have is with your team of developers and engineers. However, there’s a common myth that software developers are merely order takers - that they are there to execute on the Product Manager’s orders. In reality, developers are critical problem solvers who want to be involved in the ideation process so that they can help you figure out what’s viable, feasible, and scalable.

Here are 4 tips on how to successfully partner with developers and engineers to achieve the best possible product outcomes:

1️⃣ Learn their Communication Preferences

Understanding your developer’s communication preferences is key to having a successful partnership. For instance, some developers prefer to work heads down after standup through lunch time, while others may prefer Slack over email. By respecting their communication preferences, you’re giving them the space and environment they need to be successful. We highly recommend teams have a Ways of Working ceremony to openly define these preferences together! It sets the tone for a psychologically safe environment for the team. 

2️⃣ Give Them the Big Picture

Developers want to build solid and flexible products, and they can’t do that if they only have a slice of insight into your roadmap. When you share the big picture, you’re empowering your team to think creatively and critically about the product you’re building. This also gives them an opportunity to identify potential technical constraints and roadblocks early on, which can save you time and resources down the line. It's important they know the what and the why so they can solution for the best how! 

3️⃣ Include Them in Discovery

We were so fortunate to spend time with Marty Cagan, a prominent figure in the world of product management, in a Product Coach training session last year in NYC! He shared a wonderful reminder that he often says: “If you’re only using your devs to code, then you’re only getting half of their value.” Including developers in the discovery process can help identify technical constraints and opportunities that may not be immediately apparent to the product team. By working together during the discovery phase, you can ensure that the product you’re building is both technically feasible and valuable to your customers.

4️⃣ Give Them the Opportunity to Think Through Approaches

In Sprint Planning, it can be tempting to throw developers a user story and expect them to be off to the races. However, this approach can lead to misunderstandings and missed opportunities. Instead, give your developers the opportunity to think through how they will approach the ticket by sharing it with them early and often. We teach teams to structure their grooming and pre-planning ceremonies in such a way that the team has already seen a user story twice before getting to Sprint Planning. By doing so, you’re allowing them to bring their technical expertise to the table, identify potential roadblocks, and develop a plan that ensures the best possible outcome.

Conclusion

In conclusion, software developers are critical problem solvers who want to be involved in the ideation process so that they can help you figure out what’s viable, feasible, and scalable. By understanding their communication preferences, sharing the big picture, including them in discovery, and giving them the opportunity to think through approaches, you can build a successful partnership that leads to the best possible outcomes. Remember: developers aren’t just order takers. They’re critical partners in the product development process, and by working together, you can build the best possible product for your customers.

Did you also believe this myth? It is one we are SO passionate about breaking.

We would love for you to share it with your community to help spread the positive team narrative & tag us in your share so we can see what other tips we should add to this post!

We are @productxagile on LinkedIn, Instagram, Facebook & TikTok.