10. Choosing the Right Idea

A founder does not choose the right idea by finding the idea with the biggest dream attached to it. You choose by comparing evidence, speed of learning, founder fit, market access, and the quality of the first wedge.

The core idea-choice question is: which idea gives us the best combination of painful customer reality, fast learning, founder advantage, reachable buyers, and room to become a meaningful company?

At the beginning, the “right” idea is rarely the final company. It is the best learning vehicle: specific enough to test, painful enough to matter, reachable enough to sell, and expandable enough to become meaningful if it works.

Compare Ideas By Tradeoff, Not Excitement

Most founders compare ideas badly. They compare the exciting version of one idea with the realistic version of another. Or they compare the future TAM of one idea with the first customer of another. That creates false confidence.

Compare each idea on the same dimensions:

Dimension	Question
Passion vs evidence	Do you love the problem, and do customers show behavior that supports it?
Speed vs ambition	Can you learn quickly without shrinking the long-term possibility too much?
Market size vs entry wedge	Is the first wedge small enough to win but connected to a larger market?
Revenue speed vs defensibility	Can you earn early revenue without choosing a dead-end service model?
Founder fit vs trendiness	Are you suited to this market, or are you chasing what is fashionable?
Ease of launch vs long-term upside	Is it easy because it is focused, or easy because it is shallow?

A good idea may not win every dimension. What matters is whether the weaknesses are known and testable.

The Best Idea Is Often The Narrowest Useful One

Founders often resist narrowing because it feels less ambitious. In reality, narrowing is how you make ambition executable.

Weak idea:

We help Indian SMBs manage finance.

Stronger wedge:

We help multi-location cloud kitchens reconcile aggregator payouts, UPI collections, refunds, commissions, and GST-ready records every week.

The second idea is narrower, but it is easier to test. You know whom to call, what pain to ask about, what current workflow to inspect, what outcome to promise, and what a pilot might look like.

Narrowing does not mean you stay small forever. It means you enter through a door that customers recognize.

How To Choose A Wedge

Define your first wedge across seven choices:

Choice	Example question
First customer	Which exact segment has the sharpest pain?
First use case	Which one job will you solve first?
First workflow	Where does the pain show up in daily or weekly work?
First geography	Does one city, region, or market context make adoption easier?
First industry	Which industry has repeated pain and reference value?
First buyer type	Is the buyer owner-led, department-led, finance-led, IT-led, or consumer-led?
First channel	How will you reach the first twenty qualified prospects?

The wedge should be narrow enough that your message feels written for the customer. If the customer reads your landing page and says, “This is exactly for people like us,” you are closer. If they say, “This is broadly useful,” you are probably too vague.

Choosing Between Two Good Ideas

If two ideas both look promising, choose the one with the fastest path to high-quality evidence.

Ask:

Which idea can produce a real customer conversation this week?
Which idea can get a paid or manual pilot fastest?
Which idea has a buyer we can name?
Which idea gives us more founder advantage?
Which idea has clearer expansion if the wedge works?
Which idea would still interest us after six months of messy execution?
Which idea has a failure mode we can survive?

The last two questions matter. You are not choosing a topic for a weekend project. You are choosing a problem you may live with for years.

Passion Versus Evidence

Passion matters because startups are long. But passion without evidence becomes stubbornness.

Use this table:

Situation	What to do
High passion, high evidence	Continue, but keep testing assumptions.
High passion, low evidence	Run sharper validation before building.
Low passion, high evidence	Ask if a co-founder or business model makes it worth pursuing.
Low passion, low evidence	Kill or park it.

Do not choose an idea only because investors like it. Do not reject an idea only because it looks boring. Many excellent companies begin in unglamorous workflows.

Speed Versus Ambition

The best early idea is not always the biggest idea. It is the idea that lets you learn the most important truth quickly.

Fast learning looks like:

Customer calls this week.
Manual delivery this month.
A paid pilot without building everything.
A small but real workflow where value can be measured.
A channel you can test immediately.

Slow learning is acceptable only if the potential reward and founder advantage are unusually strong. If the idea requires six months of building before any customer can react, be very sure the technical risk is the real risk. Often it is not.

When To Kill An Idea

Killing an idea is not failure. It is capital preservation. It saves time, reputation, energy, and attention for better opportunities.

Kill or park an idea when:

You cannot identify a buyer after serious discovery.
The pain is real but not urgent.
The customer will use it only if it is free.
Distribution depends on a channel you cannot access.
The first wedge requires too much capital before learning.
Regulation, procurement, or operational complexity is beyond your current ability.
You are continuing mainly because you have already spent time on it.
The idea repeatedly produces compliments but no behavior.

Do not kill an idea only because one person dislikes it. Do not continue only because one person praises it. Look for repeated behavior across the right customer segment.

When you stop, preserve the learning:

Which customers had the pain?
Which segment did not care?
Which language created interest?
Which objections repeated?
Which adjacent problem appeared stronger?
Which relationships should you maintain?

Many good startups emerge from a killed idea’s research notes.

How To Communicate With Early Users When You Stop

If you ran interviews, pilots, or manual tests, do not disappear.

Send a short note:

Thank them for their time.
Say what you learned.
Explain that you are pausing, narrowing, or changing direction.
Share anything useful you can.
Ask permission to stay in touch if the problem becomes relevant later.

This protects reputation. In the Indian ecosystem, trust compounds. A founder who handles a stopped idea maturely is easier to trust on the next one.

India Angle

For Indian founders, the right idea often depends on distribution and trust as much as product. A founder with deep access to clinics, schools, factories, accountants, exporters, creators, or local retailers may have a better starting point than a founder chasing a larger but unreachable category.

India also punishes vague “SMB” thinking. A textile exporter in Surat, a coaching institute in Kota, a D2C brand in Bengaluru, a kirana wholesaler in Indore, and a CA firm in Mumbai are not one customer segment. Their budgets, workflows, trust networks, and buying triggers differ.

Choose a wedge where the customer reality is specific enough to learn from quickly.

Also consider:

Does the buyer prefer software, service, financing, or bundled outcome?
Does the customer need local language support?
Does sales require a trusted intermediary?
Is payment monthly, annual, commission-based, per transaction, or cash-flow-linked?
Is there a compliance deadline or seasonal trigger?
Can one customer become a reference for the next ten?

Decision Memo

Before committing to an idea, write a one-page memo:

Section	What to write
Idea	One sentence with customer, problem, and outcome.
First wedge	The first customer, workflow, buyer, and channel.
Evidence	What you have seen, heard, or tested.
Weakest assumption	The thing most likely to kill the idea.
Seven-day test	The next action that will improve or invalidate that assumption.
Stop rule	What result would make you pause, narrow, or kill the idea?
Expansion path	If the wedge works, what adjacent customer or workflow comes next?
Founder fit	Why you can learn faster here than a generic team.

This memo is not for investors. It is for founder clarity. If you cannot write it simply, you probably have not chosen the idea yet.

A Final Selection Process

Use this process for your top three ideas:

Write each idea as customer, problem, outcome.
Define the first wedge for each.
Score pain, buyer clarity, reachability, founder fit, and speed-to-test.
Identify the weakest assumption.
Run one test per idea if possible.
Compare evidence, not excitement.
Choose one idea for a focused sprint.
Set a review date and stop rule.

Do not keep three ideas alive forever. Exploration is useful. Endless optionality becomes avoidance.

Decision Review Meeting Agenda

If there is more than one founder, run a short decision meeting before committing.

Agenda:

Restate each idea as customer, problem, outcome.
Review evidence only; park opinions unless tied to evidence.
Compare first wedges, not future visions.
Identify the riskiest assumption for each idea.
Name the fastest meaningful test for each idea.
Discuss founder energy and access honestly.
Choose one active idea and one parked backup.
Write the commitment contract and review date.

Use this rule during the meeting: no one is allowed to defend an idea only with adjectives. “Huge,” “exciting,” “obvious,” “needed,” and “AI-first” are not evidence. Bring customer stories, current workarounds, buyer signals, channel tests, or founder advantage.

The One-Month Commitment Rule

Once an idea has enough evidence to continue, give it a serious sprint. Many founders quit too early because the first ten conversations feel messy, or they keep switching ideas because the next idea feels cleaner.

Commit for one month if:

You can reach the target segment.
Several customers described recent pain.
There is a plausible buyer or commitment path.
You have a clear riskiest assumption to test.
The idea still feels worth learning about after bad calls.

During that month, do not redesign the idea every day. Run a disciplined sequence:

