Table of Contents
🌏 中文版
Today's Topic
The Strategy & Execution round isn't testing whether you can recite the five forces in Porter's Five Forces — it's testing whether, given an ambiguous prompt about a market that already has strong incumbents, you can land on a concrete call about whether to fight and which specific company asset would turn into a moat. Most candidates stall out on vague conclusions like "the market is big and we have brand advantage," and the interviewer's next question is always "so why do you actually win."
Today we use Five Forces to first decide whether the market is even worth entering and where the competitive intensity comes from, then use TAM-SAM-SOM to cut the market down to something you could validate within the first year — so a strategy answer stops being a story and starts having real market boundaries and trade-offs behind it.
Core Frameworks
Porter's Five Forces: deciding whether this fight is worth having
Before entering a new market, use Five Forces to judge the competitive structure — not just whether the market is "big enough":
| Force | Question to ask | What it means for the PM decision |
|---|---|---|
| Rivalry among existing competitors | How many players, and what do they compete on (price, features, ecosystem)? | Higher intensity means you need a clear differentiator — you can't win a feature-for-feature war of attrition |
| Threat of new entrants | How high is the barrier to entry, and are you the new entrant here? | If you're the late mover, be ready to answer "why now" and "why us" specifically |
| Threat of substitutes | What would users do instead if this category didn't exist? | Low substitute threat lowers the cost of educating the market, but can also mean the underlying pain isn't sharp enough |
| Supplier bargaining power | What upstream dependencies does this product rely on (cloud services, data, platform owners)? | Higher dependency means your moat is more exposed to being squeezed by the upstream party |
| Buyer bargaining power | How costly is it for users to switch to a competitor's product? | Determines whether the moat should be built around "retaining existing users" or "winning new ones" |
Common mistake: treating Five Forces as a fill-in-the-blank table to recite rather than a tool to answer one concrete question — is this fight worth having. What the interviewer wants is the conclusion, not all five forces read out loud.
TAM-SAM-SOM: cutting the market down to an executable first step
A big market doesn't mean you can win it now — split it into three layers to know exactly which slice to go after first:
| Layer | Definition | What it means for the PM decision |
|---|---|---|
| TAM (Total Addressable Market) | The theoretical full market this category could reach | Useful for convincing the company "this direction is worth investing in," but not something you can set a quarterly target against directly |
| SAM (Serviceable Addressable Market) | The portion actually reachable given the company's existing channels, technology, and positioning | Determines which segment to go after, usually excluding segments where you have no real advantage |
| SOM (Serviceable Obtainable Market) | What's realistically winnable within a defined time frame (usually a year) | This is the number the interviewer actually wants — concrete, time-boxed, and something you can reverse into a success metric |
When the interviewer follows up with "how would you actually enter this market," the answer should land at the SOM layer — naming the specific first segment to target, not repeating the sweeping TAM number.
Today's Practice Question
The Question
"The company builds a collaboration tool whose core users are designers. The market already has one or two well-established whiteboard-collaboration products. How would you decide whether to enter this market? If you decide to go for it, which piece would you target first?"
(Question type: strategy case study; self-authored based on Figma's real 2021 launch of FigJam, going head-to-head with whiteboard-collaboration leader Miro)
How to Break It Down
- Clarify the scope: First confirm what "entering" means — a standalone new product, or a new module inside the existing product? What's the decision time frame? Which company goal should this align to (retaining existing customers, or opening up a new customer segment)?
- Use Five Forces to judge whether it's worth fighting: Rivalry from an incumbent like Miro is high, built on template libraries and enterprise governance. But flip the buyer-bargaining-power lens: if the company already has a base of designer users, the incremental switching cost for those users is actually low, because the decision isn't "should I abandon my current whiteboard tool" — it's "should I turn on one more feature inside an account I already have."
- Use TAM-SAM-SOM to converge on the first step: TAM is the entire visual-collaboration market; SAM narrows to "teams already using the company's existing design tool," since that's the only segment where the company has a real edge; SOM is "the share of existing paying accounts that adopt the new feature within a year" — specific enough to reverse-engineer a feature priority list from.
- Decide on the differentiator: Don't chase the incumbent's template library or enterprise governance feature-for-feature. Instead lead with "seamless integration with the design files you already have" — pulling design mockups directly into the whiteboard during a discussion, something the incumbent can't do because it doesn't have the company's existing designer user base or multiplayer-editing tech asset. The moat sits on top of the existing collaboration tech and user network, not a rebuilt standalone product.
- Define success and risk: The primary metric is "share of existing paying accounts that activate and keep using the new feature." The risk is diverting engineering resources from the core product — name a stop-loss: if penetration doesn't clear a threshold within a year, scale back scope or pause the investment.
Sample Answer (say it like this in the interview)
Clarifying the scope: "I'd want to confirm scope first — I'll assume 'entering' here means a new module inside the existing account system, not a from-scratch standalone product, over a one-year time frame. I'd also want to ask: is this decision meant to align to retaining existing customers against churn, or opening up a segment we haven't reached before? I'll assume the former for now, since the incumbent is already mature and going straight after new customers would carry a much higher marginal cost."
Whether it's worth it, and where to enter: "Looking at Five Forces, rivalry in this market is high — the incumbent is entrenched on template libraries and enterprise governance, and we can't win a straight feature-for-feature fight. But I'd flip the buyer-bargaining-power lens: we already have a base of designers using our core product, and turning on a whiteboard feature inside an account they already have is a much lower switching cost than picking a brand-new tool from scratch. So I'd narrow SAM to 'teams that are already our paying customers,' and set SOM at 'what share of that base activates and keeps using the new feature within a year' — rather than going after the incumbent's entire TAM in the whiteboard market."
Differentiation and risk: "The differentiator wouldn't be copying the incumbent's template library — it'd be leading with 'seamless integration with the design files you already have,' pulling mockups directly into the whiteboard during a meeting, something the incumbent can't replicate because it doesn't have our core product's asset. The moat sits on our existing user network and multiplayer-editing tech, not a rebuilt standalone product. The risk is this pulls engineering resources away from the core product, so I'd set a stop-loss: if penetration among existing customers doesn't clear a threshold after a year, we scale back scope instead of doubling down to match the incumbent's feature breadth."
Self-Check
Use this table to check whether your answer hit the key points:
| Checklist item | Covered? |
|---|---|
| Used clarifying questions to narrow "how to enter," "time frame," and "alignment goal" | |
| Used Five Forces to reach a concrete conclusion (worth it or not, where the intensity comes from), not just reciting the framework | |
| Used TAM-SAM-SOM to converge down to a concrete SOM number, not stopping at TAM | |
| Named clearly which existing company asset the moat is built on, not just a slogan | |
| Covered both a success metric and a risk stop-loss, not just "we'll win" | |
| Bonus: mentioned how to scale back or exit if the entry doesn't work out |
Today's Case Study
Figma: entering the whiteboard-collaboration market head-on against Miro using its existing designer network
Figma launched FigJam in 2021, entering a whiteboard-collaboration market where Miro was already the entrenched leader, with a far more mature template library and enterprise governance feature set. Instead of trying to match Miro template-for-template or feature-for-feature, FigJam led with seamless integration into Figma's existing design files — teams could pull mockups directly into a FigJam board during a discussion, something a whiteboard-only product like Miro couldn't replicate, because it didn't have Figma's existing designer user base or multiplayer-editing tech asset. FigJam established itself in the specific niche of "design-adjacent cross-functional collaboration" rather than trying to capture the entire whiteboard-collaboration market in one move.
Interview connection: This case is the best demonstration of "a late entrant skips feature parity and instead weaponizes an existing asset as the differentiator" — use it directly to answer "how would you decide whether to enter a market with strong incumbents already" or "give an example of a company using an existing advantage to break into a new market." The point isn't memorizing the name FigJam — it's articulating how it narrowed SAM down to the one segment where it actually had an edge, instead of going after the incumbent's entire TAM.
Further Reading
- Google Product Strategy Interview Guide — Aced's (formerly Exponent's) full breakdown of Google's product strategy interview process, including how the ambiguous case-study round works and its follow-up patterns
- Netflix Product Manager (PM) Interview Guide — Netflix's PM cross-functional stakeholder round, showing how strategy questions often pair with stakeholder-management assessment
- 6 Product Management Trends in 2026: The PM Role Is Splitting — Userpilot's rundown of how the PM role is splitting in 2026, with Productboard's CPO Survey data on the growing importance of strategy skills
References
- Google Product Strategy Interview Guide — source for the case-study format described in "Today's Topic" and "Today's Practice Question"
- FigJam vs Miro: Which Whiteboard Tool Wins in 2026? — source for FigJam's 2021 launch and its positioning difference from Miro in "Today's Case Study"
- Breaking the Canvas: Figma's FigJam and the Evolution of Its Collaborative Design Ecosystem — source for the analysis of FigJam as a late mover differentiating through integration with the existing Figma ecosystem, used in "Today's Case Study"
Loading...