Easy everything in Product Strategy, page 2
What technical steps would you take to investigate a user's workflow frustration?
Tests if you can turn qualitative user pain into structured technical investigation. Strong answer: reproduce the exact workflow, then inspect logs and traces for errors or latency spikes, and segment by the user's environment.
How do user personas and stories inform technical design and edge cases?
Tests if you translate product requirements into technical constraints and failure modes. Strong answers map persona pain points to architecture, derive unhappy paths from preconditions, and validate edge cases through vertical slices.
How would you estimate user base for a new feature before coding?
Sizing an opportunity with proxy data before coding. A strong answer defines the behavioral profile, then triangulates internal segments, competitor analogs, and market data to bound the estimate with stated assumptions.
What are the risks of a roadmap without product strategy?
Risks include building wrong things fast, orphaned features, and tradeoff paralysis.
Stakeholder Communication Plan: Who Gets Told What, and When
A stakeholder communication plan is a roadmap for who needs to know what, when, and how. It's used to keep executives, dependent teams, and users aligned on project progress. The biggest footgun is a one-size-fits-all approach; tailor updates to each group.
DevRel: Building For and With Developers
DevRel is the bridge between a company and the developers using its tools, treating them as partners, not just customers. You see it in API docs, tutorials, and community forums. The footgun is treating it as just marketing, not a feedback loop to improve the.
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.
Platform Business Model: Connecting, Not Owning
A platform business connects groups (like buyers and sellers) instead of making its own products. It's a marketplace, not a store. This model powers ride-sharing apps and app stores.
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.
BCG Growth-Share Matrix: A Map for Your Product Portfolio
The BCG Matrix plots products on a 2x2 grid of market growth vs. market share to decide where to invest. It's used to categorize products as Stars, Cash Cows, Question Marks, or Dogs. The footgun is treating it as a static, predictive tool.
Launch Readiness Checklist: Your Launch's Single Source of Truth
A launch checklist is a flight plan, not just a to-do list, coordinating every team from engineering to sales. It ensures marketing, sales, and support are aligned for a release.
Ideal Customer Profile (ICP): Stop Selling to Everyone
An Ideal Customer Profile (ICP) is a data-driven portrait of the perfect customer for your business. It helps focus marketing and sales on high-value leads, reducing acquisition costs.
Scope Creep: When 'Just One More Thing' Derails a Project
Scope creep is the uncontrolled growth of a project's requirements after it starts. It shows up as 'small tweaks' that balloon into major features, delaying schedules and increasing costs. The footgun is trying to prevent it entirely instead of managing it.
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.
Value vs. Effort Matrix: Prioritize What to Build Next
A Value vs. Effort matrix is a 2x2 grid for deciding what to build, plotting features by their potential value against implementation complexity. Product teams use it to prioritize roadmaps and justify resource allocation.
The Eisenhower Matrix: Urgent vs. Important
The Eisenhower Matrix sorts tasks by urgency and importance, not just deadlines. Use it for daily or weekly planning to focus on what truly moves the needle. The biggest footgun is letting 'urgent but not important' tasks dictate your day.
Product Roadmap vs. Backlog: Strategy vs. Tactics
A roadmap is your strategic travel plan showing major destinations (product goals), while the backlog is the turn-by-turn navigation for the current leg of the journey (development tasks). The footgun is cluttering the roadmap with backlog details.
Vanity vs. Actionable Metrics: Measure What Matters
Vanity metrics look impressive but don't inform decisions (e.g., total downloads). Actionable metrics tie to business goals and guide your next move (e.g., conversion rate). This helps product teams focus on real growth, not just impressive-looking charts.
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.
Cost-Plus Pricing: Set Price Based on Cost, Not Value
Cost-plus pricing sets a product's price by adding a fixed percentage markup to its unit cost. It's common in government contracts where costs are clear. The footgun is that it ignores what customers are willing to pay, leaving money on the table.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles