Too Many Ideas: Pick One and Start

The Scene

You have a great session with someone. They come back and say it was so good, and now they have so many ideas and so many things they could do. They don't know where to start. The problem isn't a lack of ideas. It's too many.

The Trap

Treating the idea phase as progress. For some people, generating ideas is fun and builds real energy, because they put effort into it. But having the idea can trick your mind into thinking it has already been done, so you move on to the next idea instead of implementing the one you have.

A thought exercise, even a thorough one, is not the same as doing the work of starting. Only one of them produces information.

The Reframe

Don't let perfect be the enemy of good. Don't wait for your idea to be good enough, or for it to be the perfect idea. Pick one and start. Then iterate on that one idea until it stops: until it stops working, or stops teaching you anything. Then choose the next one with real information instead of guesses.

For some people that's all it takes: a kick in the pants. For others, a way to choose helps.

Ways to Choose

Which one works depends on the person and the session. Think of it as a menu, and often it's a combination.

1. Just pick one. No scoring. Any idea you start beats the perfect idea you're still sorting. The iteration does the sorting for you.

2. Feasibility vs. impact. Score each idea on two questions:

  • Feasibility: in the here and now, how feasible is it to implement or test this?
  • Impact: if it works, what's the gain? It might be financial or something else, but use one common metric across all ideas so they're comparable.

"Great" can mean many different things. A common metric lets you sort quickly.

3. Fewest assumptions and dependencies. Count what has to be true, or what has to be in place, before each idea can work. Pick the one with the least. It's the easiest to start, and it fails cleanly if it's wrong, so you learn fast. An idea resting on five assumptions can't tell you much until all five hold.

4. Notice the energy. When someone lists their ideas, you can usually tell which ones they care about and which they're naming for the sake of naming it. The plain "well, I could just do X" often isn't the one they're passionate about. Two ways to bring it out:

  • Reflect it back as an observation, not a judgment: "I noticed you got a lot more animated about this one."
  • Ask: "If all of these took the same effort, which would you do?"

Passion isn't validation. Passion tells you what they'll keep doing. It doesn't tell you whether it's worth doing. Help them see that just because they're passionate about something doesn't make it the right choice. Use the energy check alongside the others, as a gut check on the shortlist.

The Two-Session Arc

Session one. They list the ideas. You help them see where the energy is. The homework is to score or rank the ideas using whichever method fits them, which also quietly forces a choice before the next session.

Session two. They come back with a pick, and you work on how to validate it. In the early phase this is looser than a formal hypothesis test. It's less "design an experiment" and more "how do we get this in front of reality quickly and start working on it."

Why It Works

It swaps a question with no stopping point ("which idea is best?") for one you can answer ("which one can I start now, and would I keep going?"). It also moves people out of thinking and into doing, which is where the real information comes from.

How to Use This With Someone

Name the trap out loud, gently: coming up with ideas is not equivalent to starting on one. Then let them choose the method, or pick it together based on how they behave. Never hand them the ranking. The homework is theirs.

Coming Next

Quick validation for early-stage ideas: the light, do-it-in-front-of-real-people version, as a companion to this entry.

Back to all frameworks