Risks are tacked up front
Risks are tacked up front rather than at the end. Products are no longer designed sequentially in waterfall-style top-down roadmaps because that method puts the largest risks at the end of the project instead of the beginning.
Graph:
- 122.03.02 PM Responsibilities - Risks are tackled up front to 125.010 Books - Inspired - Marty Cagan
- 122.03.02 PM Responsibilities - Risks are tackled up front to 122.03.01 PM Responsibilities - Workflow
- 122.03.02 PM Responsibilities - Risks are tackled up front to 122.02.02 PM Why - Not all product discovery will be successful
- 122.03.02 PM Responsibilities - Risks are tackled up front to 122.01.10 PM Skillset - Prioritization
- 122.03 PM Responsibilities - Responsibilities of a PM to 122.03.02 PM Responsibilities - Risks are tackled up front
- 122.07.03 PM Discovery Process - What is product discovery to 122.03.02 PM Responsibilities - Risks are tackled up front
- 122.08.06 PM User Testing - Understand and learn quickly - let go of pride to 122.03.02 PM Responsibilities - Risks are tackled up front
- 122.11.001 User Story Mapping to 122.03.02 PM Responsibilities - Risks are tackled up front
- 122.11.003 User Story Maps - Story Maps help us iterate fast to 122.03.02 PM Responsibilities - Risks are tackled up front
- 122.11.012 User Story Maps - Story Maps are used to define prototypes to 122.03.02 PM Responsibilities - Risks are tackled up front
- 122.11.017 User Story Maps - Never create a map before defining user needs to 122.03.02 PM Responsibilities - Risks are tackled up front