- Who is the target?
- What is its (real) problem?
- Which use cases and features do we have to build and what are the differentiators with competitors?
- w/marketing guys to identify acquisition channels
- w/sales guys to identify monetization models
- w/users to identify valuable feedback
- User experience do not end at the UI of an app: what happens before and after using the app is important to design
- Defining the right metrics: qualitative and/or quantitative
- Measuring in a data-driven way vs data-informed way
Compromising between:
- Maximizing impact on the user experience, the business and the data learnt
and:
- Minimizing the required workload, the required delay to measure and the technical debt
- Getting everyone on the same page without the need for exhaustive documents
- Building a product is not just about delivering predetermined features at predetermined dates -- it's about understanding and solving a problem by driving iterations based on launches and measures
- Being one step ahead of your teammates to be able to challenge them
- Building company standards above market standards
- From the inside: requests from other teams such as marketing
- From the outside: complaints from customers
- The hard path of launching, measuring and sometimes killing a product or a feature
- Consolidating all inputs, all the time, with a minimum effort
- The necessity of loving to remove human and technical hurdles on a daily basis
- Compromising between execution speed and maintainability + reliability
- When to A/B test and when not to A/B test
- Choosing the right user segments
- Choosing the right statistical methods
- Choosing the right decision tools
- Local vs global maxima
By measuring:
- User experience quality
- User outcomes
- User loyalty
- The limitations of the NPS
- Inspiring the vision to the entire team
- Repeating, repeating and repeating the "why", each week
- The right meetings, with the right people, at the right time, with the right duration
- Mistakes: learning to be the "responsible" party for the mistakes your team is "guilty" of making, and teaching them the difference between the two
- Successes: accepting that when the team wins, the players are celebrated, not the coach
Evangelizing the discipline of product management, its promises, its processes and its tools:
- w/developers and designers
- w/managers
- w/C-Levels
- The necessity of loving to understand people