Відео

Time codes: 0:00 Introduction. Sponsors and thanks 4:19 How ProductTank Brisbane started 7 years ago 6:30 Introduction and role of of Marty Cagan 8:55 Reasons and goals behind "Transformed" book 12:50 About Product Operating Model 17:58 About Mike Fisher 18:58 What it really means to transform? 21:25 Three dimensions: changing how you decide which problems to solve (applying continuous product strategy) 26:30 Three dimensions: changing how you solve problems (applying continuous product discovery) 36:04 A story of how Marty transitioned from Engineering into Product Management 47:00 Three dimensions: changing how you build solutions (applying continuous product delivery) 50:15 Concepts, competences and principles 50:22 Competences (Product Manager, Product Designer, Tech Lead, Product Leaders) 51:25 Example of a Tech Lead competency 53:25 Concepts (Product Teams, Product Strategy, Product Discovery, Product Delivery, Product Culture) 53:53 Example of a Product Culture (at Spotify) concept 56:09 Principles (20 First Product Principles) 57:40 Example of Innovation over Predictability principle 1:00:17 Importance of shared strategic context 1:03:05 Examples of companies transformed to Product Model 1:07:48 Winning minds and hearts 1:11:45 Dealing with company politics 1:20:43 SVPG books 1:22:10 Contacts 1:23:05 Question: with GenAI we'll not need PMs anymore? 1:27:05 Question: does this apply to purely physical products? 1:31:15 Question: what story are we telling ourselves that is holding back the product discipline? 1:34:55 Question: what IC promoted to Product Leader without coaching can do? 1:37:52 Question: how do you deal with tech debt? 1:42:40 Question: what to do if ethical risk in a product? 1:48:04 Termination

Laughed loudly at 51:55 "Look at how most companies work: executives are making the roadmap and engineers not even in the room! Sometimes they not even in the country!" Love that ending!

For Marty 1:21:45

Great content!... Thank you for honesty

(1:21 product tank) (3:23 her background) 4:20 discovery vs delivery ~deciding what to build 5:55 continuous discovery 101 weekly touch points 6:10 -curse of knowledge 8:00 so as to pursue desired outcome 18:50 -opportunity solution tree 19:20

2 minutes summary: The transcript is from a seminar on stakeholder management where the speakers shared their experiences and tips on how to effectively work with stakeholders throughout the product life cycle. The first speaker, Alex, emphasized the importance of including relevant stakeholders from the beginning and making sure to identify all key players. He shared a personal experience of dealing with a stakeholder who questioned why they were not consulted and how he addressed the issue by listening, understanding the stakeholder's perspective, and adjusting the project accordingly. The next speaker, representing a large tech company, talked about how to manage stakeholders in a toxic environment. The key points included avoiding gossip, separating personal feelings from the problem, and focusing on constructive solutions. The third speaker discussed the challenge of aligning with stakeholders midway through a project and avoiding scope creep. The important advice was to have an open communication channel, prioritize the key stakeholders, use a data-driven approach to determine essential features, and be open to saying no when necessary. The final speakers highlighted the importance of stakeholder partnerships over management. They emphasized the need for collaboration, understanding different stakeholders' preferences and communication styles, and using empathy to build connections. They also discussed strategies for equipping stakeholders with the right information and skills, especially when dealing with difficult or resistant stakeholders. Overall, the speakers stressed the importance of building strong relationships with stakeholders, understanding their needs, and effectively communicating with them throughout the product life cycle. They recommended being proactive in identifying key stakeholders, listening to their perspectives, adapting to their communication styles, and being transparent and honest in dealing with challenges. They also highlighted the significance of storytelling in engaging stakeholders, being data-driven in decision-making, and prioritizing stakeholder needs to avoid conflicts and scope creep. In conclusion, effective stakeholder management involves inclusivity, empathy, transparency, and proactive communication. By building stakeholder partnerships, understanding their preferences, and equipping them with the necessary information and skills, product managers can navigate challenges, address resistance, and align stakeholders towards achieving successful product outcomes. It is essential to prioritize key stakeholders, build strong relationships, and maintain open and honest communication to ensure the success of product development projects.

Make that 5 years

I'm checking this out 3 years later thanks for the great advice

Buenísima iniciativa, speakers y presentaciones!

Thanks for your insights!

Abhishek from India !

Hi, from Australia :

Has anyone ever walked into a mall with a laptop or phone, and tried stopping random people to use your product?

Brilliant talk! Well done :) I loved the slide: "10x Better Product + Mission-Driven Marketing = Word of Mouth Growth". This is such a powerful strategy!

nice!

Como eu vou pegar um item do que o usuário espera e inserir quais são os problemas dessa funcionalidade que ainda não existe?

Depends on the engineer. My engineers have no interest in learning about the business problems.

Thanks. Insightful presentation!

Literally a gem! So grateful for this content.

Regarding prototyping, a doubt, can't we prototype on Figma?

Slides are not clear, kindly share it. Insightful presentation

This guy is awesome!

Agile is not a process, "we value more people and interaccions over processes and tools"

It's hard to read the slides behind Nacho Bassino

Awesome presentation Janna 🎉 ❤OIKRS

thanks for sharing the talk, Joshua is awesome! (thanks to the channel owners for trimming the video)

Really impressed with presentation which was rich with the visuals, it was really to digest all the information he presented.

Very valuable and insightful talk.. The way they formulate their mission and harness their userbase to both grow and shape regulations is awesome. Wise is kickin' it..

Extraordinary content - thanks for this!

