2. 1. Guerrilla Warfare: The Asymmetric Playbook
Mao didn’t invent guerrilla warfare, but he wrote the manual. On Guerrilla Warfare (1937) codified a set of principles for how a weaker force defeats a stronger one. The core insight: the guerrilla doesn’t win battles. The guerrilla makes the enemy’s strength irrelevant. Every bootstrapped startup competing against a funded incumbent is fighting a guerrilla war whether it knows it or not.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Guerrilla Warfare | Warfare conducted by irregular forces using hit-and-run tactics, mobility, surprise, and knowledge of terrain. The guerrilla avoids pitched battles, strikes where the enemy is weak, and withdraws before the enemy can concentrate force. The goal is not to destroy the enemy but to exhaust them. | Compete where the incumbent can’t. Don’t launch a frontal assault on their core market. Pick off underserved segments, ship faster, be where they aren’t. The bootstrapped startup’s advantage is speed, focus, and willingness to serve markets the incumbent considers too small. | Basecamp vs. Asana/Monday/Jira: Basecamp never tried to win enterprise project management. It served small teams who wanted simplicity. It stayed profitable for 20 years while competitors burned billions. Guerrilla warfare: don’t fight their war. |
| “The enemy advances, we retreat” | Mao’s sixteen-character formula: “The enemy advances, we retreat. The enemy camps, we harass. The enemy tires, we attack. The enemy retreats, we pursue.” Never engage on the enemy’s terms. Control the tempo. | When the incumbent launches a competing feature, don’t engage. Move to a different segment. When they get distracted (reorg, new CEO, quarterly earnings pressure), ship aggressively. When they retreat from a market (cost-cutting, “focusing”), fill the gap immediately. Control the tempo of competition. | When Google launched Google+, Facebook didn’t panic-ship social features. They retreated (focused on mobile). When Google camped (poured resources into G+), Facebook harassed (acquired Instagram). When Google tired (G+ stagnated), Facebook attacked (mobile-first feed). When Google retreated (killed G+), Facebook pursued (dominated social). Textbook Mao. |
| Concentrate a Superior Force | The guerrilla is weaker overall but can achieve local superiority by concentrating all force on a single point. Attack where you outnumber the enemy 10:1, win decisively, then disperse before reinforcements arrive. The globally weak become locally strong. | You can’t beat the incumbent across the board, but you can beat them in one niche, one feature, one segment. Put 100% of your resources into the one thing where you can be 10x better. Win that decisively. Then expand. The startup’s version of local superiority: total focus on one thing. | Superhuman: concentrated all resources on one thing — making email fast for power users. Didn’t try to build a calendar, a CRM, a notes app. 10x better at one thing for one segment. Local superiority achieved through radical focus while Gmail served billions with divided attention. |
| Knowledge of Terrain | The guerrilla’s decisive advantage: they know the terrain better than the occupier. Every hill, every path, every village. The conventional army has maps; the guerrilla has lived experience. Terrain knowledge compensates for inferior firepower. | Domain expertise is the bootstrapper’s terrain advantage. The founder who spent 10 years in the industry knows things that no market research can reveal: the real workflows, the real pain points, the workarounds, the politics. The VC-funded team with a pitch deck has a map. The domain expert has lived the terrain. | Toast (restaurant POS): founders came from the restaurant industry. They knew that restaurant owners care about reliability above all else because a POS crash during dinner rush is catastrophic. Competitors from tech backgrounds built prettier UIs. Toast built something that never went down. Terrain knowledge won. |
3. 2. Protracted War: Winning by Not Losing
On Protracted War (1938) is Mao’s masterwork on strategy. The core argument: China cannot win a quick war against Japan (Japan is stronger), but Japan cannot win a long war against China (China is bigger and fighting on its own territory). Therefore, China’s strategy must be to extend the war. Time is the underdog’s weapon. The startup translation: survival is strategy.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Protracted War | A three-phase strategy: (1) strategic defensive (survive while the enemy is strong), (2) strategic stalemate (build strength while the enemy overstretches), (3) strategic offensive (attack when the balance has shifted). You don’t need to win now. You need to still be alive when conditions change. | The bootstrapper’s arc: (1) survive while competitors raise and spend (defensive), (2) build product and customers while competitors struggle with burn rate (stalemate), (3) grow aggressively when competitors run out of funding or pivot (offensive). The key insight: if you can survive long enough, the landscape always changes in your favor. | Mailchimp: survived for 12 years as a bootstrapped business while competitors raised hundreds of millions. Watched competitors rise and fall. When the market matured and email marketing became essential for SMBs, Mailchimp was the last one standing. Sold for $12B. Protracted war, won in the third phase. |
| Strategic Defensive | Phase 1: the enemy is strong and you are weak. Do not seek decisive battle. Trade space for time. Preserve your forces. Let the enemy overextend. Your job is not to win — your job is to not lose. | Pre-product-market-fit: your job is to survive. Keep burn low. Don’t hire ahead of revenue. Don’t compete for the incumbent’s customers. Serve the customers they ignore. Not losing is winning during the strategic defensive phase. | Notion in 2016–2018: tiny team, almost died twice, nearly ran out of money. They didn’t try to compete with Confluence or Google Docs. They served individual users and small teams — a market the incumbents ignored. Strategic defensive: survive until conditions change. |
| Strategic Stalemate | Phase 2: the enemy has overextended and can’t advance further, but you’re not yet strong enough to counterattack. The longest phase. Use this time to train, organize, build infrastructure, and erode the enemy’s will through constant small actions. | You have product-market fit but aren’t yet dominant. The incumbent exists but isn’t crushing you. This is the phase to compound: build features, deepen the product, grow the community, create switching costs. Don’t rush to scale — deepen what you have. | Linear (2020–2023): had PMF with developer teams but wasn’t challenging Jira broadly. Used the stalemate phase to obsessively refine the product, build keyboard-first workflows, and create a cult following. When they expanded to larger teams, the product was unassailable because they’d compounded during the stalemate. |
| Strategic Offensive | Phase 3: the balance has shifted. You are now stronger (or the enemy is weaker). Launch the decisive campaign. This is the moment to be aggressive, expand rapidly, and consolidate gains. But only when the conditions are truly ripe — premature offensive is adventurism. | The inflection point: you have the product, the team, the revenue, and the market conditions. Now scale aggressively. Hire sales. Raise capital if needed. Go upmarket. This is the time to blitzscale — but only after the first two phases have prepared the ground. | Figma launching FigJam, expanding to enterprise, and going after Adobe’s entire design suite — this was the strategic offensive, launched only after years of building product (defensive) and growing with individual designers (stalemate). The $20B acquisition offer validated the timing of the offensive. |
| Trading Space for Time | The guerrilla gives up territory to preserve forces. Land can be retaken; a destroyed army cannot. The willingness to retreat, to lose ground temporarily, to give up non-essential positions in order to preserve the core — this is the hardest discipline for commanders and founders alike. | Give up features, markets, or customers that drain resources without strategic value. Kill the product line that’s “almost working.” Exit the market segment that requires custom work. Every resource spent on a losing position is a resource not spent on the decisive one. Trading space for time means accepting short-term losses for long-term survival. | Netflix killing its DVD business (which was still profitable) to go all-in on streaming. They traded space (DVD revenue) for time (streaming market position). The DVD market was a position they could afford to lose; the streaming market was the war. |
4. 3. The Mass Line: Bottom-Up Intelligence
The mass line is Mao’s most original contribution to organizational theory. It’s a feedback loop: gather ideas from the masses, synthesize them into coherent policy, return the policy to the masses for implementation, then gather feedback again. It sounds like a customer development loop because it is one — invented 40 years before Steve Blank.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| The Mass Line | “From the masses, to the masses.” Gather the scattered, unsystematic ideas of the people. Concentrate them into coherent policy through study. Return them to the masses as guidance. Then gather feedback on implementation. Repeat endlessly. | The customer development loop: talk to users, synthesize their scattered pain points into a product thesis, build the product, ship it to users, measure what happens, talk to users again. The mass line is the lean startup method with Chinese characteristics. | Rahul Vohra’s Superhuman PMF engine: survey users, categorize responses, synthesize into product priorities, ship improvements, re-survey. The cycle repeats every quarter. It’s the mass line in SaaS form: from the users, to the users. |
| From the Masses, To the Masses | The direction of information flow matters. Ideas originate from the people (not the leadership), are refined by the leadership, and return to the people as action. The leadership’s role is synthesis, not invention. The creativity is distributed; the coherence is centralized. | Your users know things you don’t. The best product ideas come from watching how users misuse your product, what workarounds they build, what they complain about. The founder’s job is not to have all the ideas but to synthesize user behavior into coherent product direction. | Slack’s emoji reactions, threaded replies, and channel organization all came from watching how users adapted the tool. Users were already using emoji as reactions (mass behavior). Slack formalized it as a feature (synthesis). Shipped it back (to the masses). The mass line in product development. |
| Investigation Without Preconceptions | “No investigation, no right to speak.” Mao insisted that cadres spend extended time living among the people before making policy. Don’t arrive with theories — arrive with questions. The investigation must precede the conclusion. | Don’t build a solution before understanding the problem. Don’t write the PRD before doing user research. Don’t design the architecture before understanding the constraints. “No investigation, no right to speak” is the most concise formulation of the anti-build-first fallacy. | The Intuit “Follow Me Home” program: product teams literally followed customers home and watched them use the software in their natural environment. No questions, no preconceptions — just observation. Mao would have approved: investigation precedes theory. |
| Seeking Truth from Facts | Mao’s epistemological principle: start from objective reality (facts), identify the internal laws and patterns (truth), and use those to guide action. Not ideology-first but reality-first. Let the facts lead, not the theory. | Data-informed, not data-driven. The difference matters: data-driven means the data decides (which leads to A/B testing your way into local optima). Data-informed means the data informs your judgment. Seek truth from facts means looking at the data honestly, including the inconvenient parts. | The startup that surveys 100 users, 90 say they love the product, and celebrates — without investigating why 10 churned. Seeking truth from facts means looking at all the facts, especially the ones that contradict your thesis. The 10 churned users contain more truth than the 90 happy ones. |
5. 4. Surround the Cities from the Countryside
Mao’s most famous strategic innovation. Lenin’s revolution was urban: seize the capital, seize power. Mao couldn’t do that — the Nationalists controlled the cities. So he flipped the playbook: win the countryside first, encircle the cities, let them fall last. This is the most directly applicable Maoist concept to startup strategy.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Surround the Cities from the Countryside | Win where the enemy isn’t. Control the rural areas (which the Nationalists considered unimportant), build a base, recruit, train, and eventually surround and take the cities. The periphery conquers the center. | Start with the customers the incumbent doesn’t care about. SMBs, indie developers, students, emerging markets. Build product-market fit there. Grow. Eventually, you’re large enough to challenge the incumbent in their core market — and you arrive with a battle-tested product and a loyal base. | AWS: started serving startups (the countryside) that IBM and Oracle didn’t care about. Built the product on small customers. Grew into mid-market. Eventually took enterprise workloads from the very incumbents who laughed at cloud computing. The countryside surrounded the city. |
| Base Areas (Revolutionary Bases) | Liberated zones where the guerrilla has full control. Not the whole country — just specific regions. From these bases, the revolution expands. Each base area is self-sustaining: it has its own government, economy, and military. Lose the base areas and you lose the revolution. | Your core market segment, your beachhead. The one niche where you are the undisputed leader. Don’t expand until the base area is secure. The base area funds the expansion, provides the case studies, generates the word-of-mouth. It’s your source of strength, not a stepping stone. | Shopify’s base area: small online stores selling physical products. They owned that segment completely before expanding to enterprise, POS, payments, and fulfillment. Every expansion was funded and validated by the base area. Without it, there’s no Shopify. |
| The Long March | The 6,000-mile retreat (1934–1935) that nearly destroyed the Communist Party but ultimately saved it. 80% casualties. But the survivors were the hardened core that would win the revolution. The Long March was a catastrophe that became a founding myth and a selection event. | The near-death experience that forges the team. Almost running out of money. Losing your biggest customer. A critical technical failure. The startups that survive these crucibles emerge with a hardened team, a clarified mission, and a founder who knows exactly what matters. The Long March is survivorship bias, but for the survivors, it’s real. | Airbnb’s 2008–2009: $20K in credit card debt, selling cereal boxes to fund the company, YC application as a last resort. The “Long March” period produced the founding story, the resilience, and the clarity of mission that carried them to a $100B company. The survivors of the march built the revolution. |
| Establishing a New Base After Retreat | After the Long March, the CPC established a new base in Yan’an — remote, impoverished, but defensible. The retreat wasn’t just survival; it was relocation to better terrain. The goal of a retreat is not to stop moving but to find ground where you can win. | The pivot. You retreat from your current market/product, but you don’t just wander — you deliberately relocate to a new market where conditions favor you. The failed consumer app team that pivots to B2B is establishing a new base area. The key: choose the new terrain deliberately, don’t just flee. | Stewart Butterfield: game company fails (Glitch), retreats to internal tool (Slack), establishes a new base area in enterprise messaging. The retreat from gaming wasn’t random — the team recognized that the internal tool was better terrain. New base, defensible position, eventual dominance. |
6. 5. On Contradiction: Maoist Dialectics
Mao’s On Contradiction (1937) is his most philosophical work, and it’s more practical than it sounds. Where Lenin identified contradictions in incumbent systems, Mao developed a framework for working with contradictions — understanding that they’re not problems to solve but tensions to navigate.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Principal Contradiction (Maoist version) | In any complex situation, many contradictions exist, but one is principal — it determines the character of the whole. Resolve it and the secondary contradictions realign. But the principal contradiction changes over time. What was primary yesterday may be secondary today. Constant reassessment is required. | Your company’s principal contradiction shifts with stage. Pre-PMF: the contradiction between what you’re building and what the market wants. Post-PMF: the contradiction between growth and quality. At scale: the contradiction between innovation and maintenance. The founders who fail are the ones still solving yesterday’s principal contradiction. | Twitter’s failure to resolve the principal contradiction at each stage. Early: distribution vs. engagement (solved). Growth: content quality vs. free speech (never solved). At scale: advertiser safety vs. user engagement (never solved). Each stage demanded a different principal contradiction be addressed. Twitter addressed the first and fumbled the rest. |
| Antagonistic vs. Non-Antagonistic Contradictions | Some contradictions can be resolved through discussion and compromise (non-antagonistic: contradictions “among the people”). Others can only be resolved through struggle (antagonistic: contradictions with the enemy). Treating a non-antagonistic contradiction as antagonistic creates unnecessary enemies. Treating an antagonistic one as non-antagonistic leads to defeat. | Not all competition is war. Some conflicts are with partners, customers, or internal teams — resolvable through alignment. Others are with direct competitors trying to kill you — these require competitive action. The mistake: treating every disagreement as war (paranoid) or treating existential threats as misunderstandings (naive). | Apple and Google: antagonistic on mobile OS (Android vs. iOS) but non-antagonistic on Google Search as default iOS search engine. Both relationships exist simultaneously. The founders who can hold both — cooperating on some axes while competing fiercely on others — navigate contradictions maturely. |
| The Transformation of Contradictions | Under certain conditions, contradictions transform: what was the principal aspect becomes secondary, and vice versa. The dominant force becomes the subordinate one. These transformations are the pivotal moments in any conflict or market. | The startup that was the disruptor becomes the incumbent. The feature that was your moat becomes your liability. The community that powered your growth becomes the force that constrains your evolution. Contradictions transform, and the company that doesn’t recognize the transformation gets caught on the wrong side. | Facebook in 2007: the network effect was the principal positive force (growth). Facebook in 2023: the network effect is the principal constraint (can’t change the product without disrupting the network). The contradiction transformed: the same force that built the company now prevents it from evolving. |
| One Divides Into Two | Every unity contains the seeds of its own division. Every strength generates its own weakness. Every success creates the conditions for new problems. There is no permanent equilibrium — only continuous splitting and recombination. | Every solution creates new problems. Launch a self-serve product: you solve distribution but create a support burden. Raise VC: you solve funding but create growth expectations that distort product decisions. Hire fast: you solve capacity but create culture dilution. There is no action without side effects. | Slack’s success at making communication easy created the problem of making communication excessive. The solution (frictionless messaging) contained its own negation (notification fatigue, always-on culture). One divides into two: every product success defines its own failure mode. |
7. 6. On Practice: Learning by Doing
On Practice (1937) is Mao’s epistemology: all knowledge comes from practice. You don’t understand something until you’ve done it. Theory without practice is useless; practice without theory is blind. The loop is: practice → theory → practice again, at a higher level. This is the build-measure-learn loop stated with philosophical precision.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Practice as the Criterion of Truth | The only way to know if a theory is correct is to test it in practice. Not argument, not authority, not elegance of reasoning — practice. If the theory doesn’t survive contact with reality, the theory is wrong, no matter how logically sound it appears. | Ship it. The pitch deck is not truth. The PRD is not truth. The user research is not truth. Only shipping the product and measuring what happens reveals truth. The startup that debates internally for months has no knowledge. The startup that shipped a crappy MVP last week has more truth than a year of planning. | Dropbox’s MVP: a video demonstrating a product that didn’t exist yet. 70,000 signups overnight. The truth was revealed by practice (the landing page), not by theory (the business plan). Drew Houston didn’t need a market study — he needed a waitlist. |
| Perceptual Knowledge vs. Rational Knowledge | Knowledge develops in stages: first perceptual (you observe phenomena), then rational (you understand the underlying laws). Most people stop at perceptual. The leap from “I see what’s happening” to “I understand why it’s happening” is the critical cognitive step. | Vanity metrics are perceptual knowledge (we see signups going up). Understanding why signups go up (which channel, which message, which user segment) is rational knowledge. Most dashboards show perceptual knowledge. The insight that changes the business comes from the rational level. | A startup sees a spike in signups (perceptual). Investigation reveals the spike came from a single Hacker News comment in a niche thread (rational). Now they know: their audience is developers in that specific niche, not the broad market they assumed. The perceptual-to-rational leap changes the entire strategy. |
| The Spiral of Knowledge | Knowledge moves in spirals: practice → theory → practice at a higher level → refined theory → higher practice. Each cycle deepens understanding. There is no final knowledge — only the current iteration of the spiral. | Product development is a spiral, not a line. V1 teaches you what V2 should be. V2 teaches you what V3 should be. The product at launch is not the product at scale. Founders who plan the final product from day one are drawing a straight line through a spiral. You can’t see V3 from V1 — you have to travel the spiral. | Instagram: Burbn (check-in app) → insight that people only used the photo feature → Instagram V1 (photo filters) → insight that Stories format was winning attention → Instagram Stories → Reels. Each iteration was informed by the previous practice. The final product was unreachable from the starting point without traveling the spiral. |
| Concrete Experience Over Abstract Theory | A cadre who has actually organized a village is worth ten who have read books about organization. Mao distrusted intellectuals who theorized without doing. The doer with rough theory beats the thinker with polished theory. | The founder who has shipped three failed products knows more than the MBA who has analyzed three successful case studies. Startup knowledge is embodied, not academic. Hire the person who has done the thing, even imperfectly, over the person who has studied the thing, however thoroughly. | The serial founder with two failures and one modest success will outperform the first-time founder from McKinsey in almost every scenario — because the serial founder has concrete experience with the specific type of chaos that is a startup. The McKinsey analyst has abstract theory. Mao would hire the serial founder. |
8. 7. The United Front: Coalition Building
Mao allied with his mortal enemy (the Nationalists) to fight a greater threat (Japan). The United Front doctrine: unite with all forces that can be united against the main enemy, even if your allies are themselves your future competitors. Strategic alliances are temporary, situational, and instrumental — never sentimental.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| The United Front | A broad alliance of classes, parties, and groups united against a common enemy. The Communist Party participates in the alliance but maintains its own identity, organization, and army. You ally without merging. You cooperate without surrendering autonomy. | Partner with competitors against a common incumbent. Join industry associations, co-market, share an ecosystem — but maintain your own product identity, your own customer relationships, your own distribution. The united front is cooperation with independence. | The CNCF (Cloud Native Computing Foundation): competing companies (Google, Red Hat, AWS) united against legacy infrastructure. Each maintained its own products and identity. The united front gave them collective market-making power while preserving individual competitive advantage. |
| Unite with the Secondary Enemy Against the Primary Enemy | Your enemy’s enemy is your friend — temporarily. Mao allied with the Nationalists (secondary enemy) against Japan (primary enemy). After Japan was defeated, the Nationalists became the primary enemy again. Alliances are strategic and time-bound. | Partner with a smaller competitor to challenge the dominant player. Once the dominant player is weakened, you may compete with your former ally. This is not betrayal — it’s strategic clarity about which enemy matters right now. | Samsung and Google in Android: united against Apple (the primary enemy in mobile). Google provided the OS, Samsung provided the hardware. Both benefited. Now they compete on services (Samsung pushing its own app store, Google making Pixel phones). The united front served its purpose; now the secondary contradictions emerge. |
| Independence Within the Alliance | The CPC maintained its own army, its own base areas, and its own propaganda within the United Front. It never dissolved into the Nationalist structure. The alliance was real but the independence was non-negotiable. | When you partner with a platform (Salesforce AppExchange, AWS Marketplace, Shopify App Store), maintain your own direct customer relationships, your own billing, your own brand. Use the platform for distribution but never let it become your only channel. The partner is not your friend; the partner is a vehicle. | Zoom used the App Store for distribution but always maintained its own direct download, its own billing, and its own brand identity. When Apple launched FaceTime improvements, Zoom wasn’t dependent. Independence within the alliance: use the platform, don’t become the platform. |
| Isolate the Main Enemy | The purpose of the United Front is not just to add allies but to isolate the enemy. If your enemy has no allies, they face you alone. The strategic goal: make the incumbent friendless. Surround them diplomatically before you challenge them militarily. | Before competing directly, make sure the incumbent has no allies. Win over their integration partners, their developer ecosystem, their agency partners. When you finally challenge them, they discover that the ecosystem has already shifted. The battle is won before it’s fought. | HubSpot’s agency partner program systematically recruited the agencies that used to recommend Salesforce for SMBs. By the time HubSpot competed with Salesforce directly in SMB CRM, the agency ecosystem — the Nationalist army in this analogy — had already switched sides. The main enemy was isolated. |
9. 8. Rectification: Organizational Culture as Weapon
The Yan’an Rectification Movement (1942–1944) was Mao’s tool for creating ideological unity. It combined study sessions, self-criticism, and peer accountability to align the party’s thinking. It was extremely effective at creating a shared mental model — and extremely dangerous when taken to extremes. The startup version: culture-building as strategic capability.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| Rectification Campaign | A periodic, structured process for aligning the organization’s thinking with the current strategic direction. Study the core texts, discuss them in groups, criticize deviations, recommit to the line. Not a purge — a realignment. The goal is unity through education, not coercion. | Offsites, strategy workshops, “reboot” weeks. Periodic, structured realignment of the team on vision, values, and direction. Essential after rapid hiring, pivots, or leadership changes. Without periodic rectification, the team drifts into 15 different understandings of the mission. | Stripe’s internal strategy documents and reading materials for new hires — a form of rectification that ensures everyone operates from the same mental model. The onboarding process as rectification campaign: align new cadres with the party line before they start making decisions. |
| Study Sessions | Small groups studying core texts together, discussing their meaning, and applying them to concrete situations. Not lectures — discussions. The group holds itself accountable for understanding and applying the material. | Book clubs, tech talks, architecture reviews, post-mortems as learning events. The startup that reads and discusses The Mom Test together will conduct better user research than one where the CEO read it alone. Shared study creates shared language, which creates shared action. | Bridgewater’s required study of Principles by all employees. Love it or hate it, it created a shared mental model that allowed the organization to operate with unusual autonomy — because everyone had internalized the same decision-making framework. Study sessions as alignment infrastructure. |
| Criticism and Self-Criticism | The practice of publicly identifying one’s own mistakes (self-criticism) and those of others (criticism). The purpose: rapid error correction and prevention of cognitive calcification. Done well, it’s the highest-bandwidth feedback mechanism. Done badly, it’s public humiliation. | Blameless post-mortems, 360 feedback, retrospectives. The key word is blameless — the Maoist version worked when it was genuinely about learning and failed catastrophically when it became about punishment. The difference between Netflix’s feedback culture and a toxic blame culture is exactly this distinction. | Pixar’s Braintrust sessions: directors present rough cuts and receive brutal but constructive feedback. It’s criticism without blame. The director isn’t punished for showing rough work — they’re expected to. This is Maoist criticism-self-criticism in its healthy form. When it becomes coercive (Uber’s early culture), it becomes the toxic version. |
| Combat Liberalism | Mao’s 1937 essay attacking “liberalism” in the organizational sense: avoiding difficult conversations, letting bad behavior slide, prioritizing personal relationships over the mission, gossiping instead of confronting directly. Liberalism is organizational cowardice. | The culture where everyone is “nice” but no one gives honest feedback. The team that tolerates underperformance because “they’re a good person.” The manager who vents about a report to other managers instead of addressing it directly. “Combat liberalism” means having the hard conversations early, directly, and honestly. | Kim Scott’s Radical Candor is literally “Combat Liberalism” repackaged for tech. The two-by-two matrix (care personally / challenge directly) maps exactly onto Mao’s critique: caring without challenging is “ruinous empathy” (liberalism). Challenging without caring is “obnoxious aggression” (commandism). You need both. |
10. 9. People’s War: Total Mobilization
People’s War is the concept that war is not just a military affair — it’s a total mobilization of every resource: economic, political, cultural, psychological. The entire population participates. In startup terms: GTM is not just sales. It’s everything the entire company does.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| People’s War | War is not the army’s job — it’s the whole people’s job. Farmers grow food for the army. Women run intelligence networks. Children serve as couriers. The distinction between civilian and military dissolves. Everyone contributes to the war effort in their own way. | Go-to-market is not the sales team’s job — it’s the whole company’s job. Engineers write blog posts. Designers share work-in-progress on Twitter. The CEO does support tickets. Everyone is marketing, everyone is selling, everyone is building the brand. The distinction between “product” and “GTM” dissolves. | Notion: engineers, designers, and community managers all contribute to GTM. Template galleries (product as marketing), the ambassador program (users as salesforce), Twitter presence (founders as content creators). There is no separate “marketing team” at early Notion — the whole company is the marketing team. People’s war. |
| The Sea and the Fish | “The guerrilla must move amongst the people as a fish swims in the sea.” The guerrilla depends on the population for food, shelter, intelligence, and recruits. Without popular support, the guerrilla is a fish out of water — exposed and dying. | The startup depends on its community the way the guerrilla depends on the population. Without users who love you (not just use you), you’re exposed. The community provides feedback, word-of-mouth, content, beta testing, and feature ideas. A startup without a community is a fish out of water. | Figma’s design community: users who create templates, plugins, tutorials, and advocate for the product organically. Figma swims in the sea of its community. When Adobe tried to acquire Figma, the community’s vocal opposition was itself a strategic asset. The sea protects the fish. |
| Self-Reliance | “Rely mainly on our own efforts.” External support is welcome but unreliable. Build the capacity to sustain yourself without outside help. The guerrilla force that depends on foreign aid is vulnerable to its patron’s withdrawal. | Bootstrap mentality even if you’ve raised funding. Revenue is more reliable than fundraising. Customer love is more reliable than press coverage. Organic growth is more reliable than paid acquisition. Build the business to survive if every external input disappears tomorrow. | Basecamp/37signals: deliberately avoided VC funding, grew on revenue, controlled their own destiny. When the market crashed, when competitors folded, Basecamp kept running because it relied on itself. Self-reliance is the ultimate competitive advantage because it eliminates the most common failure mode: running out of money. |
| Arming the Masses | Give the people weapons and training, not just orders. An armed population is a military asset. An unarmed population is a liability that must be protected. The guerrilla force multiplies itself by arming the population. | Give your users tools to build on your platform, not just features to consume. APIs, integrations, templates, SDKs. An empowered user base creates value you could never build alone. The platform that arms its users has an army. The product that only serves users has customers. | WordPress arming its users: plugins, themes, a massive developer ecosystem. WordPress didn’t build every feature — it armed the masses with the tools to build features themselves. 40% of the web runs on WordPress not because WordPress is the best product but because it has the largest armed population. |
11. 10. The Cultural Revolution: When Disruption Eats Itself
The Cultural Revolution (1966–1976) was Mao’s attempt to revolutionize the revolution — to disrupt his own bureaucracy using mass mobilization. It was a catastrophe: the economy collapsed, millions were persecuted, cultural heritage was destroyed, and the country lost a decade. The lesson is as important as the guerrilla playbook: there are forms of disruption that destroy value rather than create it.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| The Cultural Revolution | Mass mobilization of youth (Red Guards) against the party’s own bureaucracy. “Bombard the headquarters!” The revolution turned on its own institutions. The result: chaos, destruction of competent administrators, economic collapse, and cultural devastation. | When the founder disrupts their own organization too aggressively. The “reorg every six months” CEO. The leader who empowers junior employees to bypass their managers. The “move fast and break things” culture applied to the organization itself, not just the product. Internal disruption without guardrails destroys the capacity to execute. | Yahoo’s endless reorganizations under successive CEOs: each new leader disrupted the previous structure, purged the previous leader’s hires, and imposed a new vision — before it could be executed. Ten years of Cultural Revolution produced nothing but organizational PTSD. |
| Red Guards (Weaponized True Believers) | Students and young party members mobilized as a political weapon against “revisionists” within the party. They had ideological zeal but no experience, no restraint, and no accountability. Mao unleashed them and then couldn’t control them. | The newly hired “disruptors” who are brought in to shake things up but have no institutional knowledge. The consultants who recommend org changes without understanding the history. The junior employees who are empowered to “challenge everything” before they understand anything. Zeal without context is destruction. | The new VP of Engineering who arrives and immediately rewrites the tech stack, fires the “old guard” engineers, and imposes new processes — without understanding why the old system worked the way it did. Six months later: worse performance, lost institutional knowledge, demoralized team. Red Guard energy: destructive conviction without understanding. |
| “Bombard the Headquarters” | Mao’s slogan calling for attacks on the party’s own leadership. An invitation for anyone to challenge anyone, regardless of hierarchy or competence. The result: paralysis, as every leader became a potential target and every decision became a risk. | The “flat organization” taken to its logical extreme. When anyone can challenge any decision at any time, no decision sticks. When hierarchy is abolished rather than made transparent, you don’t get democracy — you get chaos. Some hierarchy is necessary for execution. | Valve’s flat structure: in theory, anyone can work on anything and challenge any direction. In practice (as reported by former employees), informal power structures emerged that were less transparent and less accountable than formal ones. Bombing the headquarters didn’t eliminate hierarchy — it made hierarchy invisible. |
| Destroying Institutional Memory | The Cultural Revolution destroyed temples, artifacts, books, and traditions. It persecuted teachers, academics, and anyone with specialized knowledge. A decade of institutional knowledge was wiped out. The country spent a generation rebuilding what was destroyed. | Rewriting the codebase from scratch. Firing all the senior engineers and hiring new ones. Killing the documentation. Deleting the institutional Slack channels. Every time you destroy institutional memory — whether through rewriting, reorging, or turnover — you pay the cost of rebuilding it from zero. | Netscape’s decision to rewrite the browser from scratch (the project that became Mozilla): Joel Spolsky called it “the single worst strategic mistake that any software company can make.” Three years of development thrown away. The Cultural Revolution of software: destroying institutional knowledge in pursuit of purity. |
12. 11. The Great Leap Forward: When Ambition Kills
The Great Leap Forward (1958–1962) was Mao’s attempt to industrialize China overnight. It caused the largest famine in human history (15–55 million deaths). It is the ultimate case study in what happens when ambition outpaces capability, when metrics replace reality, and when no one can tell the leader the truth. Every startup failure mode is present, amplified to civilizational scale.
| Concept | Maoist Definition | As a Startup Mental Model | Example |
|---|---|---|---|
| The Great Leap Forward | A campaign to transform China from an agrarian economy into an industrial power in five years through mass mobilization. Backyard steel furnaces, communal farming, absurd production targets. The ambition was transformative; the execution was catastrophic. | The “we’re going to 10x the company in one year” bet. Hiring 500 people in 6 months. Launching 5 products simultaneously. Entering 10 markets at once. The Great Leap Forward is what happens when a leader confuses ambition with capability and speed with progress. | Fast (the payments company): raised $100M+, hired aggressively, expanded to multiple markets simultaneously, and collapsed within 18 months. The Great Leap Forward of fintech: the ambition was real, the capability was not, and no one told the CEO the trajectory was unsustainable. |
| Backyard Steel Furnaces | Mao ordered peasants to build small steel furnaces in their backyards to meet production targets. The peasants melted their farming tools to produce useless pig iron. They met the steel targets but destroyed their agricultural capacity. The metric was achieved; the actual goal was annihilated. | Optimizing the metric at the expense of the thing the metric was supposed to measure. Hitting the revenue target by signing bad-fit customers who churn in 3 months. Hitting the hiring target with unvetted candidates. Hitting the feature target by shipping broken code. The metric is achieved; the business is destroyed. | The startup that hits its ARR target by signing annual contracts with deep discounts and generous terms — then discovers that the unit economics are negative on every deal. The steel target was met. The farming tools (sustainable economics) were melted. Backyard steel furnace: vanity metrics that destroy real value. |
| Reporting Inflation (Fang Wei) | Local officials reported impossibly high grain yields (10x actual production) because reporting the truth meant punishment. Mao believed the reports. The state requisitioned grain based on the inflated numbers, leaving nothing for the peasants. The information system killed millions. | When the team inflates metrics to please leadership, and leadership makes resource decisions based on the inflated metrics. Sales pipeline that’s 80% fantasy. User engagement metrics that count bots. Revenue projections based on “committed” deals that haven’t signed. The information system is lying, and decisions based on lies are fatal. | The startup that raises its Series B on projected revenue that’s 3x actual pipeline. Hires 50 people based on the projection. The revenue doesn’t materialize. Layoffs follow. The information distortion (inflated pipeline) created a real consequence (over-hiring followed by cuts). Fang wei: reporting inflation kills. |
| The Peng Dehuai Problem | Marshal Peng Dehuai, a hero of the revolution, privately wrote to Mao criticizing the Great Leap Forward. Mao denounced him as a rightist and purged him. The message to every other leader: don’t tell the truth. The famine accelerated because the one person who spoke honestly was destroyed. | When the board member, co-founder, or senior executive who raises legitimate concerns about the company’s direction is punished or pushed out. The Peng Dehuai problem: the person who could have prevented the catastrophe is the first casualty. After them, no one else dares speak. | WeWork: multiple board members and executives raised concerns about Adam Neumann’s leadership and spending. Each was sidelined or removed. By the time the IPO filing exposed the reality, the internal truth-tellers were all gone. The Peng Dehuai problem: destroy the messenger and the message disappears, but reality doesn’t. |
13. Synthesis: The Maoist Startup Playbook
Maoism’s mental models divide cleanly into two categories: the guerrilla playbook (brilliant underdog strategy) and the governing failures (what happens when the guerrilla tries to run a country). Both are instructive.
The Guerrilla Playbook (Use This)
- Surround the cities from the countryside — start where the incumbent isn’t. Win the periphery, then encircle the core.
- Protracted war — survival is strategy. Don’t try to win quickly. Outlast the competition through three phases: survive, build, attack.
- Mass line — from the users, to the users. The best product intelligence comes from the people who use your product. Synthesize it, ship it, repeat.
- Guerrilla warfare — don’t fight the incumbent’s war. Concentrate force on the one thing you can win. Retreat when necessary. Control the tempo.
- United front — ally with anyone against the main competitor. Maintain independence within alliances. Isolate the incumbent before attacking.
- Self-reliance — build a business that can survive without external inputs. Revenue over fundraising. Organic over paid.
- People’s war — GTM is everyone’s job. Arm your users with tools to build on your platform. The community is the army.
- On Practice — ship to learn. Theory is nothing without practice. The spiral of knowledge requires doing, not just thinking.
The Anti-Playbook (Avoid This)
- The Great Leap Forward — don’t confuse ambition with capability. Scaling faster than your competence allows is the most common cause of startup death.
- Reporting inflation — when the information system lies, every decision is wrong. Build a culture where truth is rewarded, not punished.
- The Cultural Revolution — don’t disrupt your own organization faster than it can absorb change. Internal disruption without guardrails is self-destruction.
- The Peng Dehuai problem — protect the truth-tellers. The person who tells you what you don’t want to hear is the most valuable person in the room.
Mao won the revolution by being the greatest guerrilla strategist in history. He then proceeded to demonstrate, at catastrophic scale, what happens when guerrilla instincts are applied to governance. The founder who can distinguish between the two modes — guerrilla strategy for building, institutional discipline for scaling — has access to the full Maoist toolkit without the Maoist body count.