|
|
|
|
|
by hintymad
1217 days ago
|
|
I actually don't believe 5-year plan would work. Great products are built, not planned. A plan to keep management patient for 5 years, though, will work better. In AWS, a newly launched service will not seek profitability but user growth for at least the first two years, if not three. And then the GM of the service needs to pursue profitability and margin, while keeping user growth healthy. That said, product features are planned on a 6-month basis, and GMs have have moving target of profitability as market conditions often change. |
|
Google tends to suffer from the worst of both worlds: an over-abundance of 5-year plans that do not offer sufficient interim value to justify their continued work.
Part of this is bad projections - Google projects are often highly-ambitious multi-year affairs with some interim checkpoints like growth rate, but those numbers are usually poorly estimated, poorly sourced, wildly overly optimistic, and don't actually pan out. So when the team inevitably whiffs the checkpoints by a wide margin entire products get shut down. This is at least one of the larger causes of the leadership churn I described above.
But yes, if your idea is that you can have a 5-year budget to go do [insert big ambitious thing] and management won't cry about it, that's a fantasy.
That said, the opposite is also not a great way to pursue a product - which mostly rests on the theory that pursuing near-term improvements repeatedly naturally wins.
In reality you want a mixture of long-term strategy with short-term tactics. Product teams that are too heavily in one direction fail for it.