Extremely useful and points can be implemented in practical life ❤

AI/LLM for organic, (semi-)automated customer feedback, sentiment tracking and market research is one of the most fascinating areas of opportunity. - with bots trawling, crawling, indexing and (broadly) synthesising multifactorial product and market commentary, wherever it resides on the net. 👍👍🚀

Lean, Agile and Design Thinking all have their strong points. It's almost an embarrassment of riches. You have to pick what you are actually going to do. Lean is very strong on eliminating wastes and only producing customer value. Obviously, there is also a need for indirect support for customer value (payroll, IT). Knowledge first, decisions second. Quality. You make a specification and then execute it. Loopbacks are a failure. Scientific problem solving is encouraged. You adapt to the changing environment or go extinct (living, changing systems). Lean Startup (Reis) believes in Validated Learning, Split A/B testing among cohorts and Innovation Accounting. Minimum Viable Products that generate customer feedback are fine. Even if you have to cheat (an accountant is actually entering your accounting information, only the user interface is being tested). Agile is not big on specifications. If you are lucky, you can read the comments in the code to figure out what is going on. Agile is very good as customers satisfaction and getting code in front of the customer. Sprints are like lean small batch sizes. Managers give the right information, at the right item, in the right amount to software engineers. You don't let software pile up in batches and go stale. Integration design reviews are still useful and cast a wide net. Things most often break at the interface and detailed design always points out improvements that can be made. Design Thinking (user interface, user experience) is all about customer satisfaction (quality). Just hope that your typical customer is really typical. (The best software in the world is the one you have been using for years and can use without thinking.) Software Anthropologists and Graphic Artists. What to ACTUALLY do?

Amazing§ very helpful

Thank you so much for this. We all need this injection of common sense and logic.

the audio quality is beyond terrible ... after 43:07 there's no sound at all

Çok faydalı bir program olmuş hepinizin eline ve diline sağlık. Ali Bey'in de çoraplarını çok beğendim. Çorap linki gelir mi acaba 🤭🙌

Only billion dollar idea😮😮

It would have been good if the camera view of the panel had been made bigger so we could actually see the panelists

Leo, arrasou muito! Uma verdadeira fonte de conhecimento! Crânio , gênio!

NOTES Product management focuses on developing and managing a specific product or product line. Product managers are responsible for defining the product strategy, developing the product roadmap, working with cross-functional teams to execute that roadmap, and ensuring the product meets the target market's needs and delivers business results. It has 2 steps Build the product Ship the product to end customers Platform product management, on the other hand, focuses on developing and managing a platform that enables third-party developers to build and deploy their applications or services. Platform product managers must balance the needs of both developers and end-users and create a platform that is scalable, reliable, and secure. It has 3 steps Build the product Enable creators to build products on it. Ship the product to end customers. Types of platform Developer Platform Provides API, Tools, and Servers to developers Builder Focused No relation with end customers Eg, AWS, Stripe, Twilio Marketplace / Consumer Platforms Connect creators and consumers of X Creators and consumer-focused Direct relations with both consumers and creators Product Extension Platforms Purpose of making the product better through third-party developers Combination of developers and marketplace Consumer-focused Primary relationship with consumers Eg, Shopify, Salesforce, Android Strategy in Product Extention Platforms: Customers problems you need to solve = problems you could feasibly solve + Enable 3rd party developers to solve the gap ( they can because they are distributed around the world, understand niches and can build faster ) How to approach a platform Accelerate the Flywheel: More Developers -> More Apps -> More Customers/Merchants want your product -> More Developers. Structure Teams around Flywheel App Capabilities Teams: Create new ways for developers to create apps ( KPI: No of apps built) App Store and Algorithms Teams: Connect the right app to the right merchant at the right time ( Build marketplace, recommendation systems ) (KPI: No of Apps used) Developer Growth Teams: Enable developers to know where opportunities lie ( Analytics, Insights on what customers need, also Payouts to developers) (KPI: No of developers active) Trust is Flywheel grease: Invest in trust features like permissions, privacy, security, data management, quality support, and reviews. Develop Skills - Economics, Operations, Software Engineering Software Background: Developer Empathy, Product is code Economics: Microeconomics, balancing supply-demand marketplace, the intuition of free market is important Operations: Enormous human effort is required to maintain quality and safety on the platform, a constant race to automate operations as scale occurs and also introducing new features Earn trust with developers Purpose, Policy and Business Model should be in harmony Purpose: Why your platforms exist, Policy: What you punish, Business Model: What you reward App Store Algorithm optimizes for merchant success (Marketplace Ranking Factors) How do you introduce policy changes Invest in Community Get your first developers like how you get first customers Invest in meetups, conferences Treat developers as business partners Pick up the phone, especially when it is bad Build internal governance practices to ensure fairness Constantly find ways to make them more successful Be Patient Platform creativity is unbelievable Platform changes .. just take a long time Need to do things carefully and sequentially. Follow the playbook Stay open as long as possible ( Spectrum of open(creativity) to closed(control) )

This is one of the gem by Marty

So glad I found this video! So inspiring storytelling.

Starts at 2:00

Make sense, I had already thinking like these for years without known...

"The good CEOs they all know that they need teams of missionaries, not teams of mercenaries" WOOH!

Quite the eye-opener. The conversation surrounding "eye-light-up" moments was a key takeaway!

it has 9 comments? amazing, well? It seems like he talking about something non-understandable. and this gangsta movie...?

12:36 Engineers are dangerous. They dream a lot, but… 😅

Exactly the content I was looking for

Just don't have product managers.