post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

Building for change: When transformation and product management meet

Product Development

What are product features? Definition, examples, and 5 types

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! 🎉

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

Lessons from my first year as a Prod Ops Manager

How Google makes AI work at Enterprise scale – Miku Jha (Director, AI/ML and Generative AI, Google Cloud)

5 ways to invent and simplify as an AI/ML product manager

Andres Phillips

<p>In this #mtpcon Digital Americas session, <a href="https://mobile.twitter.com/audcrane?lang=en" target="_blank" rel="noopener">Audrey Crane</a>, Partner at DesignMap shows how Product Managers can leverage design teams and methodologies to move from feature teams to empowered product teams.</p>
<p>Watch the video session in full or read on for the highlights:</p>
<h2>Level set on terms</h2>
<p>Audrey begins by clarifying the differences and similarities between feature teams and product teams.</p>
<h3>Purpose</h3>
<p>A feature team&#8217;s purpose is &#8220;to serve the business by delivering features as required by stakeholders or executives”. An empowered product team&#8217;s purpose is &#8220;to solve problems in ways our customers love, yet work for our business”.</p>
<h3>Customer knowledge</h3>
<p>A feature team&#8217;s customer knowledge is the expectation (or at least hope) that if the business says they need you to build feature x, they believe feature x is valuable and viable. In an empowered product team, deep knowledge of the customer is absolutely essential and non-negotiable.</p>
<h3>Responsibilities</h3>
<p>A feature team is responsible for the output of prioritized features by certain dates. An empowered product team is responsible for solving problems and producing desirable outcomes.</p>
<p>Audrey presents a model situation. If a problem has more than one potential solution and more than one potential implementation and empowered product teams are given a problem to solve, something happens. &#8220;Hopefully, they get the chance to come up with the right solution and the right implementation. Whereas feature teams are given solutions, presumably to problems and have a chance to implement them,&#8221; she explains.</p>
<p>Yet, these teams often have similar makeups, and include a product manager, designer, and engineers. Audrey provides three ways for feature teams to become empowered product teams by taking a bottom-up, top-down, or outside-in approach.</p>
<h2>Create value where you are</h2>
<p>Many feature teams are given a list of prioritized features and asked to execute them. Audrey provides a few parallel examples  &#8211; an actor told just to read the lines, a teacher being restricted to just a lesson plan or a waiter asked to take an order. However, as a product manager, you might feel like you&#8217;re capable of more.</p>
<p>How can you turn a moment of service into a moment of collaboration? &#8220;Now is the time that we get to apply design thinking,&#8221; Audrey explains.</p>
<h3>Empathize by asking</h3>
<ul>
<li>What is the root of the business request?</li>
<li>What do they think this process should look like?</li>
<li>How did they learn that?</li>
<li>What is their personal success hinged on?</li>
<li>What do they do outside of work?</li>
</ul>
<h3>Define</h3>
<p>What is the actual problem? For example, is it</p>
<ul>
<li>Past successes or failures?</li>
<li>When contracts get signed?</li>
<li>Lack of awareness?</li>
</ul>
<h3>Ideate by asking</h3>
<ul>
<li>How might we address our problem statement?</li>
<li>What would I do if I were a consultant?</li>
<li>What&#8217;s the smallest thing I could do?</li>
<li>What if I wanted to make them a hero?</li>
</ul>
<h3>Prototype</h3>
<ul>
<li>Story maps</li>
<li>Design sprint</li>
<li>Sales support</li>
<li>Playbacks</li>
</ul>
<p>While using design thinking is effective, it&#8217;s important to remember that this is a long game and use the moments to build trust with other stakeholders.</p>
<h2>Create value at the top</h2>
<p>To create value at the top of the organization, Audrey suggests using design as a Trojan horse for the whole product team. Many executives already believe that design drives revenue and ROI, but they don&#8217;t know how to support and leverage design properly.</p>
<p>Product managers, however, are uniquely positioned to help design leaders speak to upper management and help tell the business story. They can help to explain how the business can derive business and strategic value from design and what they need to accomplish this.</p>
<p>Ultimately, what design wants the same thing as product managers:</p>
<ul>
<li>Talk to customers first, not last</li>
<li>Understand customer&#8217;s real problems</li>
<li>Have the creative flexibility to come up with great solutions</li>
<li>Know that their work is having a real impact for real people</li>
<li>Not work on tickets, orders, or feature lists</li>
</ul>
<h2></h2>
<h2>Usability testing is never (just) usability testing</h2>
<p>Audrey explains that in some situations, feature teams don&#8217;t have the opportunity to talk to customers. The problem this creates is that customer insights get pinged around. However, by definition, it is impossible to be a product team without regular customer contact.</p>
<p>Feature teams end up only being responsible for implementation and studying usability studies. However, they need to go beyond usability testing and create a conversation about value. &#8220;It&#8217;s impossible to be passionate and be a missionary about solving a problem that you don&#8217;t know exists or even understand.&#8221;</p>
<p>Audrey suggests that product managers bring other business stakeholders into interviews to help solve this problem. The key takeaways from this talk are that any company and processes are likely to be a big ship to turn, and nothing will happen overnight. However, by applying pressure in small ways across different areas, you can start to see a change in a quarter or two. In the end, the goal is to have a better impact on the business.</p>
<h2>There&#8217;s more where that came from!</h2>
<p>Use our <span style="text-decoration: underline;"><a href="https://www.mindtheproduct.com/content-a-z/" target="_blank" rel="noopener">Content A-Z</a></span> to find even more product management insights.</p>

core/freeform

Product Management Conference

Product teams in flux – Pendomonium+#mtpcon roadshow: Berlin

AI in practice at Berlin’s leading companies – Pendomonium+#mtpcon roadshow: Berlin

AI in practice at Amsterdam’s leading companies – Pendomonium+#mtpcon roadshow: Amsterdam

Product teams in flux – Pendomonium+#mtpcon roadshow: London

AI in practice at London’s leading companies – Pendomonium+#mtpcon roadshow: London

What’s next for product management in 2024? Nichole Mace (SVP Product and User Experience, Pendo)

“You’re not as competent as you think” 5 lessons from Ken Chin on navigating a product career (CPO, Spark Networks)

Perspectives from an unconventional CPO – Yuelin Li (CPO, Onfido)

The future of product management – Trisha Price (CPO, Pendo)

The future of product management in 2024 and beyond (Brian Walsh, SVP Product, Pendo)

Moving from feature teams to product teams by Audrey Crane

Andres Phillips