post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

Creating metrics that matter

A case study: Launching a product process in a project-based company

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

How much are product managers getting paid in 2024?

Leading product ops at Delivery Hero with Koen Dubelaar

Connecting fans to creators at Spotify (Dariusz Dziuk, Product Lead, Spotify)

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

Everything wrong with the product management job market. And how to fix it

Rosemary is an experienced product manager who has specialized in software development, agile enablement and lean methodologies for the past seven years. She has worked across diverse domains including government, finance, retail and enterprise. After starting her tech career in the New York City start-up scene, she moved into consulting and has spent time with ThoughtWorks and Pivotal Labs London. She has done freelance consulting and training with incubator programs like start-up bootcamp, done UX research on four continents and likes cold water surfing.

Rosemary King

<p>For the past year, as Director of Training Products for Mind the Product, I’ve been creating a training platform and service. During this time I’ve worked with dozens of companies and hundreds of product managers; hearing about their challenges, and working with them to set game plans for shifting practices.</p>
<p>The one theme that has come out of working with these clients is that other departments in a company could work better with the product team/s. In my musings on how to address this issue, two tactics have emerged; <em>the creation of understanding, </em>and <em>building a roadmap towards complementary practices</em><span style="font-style: italic;">.  </span></p>
<p>So, how can departments who are not building software “mirror” the approach of product teams? By viewing their outputs as products, and taking the same approach to evaluation, communication and optimisation as best-practice product teams.  Until my current job, my products were all software projects, so it was an eye-opener for me that, even though I’ve shifted to building a service model, nothing about the process I run has materially changed.</p>
<p>I’ve managed to shuffle the myriad of Mind the Product activities into four buckets in order to break down the process into pieces that other departments can mirror:</p>
<h2>Align Around Goals</h2>
<p>Product teams understand that in order to explore a complex and changeable domain, clear goals are a rock-solid requirement. This includes top-level goals that define a clear vision, but also more detailed goals that help teams to understand how they should measure their day-to-day outcomes.</p>
<h2>Test Everything</h2>
<p>I believe that once “testing goggles” have been acquired, they cannot be let go. Once a team understands that, each action they take is then a hypothesis, and outcomes either validate or invalidate what was understood about the product. At MTP this means that we structure all our activities as hypotheses, for example, “We bet that sending materials ahead of time will impact participant engagement,” and then we measure the results.</p>
<h2>Take Stock Regularly</h2>
<p>If a team is always testing and therefore always learning, then the distillation of what has been learned must be fed back into the product at regular intervals. For every major activity or milestone that MTP Training experiences, we have a retro with the team involved, evaluating what went well or what didn’t go well.</p>
<h2>Bake in Continuous Improvement</h2>
<p>Just reviewing the good and bad is not enough. Teams must also create and address activities that might cause improvements. Retros should culminate in a list of action items that are meant to alleviate past friction. An organisational culture of openness and transparency is needed in order to enable continuous improvement, but you can get started by scheduling retros consistently, and following through on the action items they surface.</p>
<p>I’ve seen bakeries and law firms espouse these concepts.  In general, if an organisation can drive for general adoption of these processes, then not only will departments work more effectively with product teams, but they’ll generally work better.</p>
<p>For a few other articles on product-driven culture best practices, check out these blogs and talks from the MTP archive.</p>
<ul>
<li><a href="https://www.mindtheproduct.com/challenges-approaches-building-products-complex-ecosystem/">Challenges and Approaches to Building Products In a Complex Ecosystem</a></li>
<li><a href="https://www.mindtheproduct.com/transforming-product-culture-lea-hickman/">Transforming to a Product Culture by Lea Hickman</a></li>
<li><a href="https://www.mindtheproduct.com/product-management-culture-management/">Product Management is Culture Management</a></li>
</ul>

core/freeform

Product Management Skills

How to keep your head about generative AI (when everyone is losing theirs) by Claire Woodcock

Mirroring Product: a Breakdown of Process

Rosemary King

Read more

Comments