Week 1: refine segment and interview 10 people.
Week 2: test the current workaround and buyer map.
Week 3: test a manual solution, prototype, or offer.
Week 4: ask for payment, pilot, data, intro, or workflow access.

At the end, decide with evidence. This protects you from both premature quitting and stubborn continuation.

30-Day Idea Sprint Board

Once you choose an idea, turn the first month into an operating board.

Column	What belongs here
Target segment	The exact customer profile for this sprint.
Open assumptions	Pain, buyer, access, trust, price, workflow, delivery.
Customer conversations	Names, roles, dates, and what must be learned.
Evidence captured	Workarounds, artifacts, quotes, buyer maps, data, payments.
Tests running	Outbound, interview, landing page, manual service, prototype, pilot.
Decisions pending	Continue, narrow, change, stop, build, sell, price.
Next week change	One change to ICP, message, test, product, or channel.

Review the board every Friday. If the board has many opinions and little evidence, you are not running a startup sprint. You are thinking about a startup sprint.

Choosing A Fundable Versus Bootstrappable Idea

Not every good idea should become a venture-backed startup. That is not an insult. It is strategy.

Path	Idea characteristics
Bootstrappable	Clear buyer, early revenue, modest market size, service component, profit potential, slower growth acceptable.
Venture-backed	Large market, fast growth potential, strong retention, scalable distribution, high-margin product, defensibility path.
Services-to-product	Pain is real, delivery is manual today, repeatable workflow can become software later.
Community-led	Strong identity, repeated engagement, clear monetization or distribution advantage.
Deeptech	Technical risk is central, long development cycle, grants or patient capital may be needed.

Choose the funding path that fits the idea. A bootstrappable business forced into a venture story can become unhealthy. A venture-scale market run with small-business ambition can underinvest. A services business pretending to be software can mislead founders and investors.

The Founder Energy Test

The right idea must survive a less glamorous question: can you tolerate the daily reality?

Ask yourself:

Am I willing to talk to this customer segment every week?
Am I willing to solve their boring operational problems?
Am I comfortable with the sales motion this market needs?
Do I respect the customer, or only the market size?
Will I still care if investors ignore the category for a while?
Can I recruit a team into this mission honestly?
Does this idea fit my risk appetite, financial situation, and life constraints?

Founder energy is not the same as excitement. Excitement is loud at the start. Energy is what remains after rejections, bugs, slow sales, and confusing customer feedback.

A Real Decision Looks Like A Tradeoff

If the chosen idea has no tradeoff, you probably have not looked closely enough.

Write:

We are choosing this customer, so we are not serving that customer yet.
We are solving this workflow, so we are not building the broad platform yet.
We are using this channel, so we are not pretending every channel works.
We are pricing this way, so we accept these buyers may say no.
We are taking this funding path, so we accept this growth expectation.

This clarity helps the team say no. Early startups die from vague yeses as much as from bad ideas.

Idea Selection Decision Gate

Use a decision gate before committing to an idea for the next serious sprint.

Gate	Pass condition
Customer	We can name the first customer segment precisely.
Problem	Several qualified customers described a recent painful occurrence.
Buyer	We know who pays, approves, blocks, or owns the outcome.
Access	We can reach more customers like this without waiting for luck.
Wedge	We can define a narrow first workflow, promise, and use case.
Evidence	At least one behavior signal exists: intro, workflow access, pilot interest, payment, repeated use, or data share.
Founder fit	We have a learning or execution advantage in the hard part.
Next test	The next 7-30 day test is obvious and measurable.

If an idea fails more than two gates, do not commit yet. Keep learning or choose a narrower wedge.

Reversal Criteria

Before you commit to an idea, define what would make you reverse the decision. This is not negativity. It protects judgment once identity, sunk cost, and public commitment enter the room.

Write reversal criteria in advance:

Area	Reversal signal
Pain	After 20 qualified conversations, the problem is interesting but not urgent.
Buyer	Users care, but no budget owner accepts responsibility for the outcome.
Access	You cannot reach the segment repeatedly without expensive luck.
Trust	Buyers will not share data, run a pilot, introduce colleagues, or take a low-risk next step.
Pricing	Customers like the product only below a price that cannot support the business.
Delivery	Manual delivery teaches you that the work is too custom to become repeatable soon.
Founder fit	The team consistently avoids the customer, channel, or operating reality.

