Strategy
81 bites tagged Strategy — interview questions with model answers, and 60-second explainers.
Two-Sided Markets: Playing Matchmaker for Value
A two-sided market plays matchmaker, connecting two distinct groups like buyers and sellers. It creates value by enabling their interaction, growing stronger as more users from each side join.
Product Sunsetting: Retiring Products Gracefully
Product sunsetting is the managed process of retiring a product to free up resources. It's used when a product is no longer profitable or strategically relevant. The biggest footgun is a sudden shutdown without a clear migration path, which alienates users.
ICE Scoring: Prioritize Features with a Quick Gut Check
ICE scoring is a gut-check for prioritizing features by multiplying Impact, Confidence, and Ease. It helps teams rapidly sort experiments or backlog items. The main footgun is its bias towards easy wins, potentially ignoring high-effort strategic projects.
The 80/20 Rule: Find the Vital Few
The 80/20 rule states that most outcomes (80%) come from a few causes (20%). It's used to find high-impact work, like fixing the few bugs causing most crashes. The footgun is treating 80/20 as a precise law instead of a general heuristic.
Roadmap Commitment Levels: Now, Next, Later
Agile roadmaps replace fixed timelines with commitment levels: 'Now' (in progress), 'Next' (planned), and 'Later' (potential ideas). This structure communicates decreasing certainty, allowing teams to adapt without breaking promises.
Outcome-Based Roadmaps: Solve Problems, Not Ship Features
An outcome-based roadmap frames work around problems to solve, not a checklist of features to build. It gives teams autonomy to find the best solution for goals like increasing user engagement or improving conversion.
Thematic Roadmaps: Focus on 'Why,' Not 'What'
A thematic roadmap organizes work around strategic goals ("themes") like "Improve User Onboarding," not just a feature list. It's used to align teams on high-level objectives and persuade executives. The footgun is mistaking a feature list for a strategy.
Counter Metrics: Guardrails for Your Goals
Counter metrics are the guardrails for your primary goal, preventing you from optimizing one number at the expense of user experience. If you increase ad impressions for revenue, track user retention to ensure you aren't just driving users away with spam.
Positioning Statement: Your Product's Internal Compass
A positioning statement is an internal compass, not a public slogan. It defines your product's unique place in the market for a specific customer, guiding all marketing and product decisions.
The Hedgehog Concept: Know Your One Big Thing
The Hedgehog Concept trades scattered efforts for focused strategy. It's the intersection of what you're passionate about, what you can be the best at, and what drives your economic engine. Use it for long-term strategic clarity.
Your Product's North Star: The Mission Statement
A product mission is your team's compass: a short statement of why the product exists, who it serves, and its core goal. It aligns stakeholders and guides development. The footgun is confusing it with a vision; a mission is what you do now, not a.
VRIO Framework: Finding Your Competitive Advantage
The VRIO framework is a checklist to see if a resource is a true competitive advantage. Use it to analyze internal assets like patents or expert teams. The footgun is stopping at "Valuable"—a true moat must also be Rare, Inimitable, and Organized.
Switching Costs: The Moat Around Your Product
Switching costs are the gravity holding users to a product—the sum of all financial, mental, and effort-based pain of leaving. This is why bundled services are sticky. The footgun is creating costs that feel like traps, which destroys long-term trust.
Problem Statement Framing: Define the 'Why' Before the 'What'
Don't just solve the problem, solve the *right* one. Problem framing forces you to deeply understand a user's need before building. It's the first step in product development, ensuring teams don't build something nobody wants.
Qualitative vs. Quantitative: The 'Why' and the 'How Many'
Quantitative research counts and measures ("how many?"), while qualitative research explores and understands ("why?"). Use quantitative for A/B tests to get statistical proof, and qualitative for user interviews to uncover motivations.
The Ansoff Matrix: Four Paths to Business Growth
The Ansoff Matrix maps growth strategy onto a 2x2 grid of products (new vs. existing) and markets (new vs. existing). It helps you decide whether to sell more of what you have or invent something new. The footgun is underestimating the risk of new ventures.
User Personas: Build for a 'Who', Not a 'What'
Personas are fictional character sheets for your ideal users, grounding product decisions in human needs, not just features. They guide choices from UI to marketing by asking "What would our user do?".
PESTLE Analysis: Mapping Your Business's External World
PESTLE analysis is a strategic checklist for scanning the external world for threats and opportunities you can't control but must react to. It's used for market entry strategy and product development.
Porter's Five Forces: Is This Industry Worth Entering?
Porter's Five Forces is a framework for analyzing an industry's profit potential. It assesses the competitive environment to determine if a market is attractive or if its structure will drive all profits down to a baseline, like in pure competition.
Product Roadmap: A Strategic Plan, Not a Feature List
A product roadmap is a strategic guide, not a rigid timeline, showing how work achieves long-term goals. It's used to align engineering, product, and leadership on priorities.
Strategy vs. Tactics: The Map vs. The Directions
Strategy is your destination and why you're going; tactics are the turn-by-turn directions. A product strategy defines the long-term goal, like 'capture the enterprise market,' while tactics are the specific feature launches to get there.
What a Head of Growth Actually Does
A Head of Growth is a systems architect for revenue, deciding where to place strategic bets, not just a campaign manager. They align product, engineering, and marketing around shared metrics and build the experimentation engine.
Product-Led Growth (PLG): Let Your Product Sell Itself
Product-Led Growth (PLG) makes the product the primary engine for acquiring and converting users. It relies on a mix of free features, virality, and a smooth upgrade path to paying tiers, letting users experience value before they buy.
Managing Growth with an Experiment Backlog
An experiment backlog is a prioritized list of testable ideas that turns strategy into action. Agile teams use it to manage projects, using business intelligence to measure performance and ensure ideas deliver value. The footgun is a lack of governance.
Get Strategy bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.