Product Management Process & Responsibilities

	A	B	C	D	E	F	G	H	I	J	K	L	M
1			Discovery (Elias structures and communicates, involved in Design if necessary)				Delivery (Roman)				Rollout	GTM/Analytics (John)
2	Phase		Opportunity Backlog (Elias)	Roadmap (Roman)	Product Specs (Barret)	Design (Barret x Kenny)	Tech Specs (Tech Team)	Delivery Backlog	Implementation	QA	Launch/Rollout	Product Marketing	Analytics
3	Deliverables		Product feedback repository	Rolling Now/Next/Later Roadmap or 3-12 months roadmap	Product Brief	Process Diagram	Technical Design Docs					(User) documentation
4			List of strategic objectives/features	Discovery Backlog	High-level user needs/stories/requirements User Story Map	User Flow	Detailed user stories + technical requirements
5						Prototype	Acceptance criteria
6						High fidelity designs	Set release date
7	Activities		User Research (JTBD interviews; measure customer satisfaction and effort)	Assessing priorities and building a roadmap/timeline	User research/collect user data	Ideation & Prototyping	Tech Planning					Communicate release to stakeholders	Analyze usage
8			Customer feedback collection	Prioritization and validation (Feature Shopping)	Write specs for new features	UI/UX Testing						Launch campaigns
9			Gather strategic input from leadership		Product analytics (for iterations/extensions)							Write user docs
10	Cross-functional meetings/Cadence							Cycle kickoff, cycle retro
11
12
13	Responsibilities	Product Management	Collecting and aggregating new ideas and customer feedback Maintain a structured backlog of all ideas and product opportunities based on: - company strategy stakeholder inputs (marketing, sales, account management, operations, management) - customer feedback	Prioritize opportunities/features Deciding on what opportunities go into discovery/what features go into development	Address the 4 types of product risk through research and testing: Value Risk: Will the customer buy it or chose to use it? Usability Risk: Will the customer be able to use it? Feasibility Risk: Will we be able to build it with our resources? Business viability risk: Does it work for the business? Clearly communicate the underlying opportunity/user need to the product team. Consider alternative solutions/surface best solution based on user needs, technical trade-offs...				Be responsive to input requested from engineering (unblock engineering)			- Create product training material and product documentation for stakeholders where necessary - Conduct trainings where necessary - Create relevant marketing collateral (ownership for creation with marketing?) - Align product rollout with the relevant stakeholders (e.g. Product-operations-handshake) - Publish release notes (intern + extern)	- Monitor new features (success metrics)
14		Product Design				- Deliver mockups and low-fidelity prototypes - Run user tests to ensure the customer gets the right value out of and the product is usable - Deliver high-fidelity prototypes and design specs - Consider and design for edge cases			Be responsive to input requested from engineering (unblock engineering)				Monitor UX
15		Engineering		Contribute technical topics to roadmap (tech debt, scalability...)				Write technical specifications/design docs	Report progress; Flag scope changes				Monitor reliability/bugs
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100