In a typical first-round slate of eight, I write "framework recital" on two or three score sheets. Same labels, same tour, no bet. The 3Cs — company, customer, competitor — is the cleanest example: candidates treat a 1982 strategic idea as a checklist and burn the clock.
The thesis is simple. Interviewers score how you use a structure, not whether you can name it. Kenichi Ohmae built the 3Cs as an integrated triangle, not three equal speeches. After this piece you will know the origin, the exact failure mode in a live case, and one full path where the candidate adapts the lens instead of announcing it.
Where the 3Cs actually came from
The model is not MBA folklore. Kenichi Ohmae, then a McKinsey partner in Tokyo, published the strategic triangle in The Mind of the Strategist (McGraw-Hill, 1982) and in a same-year article in the European Management Journal (Vol. 1, Issue 1, pp. 38–48). He framed three linked vertices — corporation, customers, competitors — and argued that durable strategy sits at their intersection, not in any single corner.
That history matters in the room for one reason: Ohmae's point was integration. A customer insight that your cost structure cannot deliver is not a strategy. A cost edge the buyer does not value is not a strategy. A competitor map with no implication for your next move is a slide deck. Prep sites that teach "cover all three Cs" invert the original idea.
This post stays on that triangle. It is not the 4Cs (which adds cost or channel, depending on which school you read), not the 4Ps (product, price, place, promotion), and not Ansoff (market vs. product growth). Those answer different prompts. Force-fitting them into a "can we win here?" question is how candidates sound generic.
What the score sheet actually rewards
Firms do not publish a secret 3Cs rubric. They do publish what problem-solving interviews test. McKinsey's interviewing page says interviewers want to see how you structure ambiguous challenges, identify important issues, deal with facts and data, form conclusions, and articulate thinking in a fast discussion. BCG's case-prep guidance is blunt in the same direction: structure the approach, prioritize what matters, calculate cleanly, and reason out loud — there is not always one right answer.
None of that language says "name Ohmae." My estimate from scoring rooms: naming a branded framework out loud almost never earns points and often costs them, because the interviewer hears a template instead of a decision. The points sit on three behaviors:
| What you do | What the sheet hears | Typical outcome |
|---|---|---|
| Name "3Cs" and tour each bucket | Recital | Flat structure score |
| Pick one vertex as the first test, with a kill criterion | Hypothesis-driven | Structure marks start moving |
| Adapt the branches to the prompt's metric | Tool use | Structure plus judgment |
Ned's rule. A framework earns points only when it changes what you ask for next. If the next question would be identical without the framework, you are decorating, not structuring.
Where the 3Cs fails in a live case
I will be precise. The 3Cs fails in two ways: wrong tool for the prompt, and right tool used as a tour.
Wrong tool. Profit just fell $11m year over year and you do not yet know whether volume, price, mix, or cost moved. Starting with "company, customer, competitor" will not isolate the driver. You need a profitability bridge first. Same for a pure ops prompt (cycle time, scrap, utilization) or a portfolio funding choice across four businesses. Those are not "can we win" questions; they are diagnosis or capital allocation. Forcing the triangle onto them is the same mistake as using Ansoff for a margin drop or the 4Ps for a make-vs-buy.
Right tool, wrong use — the unique fail. Prompt: should we enter, reposition, or respond to an entrant? Candidate opens with three equal branches, spends three minutes on each, and never states which fact would kill the recommendation. That is symmetric touring. It is the failure mode that belongs to this lens specifically, because the labels feel balanced and the candidate confuses balance with rigor. Ohmae's triangle was never meant to be three equal speeches.
A second, quieter fail: stuffing "market trends" under company. Trends are customer demand or competitor capacity. Company is what this firm can do on Monday at a cost that still leaves margin.
Worked example: VoltForge adapts the triangle
Prompt. VoltForge makes lithium packs for warehouse robotics in the US Midwest. Revenue is $84m. Contribution margin is 31%. A Chinese entrant, PackNova, just won two national 3PL accounts with packs priced 22% below VoltForge's list. The CEO asks whether to match price network-wide or defend the installed base with a 48-hour on-site swap program for fleet operators.
Clarify. Success metric is next-year contribution dollars, not share of packs sold. PackNova will stay. VoltForge can cut list price, add the swap program, or both. Capex for the swap network is $4.2m in year one; variable cost of a swap visit is $180.
Do not open with "I'll use the 3Cs." Open with the decision and the first test.
Candidate path (adapted, not recited). "I would treat this as a fit problem: which customers will still pay for reliability, whether we can deliver a swap promise at a cost that keeps margin, and whether PackNova can copy that service in twelve months. I would start with customer mix, because a blanket price match only makes sense if the buyers who left are the ones we can profitably keep."
That is Ohmae's triangle in the room without the brand name. The bet is: this is a customer-mix and service problem, not a unit-cost race.
Customer branch first (numbers). Of $84m revenue, fleet 3PLs are 55% of revenue ($46.2m) but 68% of contribution, because they pay $1,100 average pack price versus $820 for regional warehouses. PackNova's 22% cut implies a matched fleet price of about $858 ($1,100 × 0.78) and a regional price of about $640.
Willingness to churn is not uniform. Fleet operators care about downtime: a dead pack idles a $42/hour robot. Regional warehouses care more about sticker price. So the kill test is: what share of fleet revenue is already dual-sourcing PackNova, and will fleets pay for guaranteed swap?
Interviewer hands you: 18% of fleet revenue has already moved; the remaining 82% of fleet accounts say they would pay up to $95/pack/year equivalent for a 48-hour swap SLA.
Company branch second (only what Monday requires). Current contribution on a fleet pack: price $1,100, variable cost $720, contribution $380. After a full match to $858: contribution $138. You gave away $242 per fleet pack to chase buyers who already have a cheaper alternative.
Swap economics: assume 38,000 fleet packs in the installed base that stay with VoltForge. At $95/pack/year willingness, theoretical service revenue is about $3.6m. If 40% of packs need one swap per year, variable swap cost is 15,200 × $180 ≈ $2.7m. After $4.2m year-one build, year-one service contribution is roughly $3.6m − $2.7m − $4.2m = −$3.3m. Ugly in year one. By year two, if capex does not repeat and the same volumes hold, contribution flips to about +$0.9m before any price defense benefit.
The company question is not "are we a great company." It is: can we fund year one and still protect the $380 contribution on packs that do not need to match PackNova's list.
Competitor branch last, as a response test. PackNova's landed cost per pack is about $610. They can sit near $820 forever on regional accounts. They have no US field techs today. Building a Midwest swap network from zero would take, on my estimate, 12–18 months and similar capital. That window is the only reason the service defense is live.
Recommendation. Do not match price network-wide. Hold fleet list near $1,100, offer the 48-hour swap as a paid add-on at ~$90/pack/year to accounts that renew, and selectively match only on the regional SKUs where contribution was already thin. Risk: fleets put VoltForge on dual-source contracts and still buy PackNova for new robots. Next ask: last two quarters of fleet renewal rates by account size.
The so-what is a number: protecting ~$380 contribution on defended fleet packs beats buying volume at $138 after a full match. The candidate never said "3Cs." They used the triangle as a sequence of tests.
How the recital version loses the same case
Same prompt, bad path: three minutes on "company strengths" (brand, engineering culture), three on "customer needs" (warehouse growth, e-commerce), three on "competitors" (PackNova's China cost base), then a vague "we should differentiate." No fare-by-segment table. No kill criterion. No year-one swap P&L. The interviewer cannot score judgment because nothing was decided.
That is the exact failure: the labels appeared, the integration did not.
When to reach for this lens (and when to leave it)
Use company–customer–competitor when the decision is competitive position: launch, reposition, respond to an entrant, or choose which segment to serve. The metric is usually share, contribution, or "can we win," not "why did profit fall."
Leave it for P&L diagnosis (profitability), pure ops trees, and portfolio allocation. Leave product-mix and go-to-market mechanics to other tools. Leave market–product growth moves to Ansoff. Leave an extra "C" for cost or channel to the 4Cs post if that is the real prompt. Distinct tools, distinct questions.
Practice this today
Take any "respond to an entrant" prompt. Write one sentence for the decision metric. Write which vertex you will test first and the one number that would kill your bet. Do not write the words company, customer, or competitor on the page until the bet is stated. Then run a timed structure drill and see whether your next question changes because of the structure.
Everything on CoachNed is open for seven days, no card; then $120 for a recruiting season or $49 a month. Start with a five-minute typed case at /start, or a full structure drill at /drills/structure.
Frequently asked questions
Should I say "3Cs" out loud in a case interview?
Almost never. Restate the decision, name the first test, and ask for the fact that would kill it. Interviewers reward the logic; the brand name adds nothing and often signals a template.
Who invented the 3Cs framework?
Kenichi Ohmae popularized the strategic triangle of corporation, customers, and competitors in The Mind of the Strategist (1982) and a related European Management Journal article the same year. Prep shorthand shortened "corporation" to "company."
Is the 3Cs the same as the 4Cs or the 4Ps?
No. The 3Cs is a competitive-position lens. The 4Cs usually adds cost or channel. The 4Ps is a marketing-mix checklist. Using the wrong family for the prompt is a common structure miss.
When is the 3Cs the wrong first framework?
I will be precise. The 3Cs fails in two ways: wrong tool for the prompt, and right tool used as a tour.
When you still need to isolate a P&L driver, fix an operations bottleneck, or allocate capital across a portfolio. Start with the tool that answers the question the CEO actually asked.?
Firms do not publish a secret 3Cs rubric. They do publish what problem-solving interviews test. McKinsey's interviewing page says interviewers want to see how you structure ambiguous challenges, identify important issues, deal with facts and data, form conclusions, and articulate thinking in a fast discussion.
Sources
- The Mind of the Strategist (Google Books) — Ohmae's 1982 book introducing the strategic triangle of company, customer, and competition. Checked 2026-09-24.
- The strategic triangle (RePEc / EMJ 1982) — Ohmae's European Management Journal article on corporation, customers, and competitors as an integrated model. Checked 2026-09-24.
- Interviewing at McKinsey — Official description of what problem-solving interviews assess (structure, issues, data, conclusions, articulation). Checked 2026-09-24.
- BCG Case Interview Preparation — Official BCG guidance on structuring, prioritizing, calculating, and reasoning in case interviews. Checked 2026-09-24.