> 2. at some point Product A will reach a steady state (in some utopic future, but let's pretend). i.e. Product A will hit a point where its excitement will taper off.
> 4. hire more people to work on Product B. Have it launch, big growth!
Why is the answer "hire more people to work on Product B" and not "Move people from A to B and shrink the product A team to focus on bug fixes and security fixes"
I would think that the desire to hire a whole new team rather than move staff is what keeps Zawinski's Law [0] around.
It's not mutually exclusive. But it depends on Product B, and oftentimes these kinds of tech companies want to grow in completely different areas.
Take Amazon, for example: they have great engineers, but probably not too many game developers (or those interested in moving from current SWE positions to the game division). And they almost certainly had no artists on board, among other disciplines needed for a game. So when making Amazon Games they would have to mostly hire new staff. Not the best example given how they floundered for a decade, but I think that was a management issue over a talent issue.
> 4. hire more people to work on Product B. Have it launch, big growth!
Why is the answer "hire more people to work on Product B" and not "Move people from A to B and shrink the product A team to focus on bug fixes and security fixes"
I would think that the desire to hire a whole new team rather than move staff is what keeps Zawinski's Law [0] around.
[0] https://en.wikipedia.org/wiki/Jamie_Zawinski#Zawinski's_Law