post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

AI governance

Perplexity lawsuit sends warning to product managers

Guest Post

The Irony of Product-led Growth: How Adding More Can Slow You Down

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

Product Leader

Ben Newell

When product and engineering teams adopt an agile way of working, it&#8217;s all-to easy for them to leave other departments in the organization behind. But, there are techniques you can use which help to make your agile transformation more acceptable for everyone else in the business.
Agile transformation, undoubtedly two words that strike fear into the heart of any product organization.  It should be an exciting time, with tough conversations, compromises, and hopefully good progress. But even if you successfully form a single team, there’s another problem… the rest of the organization has no idea how to deal with you.
Did you know your agile transformation would require a transformation of the entire organization?
<img loading="lazy" decoding="async" class="aligncenter wp-image-17415 size-large" src="https://www.mindtheproduct.com/wp-content/uploads/2019/10/Idea-1024x711.jpg" alt="" width="1024" height="711" srcset="https://www.mindtheproduct.com/wp-content/uploads/2019/10/Idea-1024x711.jpg 1024w, https://www.mindtheproduct.com/wp-content/uploads/2019/10/Idea-300x208.jpg 300w, https://www.mindtheproduct.com/wp-content/uploads/2019/10/Idea-768x534.jpg 768w, https://www.mindtheproduct.com/wp-content/uploads/2019/10/Idea.jpg 1920w" sizes="(max-width: 1024px) 100vw, 1024px" />
Sales, account management, and marketing will often look for that big idea to wow customers:  “I’ve got something new, and it&#8217;s going to knock your socks off!”  Your finance team wants tight clarity on what they’re paying for (typically a feature) and a clear understanding of its return on investment.  And your HR team wants clear goals that an employee can independently control to help measure their performance.  Working incrementally toward outcomes that the TEAM is responsible for just won’t work in these traditional models.
As a product leader, you may not always have control over affecting change across the entire organization.  However, there are steps you can take to help other teams more clearly understand what’s happening and how it’s good for the company.  Below are four techniques you can start to use immediately that help to make your transformation more palatable for everyone else.
<h3>1. Involve the Organization</h3>
Hopefully most of us realize that we’re not all-knowing.  Yet, when we talk about creating tests in our products, we too often reserve brainstorming new ideas for the product and design team. The more you can engage different perspectives from the rest of the organization, the better the chance you’ll find the right one. However, you need aggressively to solicit suggestions. I recommend an open<a href="https://www.mindtheproduct.com/design-thinking-idea-product/"> design thinking</a> session where you bring in a couple representatives from each team (sales, account management, marketing) and walk through the data together.  For maximum effectiveness, ask the leaders of those teams to assign people.
BONUS: With these sessions, you’re teaching the participants the processes of design thinking.  This will allow them to take it back to their own teams.
<h3>2. Get Everyone Comfortable With Themes</h3>
Themes can be marketed, sold to customers, and generate excitement.  Strategic themes of investment are more powerful than a list of features.  Granted, customers often want to see their specific ask on your roadmap, but that becomes even more powerful if you can transform their requests to fit your themes &#8211;  it demonstrates that you’re aligned!  Develop long-term roadmaps in themes and report to executives with your investment levels relative to those same themes.
BONUS: Themes can be very useful for product managers when a request can’t be worked into a strategic theme.  It&#8217;s much easier to explain your “No” if something doesn’t align with your strategy.
<h3>3. Keep Everyone in the Know</h3>
It’s hard to the rest of the organization to keep up when you make small incremental changes and constantly evolve based on data. They may start to feel like you’re doing your own thing.  I use product update meetings &#8220;creatively&#8221; to address this. The meeting content is created for everyone outside the product and engineering teams. The goal is to share:
<ol>
<li>What we’ve done and did it work.</li>
<li>What we’re working on now and what you should expect to see shortly.</li>
<li>Where we’re going and why.</li>
</ol>
<img loading="lazy" decoding="async" class="aligncenter wp-image-17417 size-large" src="https://www.mindtheproduct.com/wp-content/uploads/2019/10/startup-594091_1920-1024x683.jpg" alt="" width="1024" height="683" srcset="https://www.mindtheproduct.com/wp-content/uploads/2019/10/startup-594091_1920-1024x683.jpg 1024w, https://www.mindtheproduct.com/wp-content/uploads/2019/10/startup-594091_1920-300x200.jpg 300w, https://www.mindtheproduct.com/wp-content/uploads/2019/10/startup-594091_1920-768x512.jpg 768w, https://www.mindtheproduct.com/wp-content/uploads/2019/10/startup-594091_1920.jpg 1920w" sizes="(max-width: 1024px) 100vw, 1024px" />
Putting together this much content can be a drain on the product team, so I recommend these are held no more often than every six weeks.  I also recommend holding them in person or broadcasting to the rest of the organization.  This gives you a chance to elaborate on intimately familiar topics that may otherwise take a long time to explain in writing.
BONUS: This meeting gives your team a chance to practise their presentation skills &#8211; and everyone can benefit from that.
<h3>4. Maintain a Scoreboard</h3>
I often ask teams what a basketball game would look like if nobody kept score: very little urgency, individual self-identified goals might take precedence, and generally it would be a pretty terrible game.  Yet, at work we do this all the time.  We show the scoreboard at the end of the game, or only monthly do we report progress.  To be really effective at keeping teams focused on the goals, you need to create some “scoreboarding”.  Maybe it’s a report that gets sent every day, or a TV with that dashboard.  What about <a href="https://www.smiirl.com/">something like Smiirl&#8217;s physical dashboard</a>?  Whatever form it takes, it must be present and discussed.  With a clear scoreboard, the rest of the organization understands exactly when you’re succeeding and when you’re not.  It can make you feel a little vulnerable to put your success metrics on the wall, but that vulnerability goes a long way towards creating trust.
BONUS: When the scoreboard metrics are not moving, the rest of the organization gets particularly creative about how to turn that around.  Now, you’re really getting everyone involved!
If you’ve read anything on agile transformation, you already know the mantra: This is Hard. Don’t forget it.  Focusing on how the product and engineering team’s changes affect the rest of the organization can seem a bit overwhelming.  However, if you bring everyone along with these techniques you have a greater potential to turn from a good team to a great team.  And, isn’t that why we have these jobs?

