The Three-Question Test for Whether an Idea Is Really Yours

Every founder eventually has a moment when they cannot quite tell whether the idea they are building is their own idea or somebody else's idea that they have been carrying around long enough that it started to feel like their own. The distinction sounds like a philosophical one, and it is easy to dismiss it as unimportant, but it turns out to matter in a very practical way, because ideas that are truly yours tend to survive the hard months while ideas that you inherited from someone else's excitement tend to collapse the first time the work stops being fun.

Founders who are working on genuinely inherited ideas often do not realise it until they hit a wall that would have been easy to push through if they had chosen the problem for themselves in the first place, and by then they have already spent a year or more on something they should have quietly walked away from at the start.

The test I want to give you is three questions, and if you answer them honestly the answer usually shows up on its own without you having to reason your way to a conclusion.

1. Where did you first hear about this problem

The first question is where you first heard about the problem the idea is meant to solve. If you first heard about it in a conversation you were part of, from someone whose life you understand, and the problem stayed on your mind because you kept noticing it in other people afterwards, the idea is probably yours in the way that matters. If you first heard about it in a podcast, a Twitter thread, a YC essay, or a conversation where you were the passive listener, and the idea entered your mind more or less fully formed rather than growing over time, the idea is probably borrowed, and the fact that you find it interesting does not make it yours.

2. Who would you build this for if there was no money in it

The second question is who you would still want to build this for if you knew for certain that no money would ever come out of it. Founders working on ideas that are truly theirs can usually name a specific person, sometimes a family member, sometimes an old classmate, sometimes themselves at a younger age, and the idea keeps existing in their head because that person keeps existing in their head. Founders working on borrowed ideas struggle with this question, because the person on the other side of the problem is an abstract customer segment rather than a specific human, and if you take the money away there is no one left in the picture worth building for.

3. What would it cost you to walk away today

The third question is what it would actually cost you emotionally, not financially, to walk away from the idea today and pick something else tomorrow. If the answer is that walking away would feel like a relief, or that you would be a bit sad but you know you could pick up another idea within a week, the idea was probably not really yours, and you have been holding on because starting over feels harder than continuing. If the answer is that walking away would feel like abandoning something you have not yet finished saying out loud, the idea is yours, and you should stay with it long enough to finish saying what it is you have been trying to say.

What to do with the answers

If the three answers point at a borrowed idea, that is useful information, and the honest move is to stop pretending you can force yourself into caring and instead start looking for the idea you actually care about, which is usually closer to home than you expect. If the three answers point at your own idea, that is also useful information, since you now know that when the work gets hard you have something real to hold on to, and the reason for continuing is one you can explain to yourself without needing anyone else's validation. Either answer moves you forward, and the founders who ask these questions early tend to spend the next year on the right thing while the founders who never ask them tend to spend the next year on the wrong one.

Why Your Best Ideas Hit on Sunday Night, and How to Keep Them

There is a specific quality to the ideas that arrive on Sunday evenings that founders notice once they have been building for a while. These are usually not the ideas you had while at your desk, and they are usually not the ideas you had while pushing through a long working session, they are the ideas that showed up while you were walking to buy something, sitting in the traffic on your way back from a family visit, or brushing your teeth before bed.

The Sunday evening version of you is often thinking more clearly about the business than the Monday morning version of you ever will, and if you can find a way to preserve what the Sunday version noticed, the rest of the week benefits in ways that are hard to explain until you have tried it.

The reason this happens is not mystical, since Sunday evenings are one of the few times in the founder week when the pressure of the working week has released enough for your mind to run in the background, and the background is where the connections between things you already knew separately actually get made. When your attention is fully occupied with immediate tasks, your mind cannot spare the resources for that kind of loose association, but when the immediate tasks are behind you for a few hours, the mind quietly does the work you had been unable to force it to do during the week.

"...since Sunday evenings are one of the few times in the founder week when the pressure of the working week has released enough for your mind to run in the background, and the background is where the connections between things you already knew separately actually get made."

