Product Development

How we do product development at Product Hunt.

- https://blog.rstankov.com/collaborative-single-player-mode/
- https://blog.rstankov.com/how-i-plan-and-execute-features/

Transcript

1. Product Development Radoslav Stankov 12/01/2020
2. ! Context " Process # Stories $ Agenda
6. How it all started
7. An Idea t %
8. Funding t ⛽
10. Product Hunt + AngelList t '
12. ~150 product launches per day are featured at Product Hunt
23. ( Ads 2.0 # Discussions 2.0 ) New mobile app * Updated post pages + New activity feed , Karma - Moderation 3.0 . User verification / New onboarding ! StackCam 0 Updated comments " Redesign of topics 1 New profiles 2 Topic feed 3 Need4Speed 4 GoldenKitties 2020 5 Redesign of collections 6 Mobile web improvements 7 Project delight 8 Trust 2.0 9 Summer cleanup : YourStack ; Newsletter updates < Howdy product initiatives in 2020 =
24. image credit: remotehub.io
25. Process
28. “Process is automatic decisions for trivial questions and framework for making decisions for all other questions.” - Rado What is process
29. Collaborative Single Player Mode
32. https://blog.rstankov.com/collaborative-single-player-mode/
34. Design Sprint Implement Sprint Implement Sprint Bug Duty Work in 2 week cycles > ? @ A
36. https://basecamp.com/shapeup Inspired by...
37. ...kinda B
38. Project Iteration Delivery Retro every 2 weeks
39. Project Iteration Delivery Retro
40. Project C scope D target metric ⏳ milestones every 2 weeks F developer G designer H community member I Slack channel J only mission oriented meetings
42. Project Iteration Delivery Retro
43. Task Planning ⚽ focus first on what won’t change L know what "ready" means M what should I do today? ⚾ retrospectives
44. https://blog.rstankov.com/how-i-plan-and-execute-features/ Feature Progress
45. All hands meeting • GOAL - keep company in sync • every Monday • require for everybody • share company CORE metrics • mention any HEALTH metrics weirdness • project status updates and demos
46. Mission oriented meetings • avoid status updates, use Slack for this • before meeting - publish the agenda • agenda is items to discuss/decide • follow the agenda • after meeting list action items with responsible party
48. Slack Channels - weekly-updates - changelog - feedback - emergency-room - virtual-coffee - project-planing - project-[...] - [team] - engineering-wip - auto-[...]
49. Project Iteration Delivery Retro
54. O Feature switches
55. OFF ON User O Feature switches Check
57. 1 week 2 week 3 week ...
58. 1 week 2 week 3 week ... developer
59. 1 week 2 week 3 week ... developer beta
60. 1 week 2 week 3 week ... developer beta admin
61. 1 week 2 week 3 week ... developer beta admin everybody
62. Project Iteration Delivery Retro
63. Retrospective • did we achieve our goal? • what did we learn? • how should we improve?
65. Stories
66. Why stories matter?
67. Why stories matter? • motivation
68. Why stories matter? • motivation • cautionary tale
69. Why stories matter? • motivation • cautionary tale • shape culture
70. Why stories matter? • motivation • cautionary tale • shape culture • ... fun P
71. Document your history
72. Document your history
73. Document your history • team photos of key events
74. Document your history • team photos of key events • every month gather product screenshots
75. Document your history • team photos of key events • every month gather product screenshots • keep list of cool stories to share
76. Listen to your community
80. Build in the open
85. Test before build
89. Don't build until needed
92. Learn from your mistakes
 (no blame culture)
95. B Q Tuesday → Thursday Q