What Is Idea Generation? Methods, Templates, and an Exercise
Idea generation is the deliberate production of multiple possible solutions before evaluation. Use practical methods, prompts, and a worked startup exercise.

Idea generation is the deliberate production of multiple possible answers to a defined question. In business, the output is not “the winning idea.” It is a varied set of options that can be evaluated and tested.
The process works best when generation and judgment happen at different times. If every idea is criticized the moment it appears, the group stays close to familiar solutions. If ideas are never evaluated, the session produces a wall of notes and no decision.

Define the Question Before Generating Ideas
Use a focused prompt:
How might we help [specific customer] achieve [outcome] when [situation or constraint]?
“How might we grow?” is too broad. “How might we help first-time managers prepare useful one-to-one meetings without adding another weekly tool?” gives the session a customer, job, and constraint.
Write the evidence behind the prompt. If the problem comes only from internal opinion, interview customers before treating it as a priority.
Seven Practical Idea-Generation Methods
1. Problem decomposition
Break the workflow into trigger, inputs, steps, handoffs, exceptions, and result. Generate options for each part rather than trying to redesign everything at once.
2. Constraint removal
Ask what you would do if a specific constraint disappeared: no meetings, no new software, one-day delivery, or no access to sensitive data. Then ask which part of that answer is practical now.
3. Analogy transfer
Choose another industry that handles a similar job. Identify the principle—not the surface feature—and adapt it. A restaurant reservation queue and a software support queue may share demand-prioritization logic without sharing the same product.
4. Reverse assumptions
List what the team assumes must be true, then reverse one item. If “customers must complete a long intake form,” ask how the service would work if the provider gathered the information during delivery.
5. SCAMPER prompts
Explore what you can substitute, combine, adapt, modify, put to another use, eliminate, or reverse. Use the prompts to vary an existing workflow, not as proof that the variation is valuable.
6. Silent brainwriting
Participants write ideas independently before sharing. This reduces early anchoring on the loudest voice and gives everyone time to contribute.
7. Evidence remix
Put verified customer facts on separate cards: trigger, workaround, objection, budget owner, desired result, and constraint. Combine cards into possible offers. Reject any combination that requires inventing evidence.
A Reusable 45-Minute Workshop
- Five minutes: state the customer problem and evidence.
- Five minutes: list constraints and assumptions.
- Ten minutes: generate silently using two methods.
- Ten minutes: share and group related options.
- Ten minutes: score the most distinct options.
- Five minutes: assign one evidence test to each finalist.
Capture every idea in the same format: customer, trigger, proposed result, delivery method, biggest assumption, and next test.
Worked Exercise: From Observation to Options
Suppose interviews reveal that independent consultants delay invoicing because project details are scattered across calendars, notes, and email. That is an illustrative problem statement, not reported market data.
The team generates options across different shapes:
- a weekly concierge that prepares draft invoices;
- a calendar-to-invoice checklist and template;
- a productized billing-setup service;
- a lightweight tool that assembles draft line items;
- a reminder workflow triggered by project milestones;
- a client-facing closeout form that captures billable changes.
Now identify the main assumption in each. The concierge assumes willingness to share records. The template assumes process confusion is the bottleneck. The tool assumes integration is feasible and valuable. Each requires a different test.
Score Ideas Without Pretending the Numbers Are Truth
Use a one-to-five scale and add the evidence supporting every score.
| Criterion | Evaluation question |
|---|---|
| Problem strength | Is the problem recent, repeated, and consequential? |
| Customer access | Can we reach the user and decision-maker? |
| Distinct value | Why would they switch from the current workaround? |
| Feasibility | Can we deliver a useful version safely? |
| Economics | Could price, cost, and frequency support the model? |
| Learning speed | Can we test the riskiest assumption quickly? |
A score is a comparison aid, not objective validation. A high-scoring idea still needs customer evidence.
Bridge From Ideas to Validation
Turn each finalist into a test statement:
We believe [customer] will take [specific action] for [result] when [trigger]. We will test this with [method] and reconsider if [evidence condition].
Then choose the smallest honest test: interview, manual sample, paid diagnostic, landing page with relevant traffic, pre-sale with clear terms, or limited pilot.
The product ideation process explains how to move from discovery through prioritization. The customer validation guide helps judge the strength of the resulting evidence. If your problem is having no starting direction at all, use the exercises for starting a business with no ideas.
Good idea generation increases the range of possible actions. Good validation decides which possibility deserves more investment.

Martin Bell
Founder of 100 Tasks. Martin Bell has launched or supported 120+ startups and turned Rocket Internet venture-building discipline into a step-by-step system used by 25,000+ founders and startups.


