Product Management: Vision & Strategy Flashcards
MVP
Minimum Viable Product. An early version of your product with minimal features that you can take to market in order to get feedback
KPI
Key Performance Indicator. KPIs can be used to measure the success of the products.
Revenue stream
A source of revenue for a company, mostly commonly transaction based or recurring events
Subscription
A type of revenue model that generates recurring revenue. Users pay a fee on an ongoing basis in exchange for access to your product.
Licensing
A revenue model that generates transaction based revenue. Users purchase a one time license to use your software on an ongoing basis
Pay per use
A revenue model that generates transaction based revenue. Users pay a fee every time they use your product.
Freemium
A revenue model that gives a small part of your product away at no cost to users with the ultimate goal of converting users to paid users in order to gain access to the full product.
CPC
Cost per click.
CPM
Cost per 1000 impressions.
CTR
Click through rate.
What is Vision?
What your product looks like in its final state
Describes the essence of the product
What your product does and why it matters to users
Can be summarized in a sentence or two
Parts of a Vision statement
Vision needs to tell a story about:
What you’re building
Who it’s for
Why it matters
Your vision should be …
Inspiring Ambitious Easy to explain Something the team believes in Something you evolve over time Something you share out frequently
The importance of having a vision statement
To understand the importance of having a vision statement, consider how difficult it would be to develop a strategically sound product without one. How would that product team know where to focus its resources, which features to prioritize, which markets to target? On what strategic basis would they make decisions and set priorities?
When should you craft the vision statement
Creating a vision allows your team to take a top-down approach to your product’s development. In other words, you begin with a high-level vision statement, then translate that vision into a strategic guide and action plan—the product roadmap. Then, you can translate that roadmap’s strategic overview into a tactical development plan.
Drafting a vision statement should be your team’s first step in starting any new product’s journey—and it always should come before you begin working on the product roadmap.
How can a product vision statement improve strategic decision-making?
Another reason a product vision can aid in your development is that it can help you more quickly and easily identify initiatives worth pursuing.
Think of your product vision statement as a compass that you can consult whenever your team is faced with conflicting priorities or lack of direction.