7. Promotion season. It's been 8 months since the kickoff and promotions are happening. The PM is promoted to Sr PM, and one of the engineers to Staff for having identified and executed on a strategic business opportunity, and shipping it to production in such a short time.
-
Show this thread
-
8. Iterating. The product rolls out in other countries, and initial growth looks good. The next 6 months the team keeps adding more features, and shipping these to smaller cohorts. There seems to be lots of churn after 2 months. But it's a bit too early to tell, to be fair.
1 reply 3 retweets 59 likesShow this thread -
9. More funding. The PM strikes a deal with Popular Company Product to integrate their chat to their the main screen. User signups surge and the growth graph is a hockeystick. The (Sr) PM asks for more funding: another 20 engineers. Approved for 15. The team grows. More hiring!
2 replies 3 retweets 59 likesShow this thread -
10. More promotions. The other founding senior engineer is also promoted to Staff, as well as other engineers. The EM is promoted to Sr EM for growing a team from zero to 20 engineers, and two managers in such a short time.
1 reply 3 retweets 66 likesShow this thread -
11. Growth slowing. That two-month churn is surfacing, and it's bad. The hockestick is flattening. It's unclear why users are churning. Well, that's not entirely true: there's dozens of reasons, and each one is a major project to fix. Confusion with other products is also one.
1 reply 5 retweets 77 likesShow this thread -
12. Founding team members leaving. The founding PM realizes a project slowing down won't help them get to Director. Best to leave when things are still growing. They internally transfer to head up three teams taking on a directly threatening competitor instead.
1 reply 6 retweets 90 likesShow this thread -
13. More team members leaving. Growth is flat, and there is no clear fix for the problem. Three of the engineers and a manager follows the PM to the new teams. A few other engineers transfer to other teams building interesting things.
1 reply 4 retweets 69 likesShow this thread -
14. A struggling team. Growth is turning negative. The team is not given additional headcount the next planning cycle. There are rumors of no backfills, unless the metrics improve. The EM and PM both transfer to another team as well. The new EM and PM are now both new hires.
1 reply 4 retweets 67 likesShow this thread -
15. The speculation. The org all-hands no longer mentions the product. Internal transfers avoid the team. People are talking: why did the product fail? The area is strategic to the company. The start was promising. What went wrong? Was it the people? Execution? The competition?
1 reply 5 retweets 67 likesShow this thread -
Gergely Orosz Retweeted Gergely Orosz
16. The realization. A PM thinks they understand the cause. The market shifted. Positioning was poor. The area is still strategic. Could this be... the opportunity they've been looking for? They take a deep breath and decide it is. They know what to do:https://twitter.com/GergelyOrosz/status/1442215732545216518 …
Gergely Orosz added,
Gergely Orosz @GergelyOroszWhen you ask "Why did Company build 7 of the same products that all failed?", it always starts with the current solution struggling. This is an opportunity. Not to fix - which doesn't get you promoted - but to start anew. An all too real story about Promotion Driven Development:Show this thread13 replies 10 retweets 345 likesShow this thread
The thread loop here is a very tasteful touch!
-
-
Replying to @Pinboard @GergelyOrosz
Exactly the same thread applies to US wars as soon as you realize that promotion in the US army is driven largely by quantity of combat experience.
0 replies 0 retweets 3 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.