Reversal criteria should be measurable enough to stop debate. “We feel less excited” is not a reversal signal. “After four weeks, no buyer agreed to a paid pilot or serious workflow access” is a signal.

Pivot, Narrow, Or Kill?

When evidence disappoints you, do not jump straight to “kill the idea.” Decide what kind of change the evidence suggests.

Evidence pattern	Likely move
Pain is real but segment is broad	Narrow the ICP.
Users care but buyers do not	Change buyer, package, or use case.
Buyer exists but price is too low	Move upmarket or bundle a larger outcome.
Product is useful but hard to adopt	Simplify onboarding or start with a service layer.
Distribution is weak	Test a channel, partnership, community, or wedge with better access.
Trust is weak	Add proof, references, guarantees, or lower-risk entry point.
No repeated pain after serious discovery	Kill or park the idea.

This distinction matters. Many founders kill too early because the first version is wrong. Others pivot endlessly because they refuse to admit the problem is weak. The mature move is to let evidence decide the type of change.

Tie-Breakers Between Good Ideas

When two ideas both look promising, compare them by operating reality:

Tie-breaker	Prefer the idea where…
Access	You can reach customers faster.
Learning speed	You can run a meaningful test this week.
Buyer clarity	The payer is easier to identify.
Pain frequency	The problem repeats often.
Trust burden	The first version needs less sensitive trust.
Founder energy	You can tolerate the boring daily work.
Revenue path	You can test payment earlier.
Strategic upside	The wedge can expand into a larger market.

Do not choose only the easiest idea. Choose the idea where fast learning and long-term ambition can coexist.

The No-Regret Kill

Killing an idea should preserve learning.

Before archiving it, write:

What we believed.
What evidence changed our mind.
Which segment we studied.
Which customer language was useful.
Which channel or source worked.
Which assumption failed.
What idea this learning points toward.

This turns a killed idea into an asset. Many good startups are built from the third or fourth serious version of an original problem area.

The Commitment Contract

Once an idea passes the gate, write a commitment contract:

Field	Decision
We are committing to	Customer, problem, wedge.
We are not doing yet	Adjacent segments, features, channels, geographies.
Sprint length	2-4 weeks.
Main test	What must be proven.
Success evidence	What behavior would increase confidence.
Stop/change evidence	What would force a change.
Review date	Calendar date.

This contract prevents daily emotional switching. The goal is not blind stubbornness. The goal is disciplined contact with reality.

Founder Calendar Test

An idea is only real when it changes the founder’s calendar. Before choosing, ask what the next two weeks will actually contain.

For a good idea, the calendar should contain:

Customer conversations with named people.
Outreach blocks to a specific segment.
Time to inspect current workflows, documents, tools, or workarounds.
A prototype, landing page, manual service, or offer test.
A weekly review of evidence and decisions.
Follow-ups asking for a commitment, not just feedback.

If the calendar contains mostly branding, domain search, pitch deck polishing, and product architecture, the idea may still be hiding from reality.

Two-Week Commitment Plan

Use this simple plan after choosing:

Day range	Work
Days 1-2	Write ICP, promise, weakest assumption, outreach list, and stop rule.
Days 3-7	Speak to 8-12 qualified people and capture current workflows.
Days 8-10	Test a concrete offer, manual solution, landing page, or prototype.
Days 11-13	Ask for a stronger commitment: paid pilot, data, intro, time, or workflow access.
Day 14	Decide: continue, narrow, change buyer, change channel, or stop.

This is the smallest serious idea commitment. If you cannot run this for an idea, you may not have chosen an idea yet; you may only have named a theme.

The Choice Memo

Before committing, write a choice memo. This is not for investors. It is for founder clarity.

Use this structure:

We are choosing:
[customer segment] with [specific problem] in [specific workflow].

We believe this is worth our next sprint because:
[3-5 evidence bullets].

The riskiest assumptions are:
[problem, buyer, channel, solution, revenue, trust].

We will not work on:
[adjacent customers, extra features, distracting channels].

In the next 14 days we will prove:
[specific behavior].

We will continue if:
[evidence threshold].

We will change or stop if:
[stop/change threshold].

The memo should fit on one page. If it takes five pages to explain why the idea is good, it is probably not clear enough yet.

One-Idea Focus Rules

Choosing an idea is painful because it means not choosing other ideas. Use focus rules to reduce daily switching.

For the next sprint:

