Risks are analyzed upfront by strong teams

• Value risk (will customers buy it)
• Usability risk (will customers know how to use)
• Feasibility risk (will engineering deliver)
• Business viability risk (will it make $)

Product teams should be:

• Cross functional from day one: product, design and engineering working together
• Mercenaries VS missionaries: build what is told VS think about what to do
• Co-located
• Durable (hang around for the long run)

Characteristics of a PM role

• Understand your customer (qualitative and quantitative)
• Understand data
• Understand your business (stakeholders)
• Understand your industry (competitors, trends, domain knowledge)

OKR process - Objective and Key results

Objective - qualitative

Key result - quantitative

Teams propose key results, no more than 3 per time, company wide scoring criteria