The problem is that Sunday evening ideas are fragile

The trouble with Sunday evening ideas is that they arrive in a form that is not yet ready to be acted on, and if you do not write them down quickly they usually disappear by Monday morning, replaced by the next urgent thing on your calendar. Founders often blame themselves for forgetting, or assume the idea was not that important, but the reality is that the idea was important and the system for catching it was inadequate, and if you fix the system the ideas start to accumulate into something meaningful over time.

Three habits that catch them

1. The first habit is to keep a single note on your phone that is only for these ideas, and to open it as soon as an idea shows up, even if you can only type two lines before the moment passes. The note does not need to be organised, and the entries do not need to be complete thoughts, since the goal is capture rather than composition, and you can polish anything worth polishing later in the week when you have more attention to spare.

2. The second habit is to schedule a specific block of time on Monday morning, no more than thirty minutes, to review what showed up in the note over the weekend and decide whether any of it is worth acting on this week. Most of what you catch will turn out to be nothing, and that is fine, since the value comes from the few that do turn out to be something, and you cannot know which are which without a review process to sort them.

3. The third habit is to keep a separate document, updated once a month, of the ideas you caught that later turned into something real. This document is not for anyone else to read, and it does not need to be impressive, but the act of maintaining it teaches you which kinds of Sunday evening thoughts turn out to be worth acting on, and after six months of tracking you will notice patterns in your own thinking that you would never have noticed otherwise.

Why this matters beyond ideas

The larger reason to build this habit is that founders who are good at capturing what their unhurried minds notice tend to be more original thinkers over time, since the ideas that make it into the note are usually the ones that are furthest from what everyone else in your industry is thinking about, and originality is one of the few real competitive advantages available to a small company. Founders who lose these ideas by not writing them down tend to arrive at Monday morning with the same conventional priorities everyone else has, and the business ends up looking like every other business in its category, which is a quiet way for a company to fail without ever noticing it was failing.

The Five-Minute Check That Separates Market Ideas from Ego Ideas

Every founder I know has at least one idea in their notes app that they cannot really let go of, and if you press them on why they still believe in it, they will give you an answer that sounds reasonable on the surface but does not quite hold up when you look at it a second time.

The idea might be well built out in their head, they might even have a name for it and a rough sense of what the landing page would say, and yet nothing has moved on it in months. What is often happening in this situation is that the idea is not really an idea about the market, it is an idea about them, and the difference matters because market ideas eventually pay you back for the effort you put in while ego ideas will take everything you have and leave you with an updated version of the same slide deck.

The check I want to give you takes five minutes and only requires you to be honest with yourself for a short while, and it comes down to three questions asked in a specific order, and the reason the order matters is that each one closes off a common way founders trick themselves into thinking they are working on a market problem when they are actually working on a self-portrait.

Question one,

Who told you this was a problem?

The first question is whether you can name the specific person or people who told you this was a problem, and how recently the conversation happened. If the answer is that you noticed the problem yourself and it has been bothering you for a while, that is not a market signal, that is a personal observation, and personal observations sometimes turn into market opportunities but they usually do not without other people confirming them first. If the answer is that a specific person said this to you, or several specific people did, then you have something to work with, and the memory of the conversation is a reasonable place to start. Sit with this question long enough to answer it honestly, because founders often reverse-engineer a convenient origin story where a friend supposedly mentioned it, when what really happened is that they had the idea first and then went hunting for confirmation to attach to it.

Question two,

What part of your explanation are you most attached to?

The second question is about what you find yourself defending most passionately when you describe the idea to someone new. If the part you are most attached to is the technology, the design, the name, the fact that you thought of it, or how novel it is, you are describing an ego idea, and the market does not really care about any of those things. If what you are most attached to is the person on the other side of the problem, the specific inconvenience they experience on a Tuesday afternoon, or the specific amount of money they are losing every week to it, then the market has a chance of caring, because you are now telling the story from the customer's side of the table rather than from your own.