core/freeform

Agile Product Development

Better value sooner, safer, and happier by Jonathan Smart

Building Successful Product Development Teams, by Simon Colmer

How to be a Successful Product Owner, by Ninon Laforce

Out of the Fog by Holly Donohue

How Design Thinking, Lean, and Agile Work Together by Jonny Schneider

Lean, Agile, & Design Thinking by Jeff Gothelf

Tales of two Continuous Loops by Tim Beattie

Agile With a Capital A Might not be Best by Morag McLaren

How to Apply Lateral Leadership in Agile Environments by Tim Herbig

Owning Agile by Jeff Patton

How to Involve the Entire Organization in Your Agile Transformation

ProductTank Sofia

ProductTank Belfast

ProductTank Köln

ProductTank México City

ProductTank Wellington

ProductTank Manchester

ProductTank Lisbon

ProductTank São Paulo

ProductTank Madrid

ProductTank Montevideo

ProductTank Montréal

ProductTank Boston

ProductTank Ahmedabad

ProductTank Bangalore

ProductTank Berlin

ProductTank Oslo

ProductTank Des Moines

ProductTank Bangkok

ProductTank Abu Dhabi

ProductTank Helsinki

ProductTank Pune

ProductTank Kraków

ProductTank Cardiff

ProductTank Mumbai

ProductTank Johannesburg

ProductTank Tauranga

ProductTank Bielefeld

ProductTank Vilnius

ProductTank Stockholm

ProductTank München

ProductTank Düsseldorf

ProductTank Birmingham

ProductTank Norwich

ProductTank Heidelberg

ProductTank Barcelona

ProductTank Newcastle Upon Tyne

ProductTank London

ProductTank Tokyo

ProductTank Braunschweig

ProductTank Edinburgh

ProductTank Pittsburgh

ProductTank Vienna

ProductTank Bristol

ProductTank Raleigh

ProductTank Brno

ProductTank Orlando

ProductTank Hong Kong

ProductTank Charlotte

ProductTank Exeter

How to Involve the Entire Organization in Your Agile Transformation

Ben Newell

Read more

Comments