post

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Are you really understanding your users or going through the motions?

Why can’t we get accessibility right? Claire Bauden (SVP Global Product Design, Global Payments Inc.)

Ditch the PRD template and embrace the PRD checklist

How to price your subscription product: insights and examples

Can product operations and innovation be friends?

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

Building confidence in product investment decisions

Sunday Rewind: The good, bad, and ugly of OKRs by Jenny Herald

Ahana is an R&amp;D software engineer at Dassault Systemes Americas Corp with over a decade of experience in software development and analytics. She started her career at IBM, transitioned through diverse roles, and is currently developing project planning software at Dassault. She holds an M.S. in Business Analytics and Information Management from Purdue University and actively follows analytics trends. Additionally, she is a Senior Member of the Society of Women Engineers.

Ahana Roy Choudhury

<p>Let me start with a story. In a busy tech office, Alex, a product manager, excitedly told Jamie, the developer, about the new &#8220;Celebration with confetti&#8221; idea. Alex explained, &#8220;When users achieve success, their screens will show falling confetti!&#8221; Jamie, always ready for new challenges, agreed immediately to try to build it. But when Jamie finished and demo-ed it, there was too much confetti, and the system slowed down. Then Alex said, &#8220;Maybe we should&#8217;ve used less confetti!&#8221; Though Jamie smiled and kept up the good humor, this bothered him immensely. Both of them realized that working together is important for successful outcomes.</p>
<h3><strong>Framework to collaborate better</strong></h3>
<p>While the story is fictional, it reflects the often-occurring real-world dynamics between developers and product managers. Collaboration between developers and product managers is essential for <a href="https://www.mindtheproduct.com/7-steps-of-new-product-development-process/">product development</a>, yet communication gaps are frequent. Fostering a collaborative relationship relies on embracing four principles for developers, and for product managers. Let me elaborate with a P2C2 framework.</p>
<h3><strong>Proximity</strong></h3>
<p>Developers value when their product manager has a keen understanding of technical boundaries and constraints they work within. Technology projects, regardless how innovative, operate within a framework defined by the technology in use, infrastructure, and third-party tools or plugins integrated into the system. Often, it is not about what is possible hypothetically; but it is also about what is feasible and can be done with reasonable trade-offs. When a product manager proposes an addition of new features or enhancements, it becomes crucial for them to be aware of these technical limitations. This awareness enables product managers to set goals that are ambitious, yet achievable, leading to more successful outcomes.</p>
<p>For instance, imagine a scenario where a product manager is excited about introducing a real-time chat feature on a website. While the idea is promising, the developer might be aware that the current backend infrastructure isn&#8217;t designed to support such instantaneous interactions. In such cases, the collaboration between the developer and the product manager becomes pivotal. They might explore alternative solutions, such as integrating a third-party chat tool or strategizing a backend overhaul to accommodate the desired feature in the future. This collaboration and open dialogue between product managers and developers are not merely about problem-solving; they are about fostering a culture of understanding and mutual respect. It is about acknowledging that while developers bring technical expertise to the table, product managers offer valuable insights into user needs and market trends. Bridging these perspectives can lead to more innovative solutions and a product that truly resonates with users.</p>
<h3><strong>Prioritization</strong></h3>
<p><img loading="lazy" decoding="async" class="wp-image-40071 alignleft" src="//wp-content/uploads/2024/01/shutterstock_2223377673-300x160.jpg" alt="a stack of numbers cubes to represent prioritization" width="536" height="286" srcset="/wp-content/uploads/2024/01/shutterstock_2223377673-300x160.jpg 300w, /wp-content/uploads/2024/01/shutterstock_2223377673-1024x547.jpg 1024w, /wp-content/uploads/2024/01/shutterstock_2223377673-768x410.jpg 768w, /wp-content/uploads/2024/01/shutterstock_2223377673-1536x820.jpg 1536w, /wp-content/uploads/2024/01/shutterstock_2223377673-2048x1094.jpg 2048w" sizes="(max-width: 536px) 100vw, 536px" /></p>
<p>In any project, some tasks are super important, and some can wait. Developers appreciate when product managers prioritize tasks with a clear list, acting as a roadmap for the project. However, unexpected ideas, like adding a chat feature, can arise. While this idea might sound cool and helpful, it wasn&#8217;t part of the original plan. Adding new things can make the project longer and more complicated. So, the product manager and the developers need to discuss and have an alignment rather than the product manager dictating tasks. They should discuss if this new idea is a good fit for the project. If they decide it is, they will have to rethink their plan and the timeline. If all are in agreement, they may need to adjust the plan or timeline, ensuring the project&#8217;s success and staying on track.</p>
<h3><strong>Clarity</strong></h3>
<p>Imagine, an online store wants to let shoppers change products before buying. At first, the product manager might tell the developer, &#8220;Let customers customize products and try them before making a purchase.&#8221; That is pretty vague. The developer might just let shoppers pick colours. But if the product manager shows pictures of what they want, like choosing colours, adding logos, or seeing a 3D preview, then the developer knows exactly what to do. It is also helpful when they say things like, &#8220;Customers should see a live preview of their design.&#8221; Building something new always has questions. The developer might ask things like, &#8220;Can customers make the logo bigger?&#8221; This is when the product manager and developer need to have frequent discussions and converge decision making having clear mechanisms for tie-breakers. By discussing regularly and getting feedback, they work together to make the tool right for shoppers and fit the company&#8217;s goals.</p>
<h3><strong>Celebrate each other</strong></h3>
<p><img loading="lazy" decoding="async" class="wp-image-40074 alignleft" src="//wp-content/uploads/2024/01/shutterstock_1367234948-300x169.jpg" alt="Two people high fiving each other" width="523" height="295" srcset="/wp-content/uploads/2024/01/shutterstock_1367234948-300x169.jpg 300w, /wp-content/uploads/2024/01/shutterstock_1367234948-1024x576.jpg 1024w, /wp-content/uploads/2024/01/shutterstock_1367234948-768x432.jpg 768w, /wp-content/uploads/2024/01/shutterstock_1367234948-1536x864.jpg 1536w, /wp-content/uploads/2024/01/shutterstock_1367234948-285x160.jpg 285w, /wp-content/uploads/2024/01/shutterstock_1367234948-570x320.jpg 570w" sizes="(max-width: 523px) 100vw, 523px" /><br />
Developers often work in the backend and product manager becomes the face of a product. They handle the technical parts, making sure everything runs smoothly. On the other hand, the product manager, is like the spokesperson for the product. They talk about it, present it, and show it off to the world. Sometimes, this setup works great, and both the developers and product managers shine when the product does well. But if something goes wrong with the product, it can put pressure on both sides. There&#8217;s a saying that when you share good times, they feel even better, and when you share tough times, they feel a bit easier to handle. This idea holds true for developers and product managers working together. Sure, they have their tasks and plans to follow. But what really makes them work well as a team is something deeper: respect for each other&#8217;s roles and hard work. Developers put a lot of effort into making things work, and they appreciate when someone notices their hard work. On the other side, product managers value the technical expertise developers bring to their ideas. When they both understand and respect each other&#8217;s roles, they create a positive atmosphere. In such a setting, new ideas pop up easily, teamwork flows naturally, and together they can create outstanding products that people love.</p>
<h3>How to actually collaborate better</h3>
<p>We often say about how product managers and developers should work closely. But saying isn&#8217;t enough; they need to work together actively to succeed. Creating a great product involves thorough planning, frequent communication, and a clear understanding of each other&#8217;s ideas. The process of refining new product or feature ideas often requires discussions, prototype testing, and constructive feedback, even for experienced professionals.</p>
<p><span style="font-style: italic;">Distilling product managers collaborations across sales, marketing, and other stakeholders</span> – developers often look to understand how the different functions in the organization work to bring a product to the market. In doing this the developer, looks to understand the overall product lifecycle and product managers are the best conduit between the developers and the rest of the <a href="https://www.mindtheproduct.com/product-lifecycle-management-beyond-early-adopter/">product lifecycle</a> flow. Be it the UX team, marketing, sales, and even executive leadership. The best way to stream in the knowledge acquired from these groups is to create an ongoing touchpoint with the developer groups. This can be distilled in the form of a monthly business report, voice of the organization deck, or a meeting to disseminate this information. This squarely should be for developer consumption. This will bring a lot of synergy into the relationship between developer and product manager.</p>
<p>Here are four mantras to work well together:</p>
<p><span style="font-weight: bold;">Write it down:</span> Product managers should write down their ideas clearly. They should mention what is needed for the first version of the product, known as the <a href="https://www.mindtheproduct.com/the-complete-guide-to-building-mvps/">MVP</a>. This helps developers know what to focus on.</p>
<p><span style="font-weight: bold;">Try it out:</span> Developers like to try things hands-on. They should make a prototype &#8211; simple version or model of the product, so everyone can see and understand the idea better.</p>
<p><span style="font-weight: bold;">Keep talking:</span> They should have regular meetings to share thoughts, feedback, and any issues they face. This helps everyone stay on the same page and solve problems together.</p>
<p><span style="font-weight: bold;">Use Agile:</span> They can use the Agile methodology. In this approach, product managers keep updating their plan, and developers keep improving the product based on feedback. It&#8217;s flexible and helps them adjust to changes quickly. They can decide how often to meet and what to work on first based on the project&#8217;s needs.</p>
<p>In product development, two key players are product managers and the developers. They are like teammates on a soccer field; they each have their roles, but they need to work together to score a goal (which often literally product managers and devs are working to achieve in a corporate setting as well – accomplishing goals). Developers are like the players who know all the moves and techniques. But just like a soccer player needs a coach&#8217;s plan, developers need guidance from product managers. That is where product managers come in. They provide a clear vision for the product, offering instructions and goals to guide developers. By giving clear instructions and goals, product managers help developers know what to do. However, product development is an ongoing journey. Along the way, there might be some shortcuts or quick fixes. Developers, being the experts, notice these things. When they share this with product managers, they can work together to decide the best way forward.</p>
<p>In the end, the success of a product depends on how well product managers and developers work together. When they communicate, share ideas, and respect each other&#8217;s roles, they can create something amazing that people will love. Like a winning soccer team, their teamwork and understanding make all the difference.</p>
<p>Explore more product management content on Mind the Product by visiting our <a href="https://www.mindtheproduct.com/content-a-z/">Content A-Z</a>.</p>
<div class="g g-21"><div class="g-single a-170"><a class="gofollow" data-track="MTcwLDIxLDEsNjA=" href="https://www.pendo.io/pendomonium/"><img decoding="async" src="https://www.mindtheproduct.com/wp-content/uploads/2024/06/MTP-Footer_ad.png" /></a></div></div>

What developers wish product managers know

Ahana Roy Choudhury

Comments

Read next