What is an empowered product team?

How do you know if you’re about to join a feature team or an empowered product team 🕵️‍♂️? Because, from the outside, they can look indistinguishable.

If you’re already working on a team, you probably have your suspicions and, in this clip, Marty Cagan shines such a big bright light on both types that you’ll have no doubt by the end 🔦.

#ProductManagement #ProdMgmt #ProductLeadership #BraveUX

======

Watch the full interview:

Subscribe to the channel:

======

Who is Marty Cagan?

Marty is one of the - if not the - most influential people in product management. He is the author of two incredibly successful books - Inspired and Empowered - both of which are essential reading for people in product. Before founding the Silicon Valley Product Group in 2002, Marty held senior leadership roles at HP, Netscape and eBay, where he worked closely with some of the most well-known names in technology, including Ben Horowitz and Mark Andreessen.

Find Marty here:

======

Liked what you saw and want to see more?

Subscribe to the channel:

You can also subscribe and listen to the Brave UX podcast on:

Follow us on our other social channels for more great UX research and product management tips, interviews and insights!

📝 Blog: coming soon!

======

Hosted by Brendan Jarvis:

[NicholasBurgher]

This was probably his best summary on the topic of Empowered Product Teams. Absolutely love this.

[marna_li]

The team is invested in the product that they are working on. It is not just about doing a job from specification and sufficiently good. They continuously improve that product.

[vivi_cocacola]

This is amazing! So glad I’ve run into this vid 😊

What an amazing mentor and an inspiring author!

Great summary of Empowered Teams

[jboive]

Is this what developer wants? I'm in the middle of moving from the "old school" feature approach to "empowered" teams - and I'm far from convinced about the benefits.
Sounds more like a workaround to the actual problem: Collaboration between the business and the IT department.

So the solution should be that the development team needs to be experts on the business side of things as well AND data driven?
Because, remember - by empowered you need all the skills within the team.

The examples and the comments here seems to relate more with a relation to a programmer than a systems engineer.
If you give a solution to an engineer he or she will naturally want to take care and refine it, Hence improving the product.

It's hard enough today to keep track of the technical side of things - if developers needs to do BI as well? Well, something is going to suffer -> less coding and less happy devs.
Yes, I know - more code doesn't equal more productivity. Especially if the code you're writing isn't for the features the customer wants.
But that's my point - the business should be the experts on what the customers wants. Developers are experts on how to solve problems most efficiently given the current conditions.

So I hear the argument: We've implemented this and all our developer are really excited!
Are they? Are they really? How many consultants does your team consist off? That's my first question...