Entrepreneurship and Innovation
Entrepreneurship is the act of organizing resources to pursue an opportunity whose value exceeds the sum of its parts. Innovation is the process of turning invention into value. This skill covers the decision frameworks used to recognize opportunities, structure ventures, understand disruption, and build platform businesses — drawing on Christensen's disruption theory, Drucker's entrepreneurship principles, Ma's platform-scaling playbook, and the lean startup tradition.
Agent affinity: christensen (disruption theory and jobs-to-be-done), ma (platform businesses and scaling)
Concept IDs: bus-entrepreneurial-process, bus-business-planning, bus-startup-growth
The Entrepreneurship Toolbox at a Glance
| # | Technique | Best for | Key signal |
|---|---|---|---|
| 1 | Jobs-to-be-done | Understanding customer motivation | Demographic segments do not predict purchase |
| 2 | Disruption framework | Interpreting competitive threats | A cheaper alternative is gaining share on "worse" products |
| 3 | Sustaining vs disruptive innovation | Choosing where to invest | Core customers want more features; margins are shrinking |
| 4 | Minimum viable product (MVP) | Validating a hypothesis | Cost of being wrong is lower than cost of being late |
| 5 | Customer development | Finding product-market fit | Product exists but customers are not buying |
| 6 | Platform business model | Scaling beyond linear unit economics | Two or more sides could value each other |
| 7 | Network effects | Defending a lead | Winner-take-most dynamics are visible |
| 8 | Unit economics | Knowing if the business can work | Growth is high but profit is absent |
| 9 | Pivot discipline | Changing direction with intent | Current path is failing faster than expected |
| 10 | Drucker's seven sources | Finding innovation opportunities | Need ideas to even evaluate |
Technique 1 — Jobs-to-be-Done
Pattern: Customers do not buy products; they hire products to do a job. Understand the job well enough to design the product backward from it. The job is defined by the progress the customer is trying to make in a specific circumstance, not by demographics or product categories.
Historical basis. Christensen developed the jobs framework in The Innovator's Solution (2003) and Competing Against Luck (2016) after observing that successful innovators routinely solved problems that demographic segmentation could not surface.
Worked example. A fast-food chain wants to sell more milkshakes. Traditional analysis (demographics, flavor preferences) produced improvements that did not move the needle. Christensen's team interviewed morning buyers and found the "job" was: "I have a long, boring commute, one free hand, and I will be hungry by 10 AM. I need something that takes 20 minutes to finish, keeps me occupied, and does not make me hungry." The competition was not other milkshakes but bagels (messy), donuts (too fast to finish), and coffee (not filling). Thicker milkshakes with added fiber, sold in the drive-through lane, grew the morning segment substantially.
Diagnostic use. For any product struggling to find traction, ask: "When a customer hires this, what job are they hiring it for, and what else are they considering?" The answer reveals the real competition and the real value.
Technique 2 — The Disruption Framework
Pattern: Disruptive innovation enters a market at the low end or in a new segment that incumbents ignore because the product is "worse" on the metrics incumbents' customers value. The disruptor improves over time and eventually serves the mainstream market, but incumbents cannot respond because responding would harm their core business.
Historical basis. Clayton Christensen's The Innovator's Dilemma (1997) analyzed disk drives, steel, and retail to identify the pattern: incumbents listen to their best customers, invest in sustaining innovations, and fail to notice that a "worse" product is better on a new dimension (cost, simplicity, convenience) and is improving fast.
The pattern in four stages.
- Foothold. Disruptor enters a segment the incumbent ignores because margins are too low.
- Upmarket march. Disruptor improves until it meets the needs of the incumbent's mainstream customers.
- Incumbent dilemma. The incumbent cannot respond without harming its more profitable business.
- Displacement. The disruptor serves the mainstream market at structurally lower cost.
Critical caveat. Not every new entrant is a disruptor. Uber is an innovator, but it entered with a product that was better on the metrics existing customers cared about (convenience, availability). True disruption enters worse-and-cheaper and improves. Mis-diagnosing a threat as disruption when it is actually sustaining innovation is a common error.
Technique 3 — Sustaining vs Disruptive Innovation
Pattern: Sustaining innovation improves existing products along dimensions existing customers already value. Disruptive innovation creates new markets by bringing new dimensions to the fore. Both are valuable; they are managed differently.
Decision table.
| Dimension | Sustaining | Disruptive |
|---|---|---|
| Customer | Existing | New or under-served |
| Value dimension | More of what they already want | Different dimension (cheaper, simpler, more convenient) |
| Organization fit | Core business | Separate unit, protected from core incentives |
| Metrics | Existing (revenue, share, margin) | New (adoption, learning rate) |
| Expected timeline | Short-to-medium | Medium-to-long |
Christensen's key finding. Incumbents are good at sustaining innovation and bad at disruptive innovation, not because they lack talent but because their resource allocation process correctly rejects disruptive projects: small markets, low margins, uncertain customers. The same process that protects the core business blocks the response to disruption. The fix is structural: pursue disruption in a separate unit with separate metrics and separate resource allocation.
Technique 4 — Minimum Viable Product (MVP)
Pattern: Build the smallest version of the product that lets you validate the core hypothesis, then measure whether customers actually want it. An MVP is a tool for learning, not a scaled-down product.
Key discipline. The MVP must be minimal enough to ship quickly but viable enough to produce a real purchase or use decision. An MVP that nobody can use does not test anything; an MVP that tests fifteen features at once cannot isolate which feature mattered.
Worked example. A software team has a hypothesis: "Customers will pay for automated expense categorization." Rather than build the full system, they build a minimal web form where customers upload CSVs and the team categorizes them manually overnight. If customers pay, the hypothesis is validated and automation becomes worth building. If customers do not pay even when the categorization is perfect, the hypothesis is wrong and no amount of automation will save it.
When NOT to use. When the cost of a public failure exceeds the cost of building the full product, or when the minimum viable version requires regulatory approval that cannot be shortcut. Hardware, medical devices, and regulated financial products have higher MVP floors.
Technique 5 — Customer Development
Pattern: In parallel with product development, actively discover who the customer is, what they value, and how they currently solve the problem. Customer development is sales-team work done by founders before there is a sales team.
Four stages (Steve Blank, following the lean startup tradition):
- Customer discovery — interviews to find who has the problem
- Customer validation — small-scale sales to confirm they will pay
- Customer creation — scaling to build the market
- Company building — transitioning from learning to execution
Discipline. The firs