Question three,

Would a competitor make you feel threatened or relieved?

The third question is the sharpest, and it is worth asking yourself out loud so that you cannot pretend you did not hear the answer. If a similar startup launched tomorrow doing the exact same thing but slightly better than you, would you feel relieved or would you feel threatened. A founder solving a market problem will feel relieved when someone else picks up part of the load, because the point was for the problem to go away, and a competent competitor is a form of help even if it is inconvenient. A founder attached to an ego idea will feel threatened, because the point was to be the one who did it, and someone else doing it removes the reason the idea existed for them in the first place.

What to do with the answers

If you can sit through the three questions and answer them honestly, you will usually know within five minutes whether the idea in your notes app is worth the next six months of your life or whether it is a project you have been carrying because it feels like part of who you are. Neither answer is a bad one, since ego ideas can sometimes be turned into market ideas by starting the process over from the customer's side, and market ideas can sometimes be dropped without regret when you realise you were only holding on because someone once told you it was clever. The check just gives you the language to tell which is which, and once you have that language, the rest of the decision becomes much easier to make.

How to Tell a Hard Problem from One Worth Quitting

Every founder eventually reaches a point in their company where the work has become hard in a way that does not feel productive, and the question they are trying to avoid asking themselves is whether the hard part is a signal that they are close to something valuable or a signal that they should stop. The two look similar from the inside, and the popular startup narrative encourages founders to interpret every hard patch as a sign of impending breakthrough, which produces a survivorship bias that hides all the founders who pushed through hard patches that were actually telling them to stop. Learning to tell the difference is one of the more valuable skills a founder can develop, and it is a skill that gets sharper with practice rather than one that arrives by intuition.

The distinction is not about how tired you are or how discouraged you feel, since those states can accompany either kind of hard patch, and using them as your guide will mislead you in both directions. The distinction is about what is actually happening in the underlying work, and there are three specific signals that help clarify which kind of hard patch you are in.

Signal one,

Is the customer moving toward you or away?

The first signal is whether the customer is moving toward you or away from you across the hard patch. If you are struggling with the product but the customer is still asking when the next version is coming, or still using what you have built despite its problems, or still recommending you to their friends, the hard part is a build problem and the customer is telling you the underlying idea is worth completing. If the customer is drifting away, going silent, or churning during the hard patch, no amount of engineering effort on your side will fix the underlying issue, since the customer has already told you that the direction is wrong regardless of how well you execute it.

Signal two,

Are you learning or repeating?

The second signal is whether the hard work is teaching you something new each week or whether you are repeating the same lessons without progress. Founders in a productive hard patch tend to describe each week as slightly clearer than the one before, even if the underlying situation has not improved on paper, since the increased clarity is itself the sign that the work is moving. Founders in an unproductive hard patch tend to describe each week as remarkably similar to the previous one, with the same problems reappearing and the same solutions failing in the same ways, and this repetition is a strong signal that the underlying structure of what you are attempting is not workable in its current form.

Signal three,

Is the effort compounding or decaying?

The third signal is whether the effort you are putting in is compounding into something that will still be there next quarter or decaying as fast as you can produce it. If the customer conversations you had two months ago are still informing your current work, if the code you wrote three months ago is still running the business, and if the relationships you built at the beginning are still generating value, the effort is compounding and the hard patch is worth staying inside. If everything you produce needs to be redone every few weeks, if the customer conversations are quickly outdated, and if the systems you built keep breaking, the effort is decaying and the hard patch is telling you to stop and restructure rather than to keep pushing.

What to do with the reading

If the three signals point in the same direction, the answer is usually clear, and the harder question is whether you are willing to accept it. Founders who are honest about what the signals say tend to make the call earlier and end up in better positions than founders who insist on ignoring the signals until the situation forces the decision on them. If the signals point at quitting, quitting is not a failure, it is a redirection, and the founders who redirect early usually go on to build something better than the founders who spent an extra year forcing a company that had already told them to stop.