CoachNed
Issue tree of brass pins and thread on a cream wall

Frameworks

7S in Case Interviews: Org Problems Only

Use hard and soft org alignment only when the case is an organization problem. Worked example: a PE portco where the founder stays CEO after a new COO.

UpdatedReviewed by Ned

The 7S lens is seven alignment checks on an organization. It is the right tree when the prompt is “the strategy is clear and the P&L still will not move” or “we just bolted on a COO and the place seized up.” It is the wrong tree for pricing, market entry, or a profit bridge. Naming “McKinsey 7S” in a pricing case is a meme fail. Teach the alignment, not the brand.

Use it only on org cases.

Hard versus soft (and why both matter)

Consultants split the seven into hard (easier to draw on a chart) and soft (where deals actually die). You do not need to tour all seven if two are broken.

ChecksTypical evidence
HardStrategy, structure, systemsOrg chart, incentives, KPIs, IT, who P&Ls
SoftSkills, staff, style, shared valuesWho gets hired, how the founder decides, what “good” means

Strategy here means the org’s stated game, not Porter. If the investment thesis is “professionalize a founder business,” the strategy S is that thesis. Structure is reporting lines. Systems are how money and information move (CRM, month-end, bonus). Staff / skills are bodies and capabilities. Style is how the CEO actually decides. Shared values are what people believe they will be punished for.

If structure says the COO owns operations but the founder still approves every hire, you have a structure–style crack. That is the case.

Worked example: PE portco, founder stays

Prompt. Harbor Partners bought Northline Logistics, a $90m-revenue regional LTL carrier, 18 months ago. Thesis: professionalize dispatch, lift on-time from 86% to 94%, expand two adjacencies. They hired a COO from a national carrier. The founder remains CEO. On-time is 87%. Driver turnover is 38%. The operating partner is in the room. This is not a pricing case and not a five-forces tour.

Do not open with all seven. Hypothesis: structure and systems were installed on top of an unchanged style and incentive system.

Structure. COO owns dispatch on the chart. Eight terminal managers still call the founder on weekends. The founder still signs offers over $70k. The COO is a dotted-line decoration.

Systems. A new TMS was turned on. Terminal managers keep a parallel spreadsheet “because the TMS lies.” Bonus is still % of terminal revenue, not on-time or empty-mile. The new on-time KPI is on a dashboard nobody’s pay hits.

Staff / skills. National-carrier COO thinks in relays and team drivers. Northline is a local-turn, driver-as-owner culture. Skills mismatch: the COO’s playbook needs dispatchers the terminals do not have.

Style / values. Founder’s style: heroics, exception freight, “we never say no.” Shared value: saying no to a drunk-on-Friday shipper is disloyal. The thesis needs saying no. Values were never reset.

AlignmentStatus$ or ops so-what
Structure vs styleBrokenCOO cannot move terminals
Systems vs bonusBrokenTMS ignored; revenue bonus fights on-time
Skills vs strategyWeakRelay model on a turn network
Shared values vs thesisBroken“Never say no” blocks density

Numbers. Empty miles 19% (peer 12%). At $3.10/mile and 18 million loaded miles, empty is 0.19/0.81 × 18m ≈ 4.2 million empty miles × $3.10 ≈ $13m. Closing half the gap to peer is ~$5m — the entire “professionalize” EBITDA bridge. It will not move while bonuses pay on revenue and the founder takes exception loads at 9pm.

Recommendation. This is an org fix, not another TMS module. Either (a) founder becomes Chair with no terminal calls, COO has hire/fire and bonus design in 30 days, bonuses flip to on-time and empty-mile, or (b) Harbor admits the thesis required replacing the founder and they did not. Do not spend another $2m on software. Risk: founder quits and customers follow; that risk is why you should have contracted non-solicits and a longer earnout — too late for some of it. Next step: rewrite bonus on one page; operating partner sits in the quarter-end pay committee.

You used four of the seven. You did not recite a mnemonic.

When 7S is the wrong tool

Profit fell and mix, price, or volume might be the driver. Profitability first. Org may be why mix shifted; you still isolate the P&L driver first.

Should we enter Poland. Market entry.

Should we pay 11×. M&A or PE DD. 7S can be one risk branch inside DD (can this team execute). It is not the whole DD.

Pricing a SaaS SKU. Never.

The mistake unique to 7S

Touring all seven because there are seven. Interviewers hear a shopping list. The unique fail is treating strategy as “industry strategy” and spending the case on competitors. In an org case, strategy is the thesis the org is supposed to run. Competitors belong only if the org cannot staff the capability the thesis needs.

Second unique fail: recommending a workshop. “Align the culture” is not a 90-day action. Bonus formulas and who can sign an offer are.

How to open

“This looks like an alignment problem between the new operating structure and the founder’s actual authority and pay system. I will check structure, systems, and style first, not a full seven-point tour.”

Then go to bonuses and who the terminal managers call.

Practice org trees, not mnemonics

Use a structure drill with an org / post-merger prompt. If you name all seven, you over-indexed.

Start a structure drill