One primary customer segment.
One painful workflow.
One main promise.
One acquisition channel to test first.
One main validation metric.
One weekly review date.

Allowed changes:

Narrowing the segment.
Rewriting the message based on customer language.
Changing the test if the current test cannot produce evidence.
Killing the idea if stop rules are hit.

Not allowed:

Adding unrelated features because a prospect asked once.
Switching to a new market because the first three calls were uncomfortable.
Rebranding before evidence.
Building a broad platform before a narrow workflow works.
Treating investor excitement as customer proof.

Focus does not mean stubbornness. It means giving reality enough time to answer.

Co-Founder Alignment Check

If there is more than one founder, the chosen idea must survive an alignment conversation.

Discuss:

Are we equally interested in this customer?
Do we agree on the first wedge?
Who owns customer discovery, sales, product, and operations this sprint?
What sacrifice are we making by choosing this idea?
What evidence would make each of us stop?
Are we choosing this because of evidence or because one founder is more excited?
Can we tolerate the boring daily work of this market?

Write disagreements explicitly. Early hidden disagreement becomes later resentment.

Commitment Milestones

After choosing, set milestones that force learning.

Milestone	Evidence required
7 days	5-10 qualified conversations or workflow inspections.
14 days	Clearer ICP, problem language, and riskiest assumption result.
30 days	Manual/prototype/pilot test with real customer behavior.
60 days	Repeatable evidence from one segment, not scattered anecdotes.
90 days	Revenue, repeated usage, or strong reason to continue without revenue.

The exact numbers can change by business type, but the rhythm should not. A founder should not spend months “exploring” without sharper evidence.

When To Keep Going Despite Messy Evidence

Not all early evidence is clean. Keep going when:

The problem is painful, but the first segment is slightly wrong.
Buyers are interested, but trust proof is missing.
Users care, and a buyer path is emerging.
Manual delivery works, but product shape is unclear.
Outreach is hard, but warm conversations reveal strong pain.
The market is messy, but customers repeatedly describe the same expensive workaround.

Stop or change when:

Customers cannot describe recent pain.
No one owns the problem.
No one will take a meaningful next step.
Every prospect needs a different custom solution.
You cannot reach the market without unsustainable effort.
You are continuing mainly because stopping would hurt your ego.

Choosing well is not about certainty. It is about committing to the idea with the best evidence-to-learning ratio.

The Idea Commitment Operating System

Once you choose an idea, the next danger is drift. Founders keep half-pursuing three ideas, changing the ICP every week, and calling it exploration. Exploration is useful only if it creates sharper commitment.

Create a simple operating system for the chosen idea:

Operating item	Decision
Chosen customer	The narrow segment you will study first.
Chosen pain	The exact problem, trigger, and current workaround.
Chosen wedge	The first workflow or outcome you will solve.
Excluded customers	Segments you will not chase yet.
Excluded features	Features you will not build yet.
Learning target	The riskiest assumption for the next 14 days.
Customer target	Number and type of conversations, pilots, or workflow inspections.
Evidence target	What behavior must happen for you to continue.
Stop/change rule	What evidence will make you narrow, change, or stop.
Review date	A fixed date when you revisit the decision.

This lets you commit without becoming stubborn. You are not promising to build the idea forever. You are promising to give one narrow version enough focused attention to learn something real.

Weekly Focus Review

Every week, ask:

Did we speak to the right customer segment?
What did customers do, not just say?
Did the same pain repeat?
Did we learn more about the buyer?
Did we learn more about distribution?
Did we get closer to a paid test, repeated usage, or strong workflow proof?
Are we drifting into a bigger, vaguer idea?
What will we deliberately not do next week?

The last question is important. Early teams die from too many plausible options. Strategy begins when you say no to things that are tempting but premature.

When A Better Idea Appears

New ideas will appear once you start talking to customers. Do not immediately switch. First classify the new idea:

New idea type	What to do
Same customer, same pain, sharper wedge	Consider narrowing toward it.
Same customer, adjacent pain	Park it unless the current pain is weak.
Different customer, same pain	Test only if reachability and buyer clarity improve.
Different customer, different pain	Put it in the backlog; it is a distraction for now.
Customer request from one loud prospect	Validate with others before changing direction.

A new idea is not automatically a pivot. Sometimes it is just anxiety wearing a clever costume.

The Founder Stamina Test

Before committing, ask yourself:

