1.4 How Do Business Ideas Originate?
Where business ideas come from, the risk of bringing a product to market, and the design-thinking process.
The notebook
Saturday at the soccer league, and our seller watches the sideline rather than the game. A parent loses hold of a folding chair, a phone, and two juice cartons at once. A coach asks the group chat for a snack volunteer, third week running. A cooler sits forgotten in a car two parking lots away. He writes all three down. Topic 1.4 explains how observations like those become businesses, and it carries two skills: accounting for where product ideas originate and why anybody accepts the risk of chasing one, and applying the process that turns an observation into a tested idea.
The entrepreneur
An entrepreneur develops a new business and takes on both the risks and the possible rewards. Our seller has fitted that description since Topic 1.1 without ever using the label, having started the corridor operation, absorbed a price war, and pocketed whatever remained. Taking the risk is the entire difference between an entrepreneur and somebody with a suggestion. Ideas begin as opportunities, and an opportunity is a customer problem, need, or want some firm could answer. A notebook of complaints is a list of them.
Where ideas come from
Three strategies find opportunities, and none of them belongs only to startups, since established firms run identical plays hunting their next product.
- Watch and ask. Firms observe buyers, interview them, and poll them. Sitting on a sideline writing things down is observation, asking five parents what they wish existed is interviewing, and a one-question poll in a team chat is a survey.
- Research. Market research collects information on buyers, rivals, and the market, which is how gaps surface, a gap being an unmet need nothing currently on sale serves. Technical research asks a separate question: can this actually be built and delivered with what exists today?
- Experiment. Capabilities develop by attempting things, and plenty of products are discovered by accident while a team builds something else.
Each tool buys a different kind of truth. Observation records what people do, which frequently differs from what they say. Interviews recover the reasoning underneath the behavior. Surveys count, turning an impression into a proportion. And a crowded market can still hide a gap, since a town with three pizza places and nothing after ten at night has an unserved need sitting in the timing rather than in the food.
Risk and reward
New products consume financial, physical, and human resources, all of which cost something, and nothing promises that sales will cover them. That holds identically for a teenager's savings and a corporation's product program. His version: permit and cooler cost cash, stock ties up more, and a Saturday behind a table is a Saturday unavailable for anything else. If parents ignore him, both are spent for nothing.
Three reasons justify accepting that, and the course treats them as equals. Future profit. The satisfaction of fixing something. And the chance to work at something you would choose anyway. Most founders run on a blend of all three, and a scenario can turn on whichever one it names.
Design thinking: validate the problem
Design thinking is a repeatable route from a raw problem to a tested idea, and it opens with observation, interviews, and surveys. The first stage identifies a problem and then validates it, and validation has three specific requirements here: the problem is real, it can be stated clearly, and more than one customer carries it.
One parent dropping juice is an anecdote, so he asks. Across two Saturdays he speaks with twenty parents and four coaches. Seventeen parents describe the same halftime scramble, in which children need food and drink mid-game, nobody tracks whose turn it is, and the nearest store is ten minutes away by car. All three requirements are now satisfied.
Develop a solution
Stage two produces a candidate solution and runs on brainstorming, sketching, and prototyping. Brainstorming lists possibilities without judging any of them, because early judgment kills the odd ideas that occasionally win. His list holds a permanent stand at every field, a cart circulating between fields, and a pre-ordered box for each team.
The stand needs capital he lacks and the cart needs hours he lacks, so the box wins on fit with his resources. He draws it, then builds a prototype, meaning an early rough version made to explore an idea and collect reactions, which in his case is a cardboard box with a menu taped to the lid.
Validate the idea with an MVP
Sketches persuade the person holding the pencil. Customers have to supply the evidence, so stage three tests the idea on a minimum viable product, the stripped-down version carrying only core features, which may amount to no more than a drawing, a written description, or a model.
Students misread the word minimum every year. It counts features, not care. Only the core is under test, and a shoddy build would corrupt the very reactions the exercise exists to collect.
His MVP is a single box for one team on one Saturday, ordered through the group chat. Alongside it he writes a business hypothesis, a claim the test will confirm or reject: five families at minimum will pre-order at two dollars. That is specific enough to fail in public, whereas hoping people enjoy it survives every possible result and teaches nothing. Seven families order, two request fruit, and a coach asks about a flat team rate.
The cheap test at any size
Nothing structural changes at scale. A snack manufacturer testing a flavor bakes a limited batch, places it in a handful of stores for a month, and reads the receipts before committing a production line. That batch is an MVP with a corporate badge on it. Large firms test for the reason a teenager tests: a cheap experiment protects an expensive commitment.
The method proves itself on a failure. One order instead of seven costs a Saturday and a cardboard box. The same lesson learned after buying a trailer of stock costs whatever the trailer cost, which is why the discipline is to spend heavily only once the cheap tests have passed.
Recap and essential knowledge
Ideas come from watching, asking, researching, and experimenting. Risk is real and gets accepted for profit, for satisfaction, or for passion. Design thinking validates the problem, then the idea, while errors are still cheap. Topic 1.5 asks what this operation actually stands for.
| Section | Essential knowledge |
|---|---|
| The entrepreneur | 1.4.A.1 |
| Where ideas come from | 1.4.A.2 |
| Risk and reward | 1.4.B.1, 1.4.B.2 |
| Design thinking: validate the problem | 1.4.C.1 |
| Develop a solution | 1.4.C.2 |
| Validate the idea with an MVP | 1.4.C.3 |
Worked examples
Testing a business hypothesis with an MVP
Judge whether an MVP result confirms or rejects a stated business hypothesis.
Before the first snack box went out, our seller wrote down a hypothesis: five families or more from this team would pre-order, each paying two dollars. Twenty parents were interviewed beforehand and seventeen described the same halftime problem. On the Saturday, seven families ordered. Decide whether both validations passed and by how much.
- Parents interviewed
- 20
- Parents reporting the halftime problem
- 17
- Hypothesis threshold
- 5 pre-orders
- Pre-order price
- $2.00
- Actual pre-orders
- 7
1. Measure the evidence for the problem
The first validation asks whether the problem is real, clearly defined, and shared by multiple customers. Seventeen of twenty parents describing the same scramble is a share of eighty-five percent.
\text{share}=\frac{\text{parents reporting the problem}}{\text{parents interviewed}}
2. State the hypothesis threshold in money
Five pre-orders at two dollars each is the minimum result that would count as a pass.
\text{threshold revenue}=\text{minimum orders}\times\text{price}
3. Compute the actual result
Seven families at two dollars each produced fourteen dollars of pre-orders on a single team on a single Saturday.
4. Compare the result with the threshold
Fourteen dollars against a ten dollar threshold clears the bar by four dollars, which is forty percent above the level the hypothesis demanded.
\text{margin above threshold}=\frac{\text{actual}-\text{threshold}}{\text{threshold}}
Answer
Both validations pass; the MVP beat its threshold by 40 percent. Eighty-five percent of interviewed parents confirmed the problem, and seven orders against a threshold of five confirmed the idea with forty percent to spare.
Why it matters
The hypothesis was worth writing precisely because it could have failed in public. Had two families ordered, the whole lesson would have cost one Saturday and one cardboard box instead of a trailer of stock.
Key terms
6 common mistakes on 1.4
The wrong moves students actually make on these questions, why each one is wrong, and what to do instead. Part of the practice tier.
See what is includedEssential knowledge covered
1.4.A.1 · 1.4.A.2 · 1.4.B.1 · 1.4.B.2 · 1.4.C.1 · 1.4.C.2 · 1.4.C.3