Use Prototypes for Executive Reviews
ManagementTo prevent oversight processes from forcing a waterfall approach, bring real user feedback and prototypes to reviews to prove progress.
2 more supporting quotes are in the member records.
마티 케이건
Founder of Silicon Valley Product Group; author of Inspired
1,016 records in all
3 free questions a day, no sign-up.
55 basic records of 365
Principles are our summary of their public statements.
To prevent oversight processes from forcing a waterfall approach, bring real user feedback and prototypes to reviews to prove progress.
2 more supporting quotes are in the member records.
The primary challenge for any creator, even with AI tools, remains identifying a viable and valuable solution rather than just the act of coding.
3 more supporting quotes are in the member records.
A founder should recognize that usability and aesthetics require different skill sets; hiring one 'designer' may not cover both needs.
1 more supporting quote is in the member records.
Senior executives should provide business context and metrics rather than dictating specific features, allowing product managers to find the best solutions.
Supporting quotes
The business strategy and business portfolio planning provides a budget and a set of business metrics.2 more supporting quotes are in the member records.
When addressing problems, it is more effective to speak specifically about the group in pain rather than using broad, all-encompassing statements.
3 more supporting quotes are in the member records.
Creating a diverse workforce requires a deliberate effort to interview and provide opportunities to those who do not look like the current majority.
3 more supporting quotes are in the member records.
Gaining experience in engineering, marketing, or business development makes a product leader more effective at building organizational bridges.
Managers should follow a structured approach: Share intent, identify when it Happened, describe Actions, explain Results, Engage with curiosity, and Discuss next steps.
3 more supporting quotes are in the member records.
Splitting product definition between a product manager and a business analyst creates confusion and reduces accountability.
Supporting quotes
Identify the true product managers, and empower them to own product definition completely, from the high-level to the details. Clear ownership and clear accountability.1 more supporting quote is in the member records.
A product manager should clear at least 10 hours a week from meetings to focus on long-term product improvements.
3 more supporting quotes are in the member records.
A product manager must use their own product or watch a user interact with it at least every 48 hours to stay grounded.
3 more supporting quotes are in the member records.
If teams consistently make poor decisions regarding shared tools, the solution is often providing better business context rather than adding more process.
Supporting quotes
I attribute most of the benefits to the increased level of motivation, and true sense of ownership, when teams feel more in control of their own destiny.2 more supporting quotes are in the member records.
Focus first on discovering a solution that is valuable, usable, and feasible before spending time on pricing optimization or cost-cutting.
3 more supporting quotes are in the member records.
Create an architect role to allow top engineers to advance professionally and financially without being forced into people management.
Supporting quotes
One of the most common mistakes that product managers make is to not include engineering early enough to make a difference.2 more supporting quotes are in the member records.
User experience design must be finalized before implementation starts to avoid technical debt and psychological resistance to change.
3 more supporting quotes are in the member records.
A product manager needs deep knowledge of their own company's sales, marketing, finance, and legal requirements to build successful products.
3 more supporting quotes are in the member records.
Even with AI, successful products still require distinct expertise in business constraints, user experience, and technology to solve complex problems.
3 more supporting quotes are in the member records.
Decision-making power should be moved down to the people closest to the actual problems and the technology.
2 more supporting quotes are in the member records.
Use product discovery for new features and major changes, but use optimization for refining existing user experiences and business results.
3 more supporting quotes are in the member records.
Teams should be assigned specific business problems to solve rather than a list of features to build, allowing them to discover viable solutions.
Supporting quotes
If you're not doing continuous delivery, then at the very least you should be doing true releases no less than every two weeks.the product team moves from a subservient relationship, to a collaborative relationship where the product team must discover a solution that the customers love yet works for the business.1 more supporting quote is in the member records.
You are seeing 152 basic records. Membership answers from all 1,016 of this master's records.
See membershipProduct and engineering
These records are our compilation of public statements and sources. We are not affiliated with or endorsed by Marty Cagan or any related company. If something should come down, tell us. Takedown request form