Can I spend the next 100 customer conversations in this market without resenting it?
Can I handle the buyer’s pace, language, objections, and trust-building requirements?
Can I keep learning if early calls are awkward or slow?
Do I respect the customer enough to solve their boring problems?
Would I still care about this problem if nobody praised the idea publicly?

Founder stamina is not motivational fluff. It affects how long you keep selling, how deeply you listen, how honestly you handle setbacks, and whether customers feel that you actually care about their world.

One-Idea Focus Contract

Choosing an idea is not only saying yes. It is also creating a temporary refusal system.

Write a one-idea focus contract for the next 30 days:

Contract field	What to write
Idea	The customer, problem, and first wedge in one sentence.
Why this idea now	The evidence that makes it worth focused attention.
What we will test	The riskiest assumption and the test that will change our mind.
What we will not do	Features, segments, channels, partnerships, and side ideas we will ignore for now.
Time allocation	How many hours or days each founder will spend on calls, selling, building, and analysis.
Proof target	The specific behavior that would justify continuing.
Stop or change criteria	What evidence would make us narrow, pivot, pause, or kill the idea.
Review date	The date when the decision will be revisited.

A good contract is boring and operational. It prevents the team from pretending to focus while secretly exploring five other ideas.

Refusal List

Create a refusal list beside the contract:

Customer segments we are not serving this month.
Features we are not building.
Partnerships we are not chasing.
Investor conversations we are not using as validation.
Branding decisions we are not overthinking.
Technology choices we are not debating until customer proof demands them.
Metrics we are not using because they only measure curiosity.

This is not rigidity. It is a way to give the current idea a fair test. Most founders do not fail because they lack ideas. They fail because each new idea steals attention before the previous one has received a real test.

Regret-Minimizing Choice Review

When two ideas both look promising, ask which decision will create less regret six months from now.

Do not use regret as romance. Use it as evidence discipline:

Question	What it reveals
If this idea fails, what will we have learned that still helps us?	Whether the work builds customer insight, distribution, or domain advantage.
If we ignore this idea, what evidence might we be walking away from?	Whether the opportunity has real pull or only personal excitement.
Which idea gives us more customer truth per week?	Learning speed.
Which idea gives us more credible founder advantage?	Why this team can win.
Which idea has a clearer first buyer?	Commercial path.
Which idea has a smaller honest first product?	Ability to test without overbuilding.
Which idea would we still respect after 50 rejections?	Founder stamina.

Then write one sentence:

We are choosing this idea because it gives us the best combination of customer truth, founder advantage, commercial path, and learning speed.

If you cannot write that sentence without sounding vague, you may not be ready to choose. Do one more week of focused evidence collection instead of making a dramatic strategy decision.

Post-Choice Drift Control

After choosing an idea, the founder’s biggest enemy is not lack of imagination. It is drift. Drift begins quietly: one customer request, one investor comment, one competitor launch, one new AI demo, one co-founder tangent.

Use a drift control table for the first 30-60 days after choosing.

Drift signal	What it may mean	Response
ICP changes every week	The original segment was too vague or founder is avoiding rejection.	Freeze one segment for a dated sprint unless evidence clearly invalidates it.
Roadmap grows faster than evidence	Product work is replacing customer truth.	Add features only when tied to a named assumption or committed customer outcome.
Investor comments change strategy	Fundraising feedback is being treated as customer evidence.	Separate investor narrative feedback from buyer behavior.
One large prospect pulls scope sideways	Cash or logo anxiety is distorting the wedge.	Decide whether this is reusable learning or custom services.
New ideas keep entering active work	The team lacks a refusal system.	Put new ideas into backlog unless they sharpen the current wedge.
Founder avoids the chosen customer	The idea may lack founder-market fit or conversations are uncomfortable.	Diagnose stamina, access, respect, and sales willingness.

Weekly drift question:

Are we learning more deeply about the chosen customer and problem, or are we making the idea broader to avoid a hard truth?

Good exploration sharpens. Bad exploration expands. A founder should feel the idea becoming smaller, clearer, and more testable before it becomes bigger.

Reader Action

List your top three ideas. For each, write the first wedge and the weakest assumption. Choose the idea where you can test the weakest assumption with the least time, money, and ego. Then run that test before you rename the company, buy the domain, or build the product.

The right idea is not the one that sounds best in your head. It is the one that survives contact with the right customers.