Most people answer this question in one of two ways, and both are wrong. The first is conviction: the idea feels great, you can't stop thinking about it, so it must be worth doing. The second is the opposite, a thick business plan with five-year projections that make the whole thing look certain. One ignores the things that could kill the idea. The other pretends to a confidence nobody actually has this early. Neither tells you whether to pursue it.
The more useful way to look at it is this. An idea is worth pursuing not when you're sure it will work, but when you can figure out cheaply whether it will. The job at the start isn't to prove the idea. It's to find the fastest, cheapest way to be wrong about it, and to see whether it survives that.
Treat the idea as a hypothesis, not a plan
The most useful shift is to stop thinking of a new idea as a plan to execute and start thinking of it as a hypothesis to test. A plan is a set of instructions you carry out. A hypothesis is a set of explicit choices and assumptions that might be true, and that you can actually check.
Written as a hypothesis, your idea stops being "a great new product" and becomes something more honest: we believe a specific customer has a specific problem, that our solution addresses it, that we can build and deliver it, and that the economics work. Each of those is a claim, and some of them are probably far shakier than others. The value of writing it this way is that it surfaces the assumptions you were unconsciously treating as facts. This is the same concept behind strategy modeling: make the idea's logic explicit enough to test, rather than impressive enough to approve.
Look at it through three lenses
Once the idea is a hypothesis, evaluate it across three dimensions that have to hold together. We call them desirability, feasibility, and viability, and they sit at the heart of BRI's strategy framework.
Desirability is about the customer and their alternatives: is there a real problem or unmet need here, and does your solution actually address it, for someone specific? Not "would people like this," but "whose problem is this, and how badly do they want it solved." Are the alternatives already available to them meeting their needs adequately, or are there gaps and openings to add real value? Feasibility is about you: can your organization actually build, deliver, and support this, given the resources, skills, and relationships you have or can get? A good idea you can't execute isn't, in practice, a good idea. Viability is about the economics: does the money work, is the opportunity big enough to be worth it, and does it fit where you're trying to go.
The reason to look at all three is that ideas usually fail on the one the founder or venture lead finds least interesting. Technical venture leaders fall in love with feasibility and skip desirability. Market-driven venture leaders assume desirability and never pressure-test viability. An idea is a candidate worth pursuing only when it's at least plausible on all three at once, and the fastest way to kill a bad idea early is to find the lens it can't survive.
Match the evidence to how early you are
Here's the part that trips people up: "worth pursuing" does not mean "proven." Demanding proof at the idea stage is how good ideas die of overcaution and how bad ones die of expensive over-investigation. What you need early is thin, cheap, order-of-magnitude evidence on the assumptions that matter most, not a rigorous study of all of them.
Early on, a few customer conversations, a rough market estimate, and an honest look at your own capabilities are enough to tell you whether the idea deserves the next small step. The bar rises as you go: the more you're about to commit, the stronger the evidence should be before you commit it. Judging a two-week-old idea by the standard you'd apply before a major launch guarantees you'll pursue nothing. The evidence should fit the stage, and it should be driven by what you've learned, not by a calendar.
The honest test
So here is the practical answer to "is it worth pursuing?" It's worth pursuing if you can do two things: name the assumptions that would kill the idea if they turned out to be false, and design a cheap, fast test for the most dangerous one. If the riskiest assumption survives a real test, you've earned the right to take the next step and test the next one. If it fails, you've saved yourself the far larger cost of finding out later.
And if you can't even name what would kill it, that's not a green light, it's your first task. An idea you can't imagine being wrong about is an idea you haven't examined yet.
Pursuing an idea well is a sequence, not a single decision. This piece is about the first question, whether it's worth starting at all. The next two are how much to invest as you go, which we take up in a companion piece right after this one, and when to stop if the evidence turns against you. Turning that sequence into a repeatable discipline, rather than a series of gut calls, is what our consulting work and Growth Forge® Software are built to support.
BRI Associates helps companies grow by drawing on decades of practitioner experience in corporate innovation and new business development — practitioners, not pundits or academics — through direct consulting, training workshops, and Growth Forge® Software, built for the unique requirements of corporate innovation and growth organizations.
Curious where your organization's innovation capability actually stands? Take BRI's free Innovation Capability Assessment — a short diagnostic that names your capability gaps and where to focus."

