How long does it take to create a product vision?
2 Answers
Meta Product Leadership - Ads, Commerce & AI | Formerly Stripe, Flipkart, Yahoo • June 7
- For any Product, the hierarcy, in terms of immediate to long-term is Execute -> Features -> Roadmap -> Strategy -> Vision
- The focus for any product team should be to execute & launch and then working on the features & building on the roadmap from a bottoms-up perspective. They should also embark on a top-down appraoch of understanding the market landscape, the user problems they can solve profitably and setting the vision. The intersection of these approaches can take anywhere from a few weeks to a few months to a few years and depends on the stage of the firm, the product, the type of company and the lifestage
- For start-ups, Vision trumpes everything else and would be required before they raise capital, attract talent or are able to build. Tesla is an excellent example here.
- For large firms, product in market thats generating revenue trumps everything else and they have the chance to stumble upon a good strategy or vision if they keep iterating. But, this isn't a given, most firms stumble & fall rather than pick themselves up & iterate. Chevy has the vision laid out for them by Tesla but they haven't been able to take the Bolt to where Tesla is.
- For other firms, the answer lies in the middle of the specturm. PoleStar & Riviian are able to ride on Tesla's coat-tails, Toyota continue to follow their incremental approach with the Prius but it feels like an opporunity lost, BMW & Merc have launched incredible electic cars that feel like the future, etc
942 Views
Oracle Cloud Infrastructure Director of Product Management • November 1
It can take anywhere from a few goals to multiple weeks. In addition to the thought that goes into it, its important to align stakeholders to your vision and this can add time to this task.
383 Views
Related Questions
When pivoting to a new product vision, what next steps would you take?In what tangible ways should your product vision dictate the day to day decisions your product development team makes?What questions do you ask yourself when building a product vision?What do product teams get wrong when defining their product vision?What is your process of setting a vision when you join a new company?How does the approach vary between a software product and a hybrid product (e.g. a router with embedded sftware)?