Building
You are not the user, even when you are the user. A quality product is built iteratively, and the only reliable source of truth is the person who buys it.
Everything great that has ever been built needed the user's input. That single sentence contains most of what I know about making products, and almost nobody wants to hear it, because it means the thing in your head is not yet the thing the world needs.
Here is the uncomfortable version. The user's input is not in your mind, and their mind is mostly not in yours, even when you happen to be one of your own users. Those other people can be different from you, and being different, you have to get to know them, to understand them. So the moment you decide you have an idea and you want to launch it, a timer starts at zero. How long that timer runs depends entirely on how quickly you accept that you do not yet know what the market thinks, and that the fastest way to find out is to put something rough in front of it.
A quality product is built iteratively. Iteration means progress based on a feedback loop, a continuous cycle that delivers you information at an aggressive pace, information that leads to conclusions that produce the result you want. And the result you want early on is not a finished product. It is a prototype you can test. Something small, something cheap, something you built with the tools that already exist so you did not spend a fortune to learn one thing. You take that prototype into the market, you ask for feedback, and it moves forward. The prototype becomes a minimum viable product. The MVP becomes a first real product. The first product becomes something you can scale. Every one of these is a checkpoint, and the speed between them is what separates you from everyone else.
People resist this because building in their head feels safe, and shipping feels exposed. In your mind, the idea is already implemented and already successful. You think, I have an idea, I want to build a pet store, I know it will work, I can see the whole thing clearly, I need people X, Y, and Z. And then reality arrives. Both the idea and the people who could bring it to life are hard to find, and the plan almost never matches what you had in your head, because the situation is far more dynamic than you believed. That gap between the clean version in your mind and the messy version in the world is not a sign you failed. It is the entire reason feedback exists.
There is a deeper reason the head-version and the world-version never match, and it is worth understanding. An idea is a form of energy, and matter is a much denser form of energy. To turn an idea into something real, you have to move an enormous amount of energy from one state to the other, and that transformation is where all the friction lives, all the details you did not foresee, all the ways the world refuses to cooperate with the clean picture. The clean picture in your head cost almost no energy, which is exactly why it was clean. The real thing costs a great deal, and the cost shows up as the mess. So the mess is not evidence you got the idea wrong. It is the price of turning an idea into matter, and everyone pays it.
The trap I see most often is over-investing before you have listened. People believe that if they pour more money into a business, they will make more money out of it. Most of the time that is false. What you need is to understand what you are trying to build and whether the world actually wants it, because if the world does not want it, the amount you spent is irrelevant. So at the start, get a source of stable-enough income to give yourself comfort, then spend as little as possible to get the feedback you need to understand whether this thing can be scaled at all. And in this era there are countless tools that can give you that ability nearly for free.
Money spent before feedback is money spent buying certainty about the wrong things. You can build the most beautiful version of a product nobody wants, and all the beauty does is make the failure more expensive. The founder who spends a little to learn whether the world wants the thing, and only then spends more to make it excellent, is playing a completely different game from the founder who spends everything up front to make it excellent and then goes looking for someone who wants it. The first is buying information. The second is buying reassurance, and reassurance is the most expensive thing you can purchase in a startup.
Once you understand the shape of iteration, the question becomes what to do when something starts working. When you have a bit of success, not huge, but real customers, real sales, your job is to figure out how to scale. And that is a moment to slow down, look, contemplate, even meditate on it, and understand what comes next. Do I expand with more partners or more products? Or do I go find more customers for the same product? Very often the situation simply calls for finding more customers for the same product, because if you lack resources, expanding into more products is harder. It depends on your strategy. We chose to expand with more products and more campaigns, because we had built a tool that let us iterate campaigns quickly, so our aim was to create value in as many places and niches as possible, and grow each one, hoping one would explode without enormous effort on our part. That is one strategy. If building a single product is a long process for you, the better move is to find as many customers as possible for that one product.
But whatever the path, when you see something work, you have to understand what is working and why, and then press the accelerator exactly there. The tendency we have as founders is to look in twenty directions, in a hundred directions, and believe we can do them all. We cannot. The amount of energy required to turn a thought, which is a form of energy, into matter, which is a denser form of energy, is enormous. You will not have the time, through yourself or through others, especially at the start without the financial resources. So you focus, ruthlessly, on the thing the feedback told you was real.
The most important habit underneath all of this is talking to your customers directly. Not through intermediaries, not through surveys, not through statistics you pulled off some site. You, personally, talking to the people who buy your product, understanding their nature, their state, their needs. That is what lets you make good decisions about whether a product is genuinely useful, whether it should change, whether it should be improved, or whether you should build something else entirely. There is a technique in the copywriting world, getting into bed with the customer, sleeping a night in their shoes. I think it goes further than that. It is the ability to become the customer, to be their mind rather than merely peek into it. And you build that ability by reading what customers actually write, not what is written about them, and reading between the lines.
Surveys and statistics feel rigorous, which is exactly what makes them dangerous. They give you the shape of an answer with all the texture removed, and the texture is where the real information lives. A number tells you that thirty percent of people did something. A conversation tells you why, and the why is the thing you can actually act on. When you talk to the person directly, you hear the hesitation, the offhand complaint, the thing they mention as an aside that turns out to be the whole story. None of that survives being turned into a percentage on a dashboard, and the founders who only ever look at the dashboard are making decisions on the least useful version of the truth.
And when you scale, scale the thing the feedback actually validated, not the thing you wish had worked. Founders often get real signal on one part of the product and then pour their scaling energy into a different part, the one they are personally proud of, and wonder why the growth does not come. The feedback is not a suggestion to weigh against your preferences. It is the market telling you where it is pulling, and your job is to pour energy exactly there, even when there is not the part you find most interesting. The discipline of listening does not end at the prototype. It governs what you choose to scale, which is the most expensive decision you make.
There is also a moment when a product's life cycle ends, and your customers will usually tell you, if you are listening. Ideally you can even predict it, sense where the market is heading, and instead of clinging to the old thing, build alongside it, a new product, another product, or a new version that leads to a different experience. Maybe you will need to solve a different problem, or maybe you already solved this one and it is no longer needed. That happens too. But you will only know if you stay informed and stay close to the people who buy from you.
The hardest part of this is emotional, not technical. Showing someone a rough, unfinished version of your idea feels like showing them a photograph of yourself at your worst, and every instinct says wait until it is polished. But polish before feedback is the exact mistake, because you spend all your effort perfecting details the market may not even care about, and you deprive yourself of the information that would have told you which details mattered. The rough version is not embarrassing, it is efficient. It asks the only question that counts, do you want this at all, before you have spent a fortune making it beautiful.
And you have to listen in a particular way, because people are polite. When you ask most people what they think, they will soften their answer to spare your feelings, which gives you flattering noise instead of useful signal. The truest feedback is not what they say, it is what they do, whether they actually buy, whether they come back, whether they tell someone else. So weight actions over words, and when you do talk to them, read between the lines, notice the hesitation, the thing they mention and then wave away, because that offhand remark is often the real verdict hiding under the polite one.
So the whole discipline reduces to a rhythm. Build something small and cheap. Put it in front of real people fast. Listen, especially to the ones who pay. Understand what worked and why. Press the accelerator on exactly that, and let go of everything else. Then repeat. Give yourself the conditions to do this without panic, because panic ruins the listening. Get a stable-enough source of income so that your survival does not depend on the first version working, and then spend as little as possible to learn whether the thing can be scaled at all. A founder who needs the prototype to succeed cannot hear what the prototype is telling them, because their fear overrides the feedback. A founder who has a floor under them can look at a disappointing result clearly, take the lesson, and iterate, instead of arguing with reality to protect a bet they could not afford to lose. Cheap experiments and a stable floor are not signs of small ambition. They are what make honest listening possible.
You are not the user, even when you are the user, and the sooner you accept that the person on the other side of the transaction knows something you do not, the sooner you stop polishing a beautiful guess and start building the thing the world was actually asking for.