Product
60 bites tagged Product — interview questions with model answers, and 60-second explainers.
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.
The HEART Framework for Measuring UX
The HEART framework provides a structure for measuring user experience on large-scale web applications. It helps teams define user-centered metrics to track progress towards goals and make data-driven decisions.
SMART Goals: From Vague Hopes to Actionable Plans
SMART goals turn fuzzy ambitions into concrete plans by forcing clarity. It's a checklist for ensuring a goal is Specific, Measurable, Assignable, Realistic, and Time-bound. Use it for project planning or performance reviews to create trackable progress.
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.
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.
Focus Groups: Understanding the 'Why' Behind User Reactions
A focus group is a guided conversation to uncover the 'why' behind user opinions, not just what they are. It's used to gauge reactions to new products or understand shared experiences.
Generative vs. Evaluative Research: Define Problems vs. Judge Solutions
Generative research defines problems by asking, "What should we build?" Evaluative research judges solutions by asking, "Did we build it right?" The footgun is using evaluative methods for discovery, which just optimizes a solution for a problem nobody has.
Contextual Inquiry: Watch Users in Their Habitat
Go to the user's environment to see what they *actually* do, not just what they say they do. It's used in early discovery to uncover unstated needs by observing real workflows. The footgun is 'helping' the user, which pollutes the observation.
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?".
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.
User Bucketing: The Engine of A/B Testing
User bucketing is a deterministic hash that assigns users to experiment groups. It ensures a user sees the same variation every time, which is critical for valid A/B tests. The main footgun is using an unstable user ID, which can re-bucket users and ruin your.
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.
The K-Factor: Measuring Your Product's Viral Growth
The Viral Coefficient (K-factor) measures how many new users each existing user generates. It's key for products with referrals or sharing. The common mistake is chasing K > 1; even K=0.5 is valuable, as it effectively halves your acquisition cost.
The Self-Serve Funnel: Let Your Product Do the Selling
A self-serve funnel lets users discover, try, and buy your product without talking to a human, making the product the main sales driver. It powers rapid growth for companies like Slack. The main footgun is poor onboarding; if users get stuck, they churn.
Freemium: Give Away the Basics, Sell the Upgrades
Freemium gives away a useful core product for free to attract a large audience, then sells premium features to a small subset of users. It's common in apps and games. The footgun is miscalibrating the free tier: make it too good and no one pays.
Customer Retention: Are Users Sticking Around?
Customer retention measures if users return to your product. It's often more valuable to keep an existing customer than acquire a new one. This is critical for any business relying on repeat engagement, from SaaS to e-commerce.
Onboarding Checklists: Guide Users to Their 'Aha' Moment
An onboarding checklist is a guided to-do list showing new users the key actions to find value. It bridges the gap between a first tour and independent use, increasing task completion by 20-30%.
Novelty and Learning Effects in A/B Testing
The novelty effect is a temporary metrics lift from curious users exploring a new feature. The learning effect is the opposite: a dip as users struggle with a change. Both can mislead A/B tests if you don't run them long enough to see the true.
The RICE Scoring Model: Prioritize with Data, Not Feelings
RICE is a formula—(Reach × Impact × Confidence) / Effort—for scoring competing features. It replaces gut feelings with a data-driven framework for prioritizing product roadmaps. The biggest footgun is treating the score as gospel, not a conversation starter.
Fogg Behavior Model: Why Users Act (or Don't)
The Fogg Behavior Model states a behavior only happens when Motivation, Ability, and a Prompt converge (B=MAP). Use it to diagnose why a feature fails or to design new ones. The footgun is blaming low motivation when the real issue is low ability.
User Activation: Engineering the 'Aha' Moment
User activation engineers the 'aha' moment when a new user first experiences your product's value. It's measured by a key action, like sending a message in Slack, that predicts retention.
Get Product bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.