Why this session looks outward
Session 3 found Himalaya's internal leak: a partner-reseller onboarding gap feeding single-module churn. Fixing that is necessary - and not sufficient. While Himalaya was leaking, two AI-native rivals launched at 40% lower prices and onboard clients in days, not weeks. A strategy built only from the inside is a strategy built blind. Today's three tools read the competitors, the industry, and the macro weather - and every one of them must end in an action, not a list.
SWOT that actually produces strategy 6 min live
Every executive has filled a SWOT. Almost none of those SWOTs changed a single decision - they died as four tidy lists on slide 7. Welcome to the SWOT graveyard. The fix is TOWS: cross-pair the quadrants so every combination is forced to produce an action - S×O offensive plays, W×T survival plays, S×T defensive plays, W×O improvement plays.
LiveFrom four lists to four plays3 min▶
Weihrich's TOWS matrix takes the SWOT you already have and asks four forcing questions. Each one pairs an internal quadrant with an external one - which is exactly what a strategy is: your resources meeting the world.
- S×O offensive: which strength unlocks which opportunity? Himalaya: 8M consumer touchpoints × unmonetized consumer data = a data product no AI-native startup can copy on day one.
- W×T survival: which weakness does a threat exploit? Weeks-long onboarding × rivals who onboard in days = the wound the price gap pours salt into. Fix first.
- S×T defensive: which strength blunts which threat? Multi-module NRR of 112% says depth defends - clients on 2+ modules barely churn.
- W×O improvement: which opportunity fixes a weakness? The same AI wave that armed the rivals can collapse Himalaya's own onboarding time.
The graveyard in the wild: a regional services firm ran the same annual SWOT workshop for six years - same facilitator, same flipcharts, forty entries per year. When a new strategy lead finally cross-paired the quadrants, the W×T cell produced one sentence ("our manual quoting loses every deal under 48 hours") that reset the entire roadmap. Six years of lists; one afternoon of pairs.
LiveRules for an honest SWOT3 min▶
TOWS can only convert what the SWOT feeds it. Garbage lists in, garbage plays out. Three rules keep the input honest:
- Strengths are relative to competitors, not to your past. "Great platform" is not a strength if both rivals ship one too. "8M consumer touchpoints" is - nobody else has them.
- Threats are outside your control. If you can fix it, it is a weakness. Slow onboarding is a weakness; buyers resetting their expectations to days-not-weeks is a threat. The W×T pairing only works when you keep them apart.
- Every entry needs a fact behind it. A number, a quote, a named observation. "Strong brand" with no evidence is an opinion wearing a badge - strike it or source it.
Self-study3C: the minimal external read2 min read▶
Kenichi Ohmae's 3C model is the pocket version of today's whole session: any strategy must simultaneously answer for the Company (what can we actually do well?), the Customer (what do they value and how is that shifting?), and the Competitor (what can they do that we cannot?). If a plan reads beautifully but only mentions one C, it is a wish.
| C | The Himalaya read in one line |
|---|---|
| Company | Deep multi-module platform, 8M consumer touchpoints, slow to onboard |
| Customer | Mid-size businesses now expect days-not-weeks and AI in the box |
| Competitor | Two AI-natives: 40% cheaper, onboarding in days, no consumer-data asset |
Use 3C as the 60-second sanity check before any bigger analysis: if you cannot fill the three rows, you are not ready for a SWOT, let alone a strategy.
Porter's Five Forces 6 min live
SWOT reads YOUR position; Five Forces reads the INDUSTRY - why some industries print money and others grind everyone down. Porter's 1979 insight: profitability is not decided by how good you are, but by five structural forces that squeeze margin. Score them honestly and you know where the pressure comes from - and therefore which moat is worth building.
LiveReading the five boxes on Himalaya3 min▶
- New entrants: HIGH. The old barrier was engineering years; AI collapsed the build cost. Two rivals appeared in 18 months - expect a third.
- Buyer power: RISING. Power comes from alternatives. A 40% cheaper option that onboards in days means every renewal is now a negotiation.
- Substitutes: MED. Some clients will DIY a "good enough" layer on general AI tools. Watch, do not panic.
- Suppliers: LOW. Cloud and foundation models are commodities with multiple vendors. The one to watch: if one model provider becomes irreplaceable, this flips.
- Rivalry: HIGH. Slowing industry growth plus price-led attackers is the classic recipe for margin erosion.
LiveThe so-what: forces point at the moat3 min▶
A Five Forces read is wasted if it ends at scores. The point: forces tell you WHERE profit pressure comes from, and therefore which moat blunts it. Himalaya's pressure comes from entrants and empowered buyers - both feed on low switching costs. So the moat candidates are:
- Switching costs via multi-module depth. The data already whispers this: multi-module NRR is 112% while single-module clients churn at 14%. Every module activated is a lock tightened.
- Network effect via the consumer side. 8M end consumers touch Himalaya monthly. If consumer-side data makes each client's experience better, entrants cannot copy it at any price - they have no consumers yet.
The moat that was actually a puddle: a B2B software firm answered rising buyer power with a loyalty discount program - which is not a moat, it is a margin donation. Its competitor answered the same read by making its data export deliberately rich but its integrations deliberately deep. Three years later one of them set prices and the other matched them. Forces do not tell you to defend; they tell you what to build.
Self-studyBlue Ocean: stop fighting over the same water2 min read▶
Kim & Mauborgne's counterpoint to Porter: instead of out-muscling rivals in a red ocean, redraw the factors of competition. Their strategy canvas plots what the industry competes on (price, onboarding speed, module breadth, AI features) and asks what you could eliminate, reduce, raise, or create to make the comparison irrelevant. Himalaya competing on price loses; Himalaya creating a consumer-data value curve nobody else offers changes the axes. Session 5 picks this thread up when we redesign the offer.
Self-studyWardley mapping: why "platform" features commoditize3 min read▶
Simon Wardley's map adds the dimension Five Forces lacks: time. Every component of value evolves from genesis (novel, custom, expensive) through product to commodity (standard, cheap, invisible). Strategy is knowing where each of your components sits on that slope - and refusing to defend the ones sliding into commodity.
- Himalaya's storefront, booking, and payment modules were differentiators five years ago; today they are product heading to commodity - exactly why AI-natives rebuilt them in months.
- The components still left of the slope: the consumer-side data asset and the cross-module workflows. Those are where defensive investment compounds; the rest should get cheaper to run, not better funded.
- The Wardley question for any roadmap item: "are we investing in genesis or gold-plating a commodity?"
Self-studyPlaying to Win: five choices, one cascade3 min read▶
Lafley & Martin's cascade turns the external read into an integrated set of choices. Five questions, answered in order, each constraining the next:
- Winning aspiration: what does winning mean? (Himalaya draft: the platform mid-size consumer businesses refuse to leave.)
- Where to play: which segments, channels, geographies? (Multi-module mid-size clients - not a price war for single-module logos.)
- How to win: what advantage there? (Consumer-side data + switching-cost depth, per today's forces read.)
- Capabilities: what must we be great at? (Fast activation, data products.)
- Systems: what management systems make it stick? (Activation metrics on the exec dashboard, not just bookings.)
The test of a real strategy: the five answers reinforce each other. If "where to play" says mid-size but "how to win" needs enterprise sales motion, the cascade is broken.
PESTEL: the weather report 4 min live
Five Forces reads the industry; PESTEL reads the weather above it - political, economic, social, technological, environmental, legal forces you do not control but must price in. Aguilar sketched it in 1967 as ETPS; the discipline has not changed: scan wide, then bet narrow.
LiveA watchlist, not an essay4 min▶
PESTEL fails the same way SWOT does - as a completeness ritual. Twenty-four bullet points across six letters, none of which anyone reads again. Run it as a watchlist instead:
- Scan wide once: fill all six lanes fast, one honest item each. The discipline is coverage, not depth.
- Bet narrow: pick the 2-3 forces with real strategic weight. For Himalaya: the technological force (model cost collapse keeps arming new entrants) and the legal force (consumer-data and AI rules govern the very asset Himalaya wants to monetize).
- Assign an owner and a review date. A force with no watcher is a surprise in waiting. Quarterly is plenty - macro weather changes in seasons, not sprints.
The lane nobody watched: a consumer-data analytics vendor ran beautiful annual PESTELs - and still got blindsided by a privacy regulation that had been visibly drafted for two years, because the legal lane had no owner. The retrofit cost a year of roadmap. Their fix was one line of process: every starred force has a name next to it.
Self-studyScenario planning: rehearsing more than one future3 min read▶
Pierre Wack's team at Shell used scenarios to rehearse the 1970s oil shock before it happened - not by predicting it, but by taking two critical uncertainties seriously. The method: pick the two forces from your PESTEL that are both high-impact and genuinely uncertain, make each an axis, and sketch the four worlds.
- For Himalaya, try: AI regulation (tight vs loose) × SMB software spend (up vs down). Tight + down is the nightmare (compliance cost while budgets shrink); loose + up is the land grab (entrants multiply, speed wins).
- For each world, ask: what would we wish we had started today? Moves that show up in three or four worlds are robust - do those regardless.
- Scenarios are rehearsal, not forecast. The value is that when the world lurches, someone in the room has already lived there for an afternoon.
SWOT Himalaya, then convert to TOWS ★ 9 min · every table plays
Three minutes, whole room: fill the four SWOT quadrants with facts from the brief. Enforce the rules - strengths relative to the two rivals, threats outside Himalaya's control, every entry with a number or observation behind it.
Each table takes the pairing challenge: produce ONE offensive play (S×O) and ONE survival play (W×T). Write each as an action sentence, not a theme - "monetize the consumer-side data no rival has", not "leverage data".
Tables read their plays aloud. Expected convergence: S×O = monetize the 8M-consumer data asset; W×T = fix onboarding speed before the price gap kills win rate. Divergence is welcome if the pairing logic holds.
Room check: could any play have been written WITHOUT the pairing? If yes, it was already obvious - the matrix earns its keep on the plays you did not walk in with.
Score the Five Forces, name the moat ★ 8 min · every table scores
Each table scores all five forces HIGH/MED/LOW - with a fact from the brief attached to every score. No evidence, no score.
Compare scores across tables. Disagreements are the good part: argue the evidence, not the adjective. (Most rooms land: entrants HIGH, buyers RISING, rivalry HIGH, substitutes MED, suppliers LOW.)
Now the question the scores exist for: which moat do we build? Two candidates from the brief - switching costs via multi-module depth, or network effect via the consumer side. Each table picks one and defends it in two sentences.
Spoiler kept honest: these are not rivals. The multi-module moat defends the base now; the consumer-side moat compounds later. Session 6 will place them on Horizons 1 and 3.
The scoring argument IS the deliverable. A leadership team that has fought about whether buyer power is HIGH or MED - with renewal data on the table - walks into pricing season with a shared map. The chart is a souvenir; the argument is the strategy work.
PESTEL speed round ★ 5 min · one force per table
Two minutes: each table scans all six lanes and nominates the ONE macro force that changes Himalaya's strategy most.
One sentence of defense per table, spoken aloud: "We nominate X because it changes Y decision." No decision changed, no nomination.
Tally the room. Typical winners: foundation-model cost collapse (it keeps arming new entrants) or data/AI regulation (it governs the consumer-data moat we just chose). Both starred lanes get an owner before the room leaves.
This week ◐ 30 min total
- SWOT→TOWS your own business unit: four honest quadrants (rules apply - relative strengths, external threats, facts only), then force one offensive and one survival play. Fifteen minutes, whiteboard or paper.
- Five Forces your industry: five scores, five facts. End with one sentence: "our margin pressure comes mostly from ___, so the moat worth building is ___."
- Read the scenario planning card above, and sketch the 2x2 for Himalaya (AI regulation tight/loose × SMB spend up/down). Ten minutes - which move shows up in all four worlds?
- Optional deep end: Porter's "How Competitive Forces Shape Strategy" (HBR, 1979) - still the sharpest 12 pages in strategy - or the Wardley mapping card if your roadmap debates keep circling.
Three questions before you go 🎯 ◐ 90 seconds
1 · Most corporate SWOTs never change a decision. Why - and what is the fix?
Lists describe, pairs decide. The graveyard is full of accurate SWOTs - the fix is forcing each quadrant pairing to yield a play.
2 · Your Five Forces read scores threat of new entrants HIGH. What does that actually tell you to do?
Forces tell you where profit pressure comes from, hence which defense compounds. Price cuts answer pressure with a margin donation; moats answer it with structure.
3 · The most useful way to run PESTEL with a leadership team is...
PESTEL is a weather report, not a thesis. Coverage once, then narrow bets with named watchers - a starred force with no owner is a surprise in waiting.
Frameworks covered & their origins
This course teaches the working 80% of each framework and cites the canon - the original books and papers stay the deep end for anyone who wants it.