Stop Asking If The Idea Is Good. Ask What It Is For

“Is this a good idea?” is a weak first question.

It sounds useful because it feels like the adult thing to ask. You have a thought in your head. It has some charge. You can see a version of it working. So you bring it to someone and ask for a verdict. Is this good? Should I do it? Am I crazy for thinking about this? But the question puts too much weight on one word. Good can mean beautiful, profitable, useful, original, timely, easy, exciting, defensible, or important. Those are not the same judgment.

A better first question is simpler. What is this idea for?

That question changes the conversation immediately. A podcast can be a bad way to generate leads in the next ninety days and still be a strong trust asset for people who already know you. A software tool can be a weak standalone product and still be exactly the internal system your business needs. A workshop can be hard to scale and still teach you more about buyers in two hours than a month of private planning. The idea is not good or bad by itself. It is good or bad against the job you are asking it to do.

A lot of people lose months here. They judge every idea as if it has to become the whole business. Then a small useful experiment becomes a brand, a launch plan, a full website, a content machine, and a private identity crisis before anyone has reacted to it. The idea did not ask for all that. It may have only needed to get ten replies, explain an offer more clearly, reduce one delivery mistake, or make your thinking visible to the right person.

Before you judge the idea, finish the sentence: this idea is supposed to. Not in a vague way. Not “create value” or “help people” or “build my brand.” Those phrases are soft enough to hide inside. Try something sharper. This idea is supposed to get ten replies from buyers. This idea is supposed to help me explain the offer in one page. This idea is supposed to reduce the same handoff mistake we keep making. This idea is supposed to show clients how I think before they book a call.

Once the job is named, the test becomes more honest. If the job is demand, you do not need to build the full product first. You need to put the offer in front of real buyers and see whether behavior follows. If the job is clarity, you do not need a perfect brand system. You need to explain the idea plainly and notice where people get confused. If the job is operations, you do not need to buy a platform on day one. You can run the process manually for a week and see where it breaks. If the job is trust, you do not need to start a content machine. You can make one useful piece and send it to five people whose judgment matters.

Energy matters in all of this. I do not like the version of business advice that treats excitement as a liability. Excitement gets you moving. It gives you enough charge to write the first message, sketch the first page, make the call, record the thought, or build the rough version. That is useful. The problem starts when you ask excitement to do the job of evidence.

Evidence comes from behavior. Someone pays. Someone replies with a real question. Someone uses it without being pushed. A process gets faster. A mistake rate drops. The same objection shows up three times. A person you respect says, “I need this,” and then acts like they mean it. That kind of signal is different from feeling alive when you talk about the idea in your own head.

The move is not to kill energy. The move is to spend it well. Let the excitement pay for a small honest test before it becomes a giant private commitment. If the idea is for learning, make the smallest version that can teach you something real. If the idea is for revenue, find the person who has the problem and ask what would make them pay attention now. If the idea is for reputation, make the judgment visible. If the idea is for freedom, judge it against the time, margin, energy, and obligations it will create if it works.

Different jobs require different standards. This is why outside feedback can feel confusing. Someone might like the creativity of an idea and still have no idea whether anyone will buy it. Someone might see the commercial angle and miss that it would pull you into work you do not want to keep doing. Someone might tell you it is too small when small is exactly the point, because the job was to learn quickly without trapping yourself.

So the useful conversation is not “Do you like it?” It is “Does this do the job?” If the job is to test demand, did it create signal from buyers? If the job is to clarify the offer, did the explanation get easier? If the job is to build trust, did it make your taste, thinking, or capability easier to see? If the job is to create a strategic option, did it open a door without taking over the whole room?

You can still decide not to do it. Naming the job does not force the answer. It gives you cleaner reasons. Keep it because the test showed signal. Change it because the problem is real but the format is wrong. Pause it because the timing or cost is wrong. Kill it because it does not do what you needed it to do. That is a much better place to make the decision from.

Ideas are not good in a vacuum. They are good in relation to a person, a market, a moment, a constraint, and a desired outcome. Before asking if the idea is good, ask what it is for. The better question usually gives you the better next move.