STP Framework: Segmentation, Targeting, Positioning Strategy

The STP framework, segmentation, targeting, positioning, helps when a consulting case asks which customers a client should pursue and how the client should win them. Segmentation breaks the market into decision-relevant groups. Targeting chooses the group with the strongest strategic logic. Positioning explains why that group should choose the offer over realistic alternatives. In a case interview, STP is useful only when customer choice matters: product launch, stalled growth, market entry, brand repositioning, adoption, or channel strategy. It is weak for pure cost reduction, operational bottlenecks, capacity expansion, or pricing math where customer behavior is not the core decision. Treat STP as a way to build a custom issue tree, not as a script to recite. Bain describes case interviews as a way to see how candidates work through problems, so your STP answer needs to sound like business reasoning under pressure.

For the broader case family, use the marketing case interview guide alongside this STP walkthrough.

What the STP framework actually solves in a case interview

STP solves customer choice. It is useful when the client is asking who to serve, what need to solve, and how to make the offer credible against alternatives. That is why it fits launch, growth, market-entry, repositioning, adoption, channel, and customer strategy cases. It is also why it should sit inside the broader problem, not replace the whole case.

The American Marketing Association frames marketing around creating, communicating, delivering, and exchanging value, which is a useful reminder: STP is not just promotion language. It is a strategy tool for deciding where value should be aimed and why that value should be accepted by a specific customer group.

The mistake is treating STP like a universal answer. A strong candidate starts from the client decision, then uses STP only if customer differences change the recommendation.

Segmentation: build useful customer groups, not demographic trivia

Segmentation is the branch-building step. OpenStax describes market segmentation as dividing a target market into smaller groups with common needs that are expected to respond similarly to marketing action. In a case, that means your segments should predict different behavior, economics, channels, or willingness to switch.

Weak segmentation sounds like: teenagers, adults, seniors. That might be useful if age changes the need, buyer role, channel, or price sensitivity. Without that logic, it is trivia. Strong segmentation sounds like: on-the-go breakfast, office snacking, post-workout recovery, and family pantry refill occasions. Those groups buy for different reasons, through different channels, and with different constraints.

A practical segmentation branch can use need state, occasion, behavior, channel, willingness to pay, usage intensity, buyer role, pain point, or switching friction. For B2B software, company size alone is often weak. Buyer pain, workflow urgency, budget owner, and implementation friction are usually more decision-relevant.

Ask for data that would change the recommendation: segment size, growth, margin, purchase frequency, pain intensity, channel access, competitor strength, and switching barriers. If your branches overlap badly or miss a major customer group, revisit the case structure vs case framework distinction before you keep going.

Targeting: choose the segment with the strongest strategic logic

Targeting is the decision step. Once you have plausible segments, compare them on attractiveness and ability to win. OpenStax's effective segmentation criteria are useful here: a segment should be accessible, differentiable, actionable, measurable, and substantial. In a case interview, translate that into practical language: can we reach them, are they meaningfully different, can we serve them, can we size them, and are they worth the focus?

Targeting also forces buyer versus user clarity. OpenStax's target-market discussion distinguishes the market a company targets from the people who may actually buy or influence the purchase. That matters in cases involving parents buying for children, procurement buying for end users, or executives approving software used by frontline teams.

Candidate wording: I would prioritize the segment where the need is urgent, the route to market is reachable, and the client has a credible right to win.

If you want to test whether this STP structure works under pressure, Road to Offer helps by forcing you to turn a vague marketing prompt into segment branches, target criteria, and positioning logic you can say out loud.

Positioning: turn the target choice into a value proposition

Positioning is the final STP step: define how the selected customer should think and feel about the offer. OpenStax's product positioning section places positioning after segmentation and targeting, because the message only makes sense once the target is clear.

In a case interview, positioning is not slogan writing. It is strategic clarity about why the target would switch, buy, or stay. A case-ready positioning statement should include target customer, situation, unmet need, alternative, benefit, proof point, and tradeoff.

Use this template in prose: for target customer, in situation, the offer solves need better than alternative because proof point.

For the premium snack example, a completed version could be: for busy office workers who need convenient afternoon energy, the product offers a cleaner and more satisfying snack than vending-machine options because it combines portability, taste, and credible better-for-you ingredients.

That positioning should shape product features, pricing logic, channel, message, and sales motion. If the position is premium office energy, the client may need smaller desk-friendly packs, workplace sampling, a subscription or office manager channel, and proof that the product is satisfying enough to replace default snacks.

Worked example: premium snack brand launch

Assume the client is a premium snack brand considering a new product. The question is whether to launch, which customers to focus on, and how to position the offer. STP fits because the answer depends on customer need and willingness to choose the product over alternatives.

Start with segmentation by occasion and need:

I would target office snackers first. The need is frequent, the product can justify a premium if it solves taste and convenience, and the brand has a credible right to win if it can access workplaces or urban retail near offices. I would not start with post-workout recovery unless the product has strong functional proof, because that segment punishes weak claims.

Spoken recommendation: I would launch with office snackers as the initial target, position the product as a convenient premium snack for workday energy, and validate channel access plus repeat purchase before expanding to adjacent occasions.

After writing your own version, use Road to Offer's Case interview structure drill to pressure-test whether your STP branches are MECE enough, decision-relevant, and sayable under interview pressure.

Questions and checklist before you use STP

Before you force STP into a case, ask what customer decision the client is trying to influence. If there is no meaningful customer choice, STP is probably not your first structure. If there is, ask which segments behave differently, which segment is reachable, what would make them switch, and what proof would validate the target choice.

Use this checklist:

• Segment differences change the recommendation.
• Target choice is explicit, not implied.
• Positioning explains switching behavior, not just brand language.
• Economics and execution are still included.
• Competitor response is not ignored.
• Buyer and user roles are clear when they differ.

MECE thinking still applies to segmentation. If office workers, commuters, and busy professionals are all separate branches, you may be overlapping the same customer. Use the MECE framework as a pressure test: branches should be distinct enough to guide analysis and collectively useful enough to cover the decision.

Practice drill: turn STP into a case-ready structure

STP improves when you practice it as spoken problem solving. Start by building the first-layer issue tree from a marketing prompt. Then pressure-test whether each branch answers the client decision or just names a category. If the structure is too generic, rebuild it around need, behavior, channel, buyer role, or switching friction.

Next, generate segment and positioning options with the Brainstorming drill. Do not stop at the first obvious customer group. Push for alternatives that create different economics or go-to-market choices.

Then use the Synthesis drill to turn the target decision into a recommendation: choose the segment, explain why it wins, name the risks, and state what you would test next. If you are unsure which skill is weak, use the Free drill picker to route yourself to the right practice path.

Road to Offer lets you move from isolated STP reps into free case practice when you are ready. That matters because the real interview will not pause after segmentation. Your structure still has to survive exhibits, math, tradeoffs, and final recommendation pressure.

Once your segment logic is sayable, the next test is whether it survives a full case from prompt to recommendation.

Sources and Further Reading (checked 2026-06-02)

• OpenStax - Market Segmentation and Consumer Markets
• OpenStax - Essential Factors in Effective Market Segmentation
• OpenStax - Selecting Target Markets
• OpenStax - Product Positioning
• Bain & Company - Our Hiring Process
• American Marketing Association - What is Marketing? - The Definition of Marketing