I'm a former Software Engineer turned Product Manager with over 15 years working on software products. I've benefited hugely from great coaching and mentoring during my career and I'm keen to pay this forward. I'd love to speak to anybody interested in cross-functional teams or continuous discovery.
My Mentoring Topics
- Product management
- Continuous Discovery
- User story mapping
- Leading cross-functional product teams
- Breaking into product management
- From Software Engineering to Product Management
- Building high-performing teams
- SASS product management
You need to be logged in to schedule a session with this mentor. Please sign in here or create an account.
Continuous Discovery Habits - Discover Products that Create Customer Value and Business Value
Teresa Torres
Key Facts and Insights Continuous Discovery: The book paints a vivid picture of the continuous discovery process, arguing that it's not a linear or one-off process but an ongoing cycle of learning, adapting, and improving. Customer-Centric Approach: The author underscores the importance of a customer-centric approach, suggesting that understanding customer needs and behaviors should be at the heart of product development. Outcome-Over-Output Mindset: Torres emphasizes the importance of focusing on outcomes rather than outputs. It's not about how many features a product has, but how it impacts customers' lives. Collaborative Discovery: The book outlines the importance of collaborative discovery, promoting the idea of involving the whole team in the product discovery process. Opportunity Solution Tree: Torres introduced a unique tool called the Opportunity Solution Tree to visualize and prioritize opportunities for product improvements. Experimentation and Validation: The author stresses the necessity of experimentation and validation throughout the product development process. Interview Techniques: The book provides insightful interview techniques and tools to gain a deep understanding of customer needs. Building Empathy: Torres highlights the importance of building empathy with customers to create products that genuinely solve their problems. Product Trio: The book suggests that the most effective discovery teams are composed of a product manager, a designer, and a software engineer - referred to as the "product trio". Discovery Cadence: The book advocates for a weekly discovery cadence, where teams engage in regular discovery activities to keep learning and adapting. In-depth Summary and Analysis "Continuous Discovery Habits" is a comprehensive guide to modern product management. Teresa Torres, an experienced product discovery coach, brings to light the importance of continuous discovery in creating valuable products. Torres starts by challenging the traditional, linear model of product development. Instead, she proposes a cycle of continuous discovery where learning, adapting, and improving are continuous processes. As a professor who's been dealing with these topics for years, I find this perspective refreshing. It aligns well with the rapid pace of change in today's digital world, where products must constantly evolve to meet changing consumer needs. The book's emphasis on a customer-centric approach is another crucial insight. Torres argues that understanding customer needs and behaviors should be the cornerstone of product development. This aligns with concepts I've taught over the years, such as "user-centered design," where the user's needs, wants, and limitations are a focus at all stages within the design process. A key theme in the book is the outcome-over-output mindset. Torres points out that product teams often get caught up in delivering features (output) and lose sight of the desired outcomes. This resonates with the "Jobs to Be Done" theory, which argues that customers don't buy products or services; they "hire" them to do a job. Another key insight from the book is the role of collaboration in discovery. Torres argues that involving the whole team in the product discovery process can lead to better solutions. This concept parallels the "cross-functional team" approach popular in agile development practices. The Opportunity Solution Tree, a unique tool introduced in the book, is an effective way to visualize and prioritize opportunities for product improvements. As an academic tool, it encourages systematic thinking and can help teams avoid jumping to solutions before thoroughly exploring the problem space. Torres' emphasis on experimentation and validation is in line with the scientific method and lean startup principles. She suggests that before investing significant resources into building a product, teams should validate their assumptions through small, quick experiments. The book is also a valuable resource for learning interview techniques to gain a deep understanding of customer needs. Torres provides practical advice on how to ask effective questions and listen empathetically. Building on the idea of empathy, Torres underscores the importance of building empathy with customers. She argues that deep empathy leads to products that genuinely solve customer problems, a concept that aligns with the empathize stage in the Design Thinking process. The product trio concept proposed in the book is also noteworthy. Torres suggests that the most effective discovery teams are composed of a product manager, a designer, and a software engineer. This trio ensures a balance of business, design, and technical perspectives in the discovery process. Finally, Torres advocates for a weekly discovery cadence, where teams engage in regular discovery activities. This routine allows teams to continuously learn, adapt, and improve, keeping the spirit of continuous discovery alive. In conclusion, "Continuous Discovery Habits" provides a comprehensive framework for modern product discovery. It echoes many concepts I've taught over the years while introducing new tools and perspectives. By internalizing the book's key insights, teams can create products that create real value for customers and businesses alike.
View
Inspired
Marty Cagan
Key Insights from "Inspired" The importance of deep customer understanding in product development. The concept of Risks and Opportunity Assessment Process (ROAD) in product planning. The role of Product Discovery in creating successful products. The value of using prototypes in product design and testing. The significance of Product Manager in an organization. The application of Agile principles in product development. The difference between product delivery and product discovery. How to create a compelling product vision and strategy. The importance of validated learning in the product development process. Understanding the role of technology and design in product development. The importance of strong leadership in fostering a successful product team. In-depth Analysis of "Inspired" "Inspired" is a seminal work by Marty Cagan that provides a comprehensive guide on how to create technology products customers love. It is based on Cagan's extensive experience in the tech industry, having worked with some of the most successful companies in Silicon Valley. The first key insight from the book is the importance of deep customer understanding. Cagan emphasizes that successful product development starts with understanding customers' needs, desires, and problems. This involves conducting user research, customer interviews, and surveys, among other methods. This approach aligns with the principles of human-centered design, a design philosophy that focuses on understanding and addressing the needs and experiences of users. Cagan introduces the concept of Risks and Opportunity Assessment Process (ROAD), a strategic tool for product planning. It helps businesses identify potential risks and opportunities in their product development process and make informed decisions. Product Discovery is another essential concept in the book. It involves exploring and validating product ideas before development begins. Cagan suggests using prototypes during this stage to visualize and test product concepts. This aligns with the Lean Startup approach, which values quick experimentation and validated learning. The author also emphasizes the role of the Product Manager in an organization. According to Cagan, Product Managers should be "product CEOs," owning the product vision, strategy, and roadmap. They should lead cross-functional teams, work closely with customers, and make crucial product decisions. Cagan's approach to product development is rooted in Agile principles. He advocates for iterative development, continuous improvement, and close collaboration between development teams and stakeholders. He also distinguishes between product delivery and product discovery, arguing that while Agile methods are excellent for delivery, different methods are needed for discovery. The author also provides guidance on creating a compelling product vision and strategy. A strong vision and strategy can guide decision-making, motivate the team, and communicate the product's value proposition to stakeholders. Cagan underscores the importance of validated learning, a concept borrowed from Lean Startup methodology. This involves testing assumptions and learning from customers' feedback to improve the product iteratively. Moreover, Cagan discusses the role of technology and design in product development. He emphasizes the need for product teams to leverage emerging technologies and prioritize user experience in their product design. Lastly, Cagan stresses the importance of strong leadership in fostering a successful product team. He believes that leaders should empower their teams, cultivate a culture of innovation, and ensure alignment with the organization's vision and strategy. In conclusion, "Inspired" is a comprehensive guide that offers practical insights and strategies on product development. It embodies a deep understanding of the importance of the customer, emphasizes the value of discovery and validation, and promotes a culture of innovation and agile principles. All these elements are crucial in the rapidly changing world of technology product development.
ViewUser Story Mapping - Discover the Whole Story, Build the Right Product
Jeff Patton, Peter Economy
Key Facts from "User Story Mapping - Discover the Whole Story, Build the Right Product" Understanding the Big Picture: The book emphasizes the need to see the bigger picture of a product, rather than focusing solely on individual features or user stories. Emphasis on User Journey: The book highlights the importance of understanding and mapping the user journey in order to build a product that truly caters to the user's needs and solves their problems. The Concept of Story Mapping: The book introduces the concept of story mapping as a tool to visualize the user journey and prioritize features accordingly. Collaboration and Communication: The book stresses the importance of effective collaboration and communication among team members as key to successful product development. Continuous Learning and Adaptation: The book advises on the need for continuous learning and adaptation throughout the product development process. Focus on Value: The book urges teams to focus on delivering value to the user, rather than getting caught up in technical details or feature creep. Importance of Feedback: The book highlights the value of feedback, both from users and team members, to improve the product and the development process. Agile Development: The book delves into the principles of agile development, and how user story mapping can contribute to this methodology. Relevance of User Personas: The book discusses the importance of creating user personas to better understand the target audience and their pain points. Iteration and Incremental Delivery: The book advocates for an iterative approach to product development, with regular, incremental delivery of value to the user. Role of User Stories: The book explains the role of user stories in expressing the needs and goals of the user, and how they can be used to guide product development. An In-Depth Analysis of "User Story Mapping - Discover the Whole Story, Build the Right Product" Jeff Patton and Peter Economy's book "User Story Mapping - Discover the Whole Story, Build the Right Product" can be seen as a comprehensive guide to understanding, creating, and utilizing user story maps in the context of product development. The authors emphasize the importance of seeing the big picture when developing a product. Too often, teams get lost in the details of individual features or user stories, losing sight of the overall product vision and user needs. By using story mapping, teams can visualize the whole user journey, align their efforts with the product vision, and prioritize features that bring the most value to the user. The concept of story mapping is introduced as a pivotal tool for product development. A story map is a visual representation of the user journey, highlighting the tasks users perform, the sequence in which they perform them, and the value they derive from each task. This map serves as a guide for product development, helping teams focus on building features that enhance the user experience and solve real problems. Collaboration and communication are identified as crucial components of effective product development. The process of story mapping inherently fosters collaboration, as it requires input from various team members to create a comprehensive and accurate map. Furthermore, the visual nature of the map facilitates communication, making it easier for everyone to understand and contribute to the product vision. The book advocates for a continuous learning and adaptation mindset. This aligns with the principles of agile development, which the authors delve into. They argue that user story mapping supports agile development by providing a flexible roadmap that can be adjusted as new insights and feedback are gathered. Feedback, both from users and team members, is highlighted as a valuable resource for improving the product and the development process. Regular feedback loops allow teams to learn from their mistakes, adapt their strategies, and continuously deliver value to the user. The authors discuss the relevance of user personas in understanding the target audience and their needs. Personas, combined with user stories, can help teams empathize with users and build products that truly cater to their needs and solve their problems. The book also champions an iterative approach to product development, advocating for regular, incremental delivery of value to the user. This approach, supported by user story mapping, allows teams to quickly respond to changes and continuously improve the product based on feedback and learning. In conclusion, "User Story Mapping - Discover the Whole Story, Build the Right Product" offers a powerful tool for product development, providing a framework for understanding the user journey, prioritizing features, fostering collaboration, and delivering continuous value to the user. The concepts presented in the book align with established principles of agile development and user-centered design, making it a valuable resource for anyone involved in product development.
ViewHow Big Things Get Done - The Surprising Factors Behind Every Successful Project, from Home Renovations to Space Exploration
Bent Flyvbjerg, Dan Gardner
Key Facts and Insights The concept of 'Reference Class Forecasting' is a crucial tool for project planning which helps to prevent over-optimism and underestimation of costs. Success in big projects doesn't rely solely on technical competence, but also on understanding and managing the political, social, and economic aspects. The 'Outside View' approach is essential for realistic project planning, as it involves an unbiased assessment of the project based on similar past projects. Strategic Misrepresentation, often a result of political and economic pressures, can lead to project failure if not appropriately managed. The role of power and its influence on decision-making processes in large projects is significant. Understanding the 'Survival of the Unfittest' concept: the most unfit projects often survive because of various manipulations in the planning and execution phase. Importance of transparency, accountability, and valid data in ensuring project success. Big projects have a 'lock-in' or 'capture' effect, making it difficult to halt or change course even in the face of failure. Every successful project requires a 'Project Champion' who drives the project against all odds. Concept of 'Institutionalized Action' where the standard practices and norms of an organization can both aid and hinder the success of a project. Detailed Summary and Analysis The book starts with an emphasis on the importance of 'Reference Class Forecasting', a concept originated by Nobel laureate Daniel Kahneman. This involves looking at outcomes of similar past projects to make accurate predictions about the current project. This method is a crucial tool to overcome the common human biases of over-optimism and underestimation of costs and complexities. My years of experience in project management align with this perspective, underscoring the value of historical data in forecasting project outcomes. The authors then delve into the understanding that success in big projects doesn't rely solely on technical competence. They argue that managing the political, social, and economic aspects is equally important. This insight resonates with the multi-dimensional nature of project management, where an understanding of the project's context and stakeholder landscape is as critical as technical know-how. Another key concept introduced is the 'Outside View'. This approach involves taking an unbiased look at a project, free from the internal views and biases of project stakeholders. This external perspective, based on similar past projects, aids in realistic and effective planning. From my experience, this approach helps counteract the 'inside view' bias that often leads to over-optimism and underestimation of project risks and complexities. One of the most insightful sections of the book deals with Strategic Misrepresentation. The authors argue that due to political and economic pressures, project planners and promoters often misrepresent the costs, benefits, and risks of projects. If not managed, this can lead to significant project failure. This concept aligns with my observations of the political dimensions of project management, where power dynamics and vested interests often influence project decisions. The book also discusses the critical role of power and its influence on decision-making processes in large projects. It introduces the concept of 'Survival of the Unfittest', where the most unfit projects often survive because of manipulations in the planning and execution phase. This concept is a stark reminder of the reality of project politics and the need for transparency and accountability in project decision-making. Furthermore, the authors highlight the importance of transparency, accountability, and valid data in project success. They argue that these factors help in better decision-making, risk management, and stakeholder management, leading to improved project outcomes. The book also delves into the 'lock-in' or 'capture' effect in big projects. Once a project reaches a certain stage, it becomes difficult to halt or change course, even in the face of apparent failure. This concept is all too familiar in project management, where sunk costs and political pressures often make it difficult to 'pull the plug' on failing projects. The authors then discuss the critical role of a 'Project Champion' in every successful project. This individual drives the project against all odds, navigating through technical, political, and economic challenges. My experience aligns with this perspective, emphasizing the value of leadership and vision in project success. Finally, the book introduces the concept of 'Institutionalized Action', where the standard practices and norms of an organization can both aid and hinder project success. This insight underscores the importance of understanding an organization's culture and practices in project planning and execution. In conclusion, this book provides a comprehensive and insightful exploration of the factors behind successful large-scale projects. It emphasizes the importance of not just technical competence, but also strategic foresight, political acumen, and leadership in achieving project success. These insights align with my years of experience and research in the field of project management.
View
The Lean Startup
Eric Ries
Key Insights from "The Lean Startup" Entrepreneurship is Management: A startup is an institution that needs to be managed. The Lean Startup approach fosters companies that are both more capital efficient and that leverage human creativity more effectively. Validated Learning: Startups exist not just to make stuff, make money, or serve customers. They exist to learn how to build a sustainable business. Innovation Accounting: To improve entrepreneurial outcomes and hold innovators accountable, a new kind of accounting is needed, one that focuses on the boring stuff: how to measure progress, how to set up milestones, and how to prioritize work. Build-Measure-Learn: The fundamental activity of a startup is to turn ideas into products, measure how customers respond, and then learn whether to pivot or persevere. Pivot or Persevere: The most successful startups are able to decide when to stick to their guns and when to change direction. Minimum Viable Product (MVP): The Lean Startup method teaches you to drive a startup-how to steer, when to turn, and when to persevere-and grow a business with maximum acceleration. Continuous Deployment and Testing: The Lean Startup methodology promotes continuous rapid prototyping and a "Just do it" mindset. With rapid iterations you can decide if the product vision is viable or not. Adaptive Organization: The Lean Startup proposes an organizational structure that fosters innovation. Small Batches: The Lean Startup process works in small batches to minimize the cost of change and risk. Work smarter not harder: The Lean Startup practice advocates for entrepreneurs to work smarter not harder. Detailed Analysis "The Lean Startup" by Eric Ries is a compelling and innovative approach to launching companies that are faster, smarter, and more successful. At its core, it is about learning what your customers really want and learning it quickly. It's about continuously testing what you think your customers might want and adapting based on the results, and doing this before you run out of money. Entrepreneurship is Management is a fundamental tenet of this book. An entrepreneur, according to Ries, is anyone who creates a new product or service under conditions of extreme uncertainty. This is as true for two people in a garage or a group of seasoned professionals in a Fortune 500 boardroom. Thus, managing a startup is a balancing act between sticking to your core vision and being endlessly adaptable. The concept of Validated Learning is one of the most profound insights in the book. Instead of making elaborate plans based on lots of assumptions, you can make constant adjustments with a steering wheel called the Build-Measure-Learn feedback loop. This concept involves quickly assembling a Minimum Viable Product (MVP) and improving it based on feedback, as opposed to perfecting a product without any customer input. This brings us to the concept of Minimum Viable Product (MVP). The MVP is a version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least effort. This strategy saves time and resources that would have otherwise been wasted on developing products that people don't want. Innovation Accounting is another significant aspect of the Lean Startup methodology. It works in three steps: using an MVP to establish real data on where the company is right now, then tuning the engine (improving the product) from the baseline towards the ideal, and finally making a decision to pivot (changing fundamental aspects of the product) or persevere. The concepts of Pivot or Persevere are central to the Lean Startup methodology. A pivot is a fundamental change in strategy that results from the feedback collected from the MVP. If the MVP isn't achieving the desired results, the startup needs to pivot by making a fundamental change to their product. If the MVP is successful, the startup can persevere and continue improving the product based on customer feedback. Continuous Deployment and Testing, Adaptive Organization, and Small Batches work in tandem to create a responsive and agile startup. Continuous Deployment allows for rapid product iteration, while small batches ensure that a startup can adapt quickly to customer feedback and market changes. The adaptive organization understands that failure is an integral part of innovation and fosters an environment that encourages learning from failure. The Lean Startup methodology encourages entrepreneurs to Work smarter not harder. It's not about the hours you put into your work. It's about the work you put into those hours. The Lean Startup methodology is not just about how to create a more successful entrepreneurial business, it's about what we can learn from those businesses to improve virtually everything we do. In conclusion, "The Lean Startup" provides a scientific approach to creating and managing successful startups in an age of uncertainty. It significantly increases the chances of building a successful venture by learning what customers want quickly and scientifically, as opposed to relying on guesswork or assumptions. This methodology has been adopted by countless startups and corporations around the world and continues to grow in popularity due to its proven success and effectiveness.
View
R.
30.October 2024Mike gave me very useful info and feedback. I'm very grateful for his time and commitment. He's also very friendly and easy-going. Looking forward to working and learning more from him. Thank you, Mike!