Is my product designed to solve a real problem, or merely to showcase technology?

This is a classic question that almost everyone with a technical background asks themselves in the dead of night when building their own product.

Think of it this way: Do you want to first forge a legendary sword that can cut through anything, and then scour the world for something to cut with it? Or do you first discover a piece of meat in life that's hard to cut, and then go find the right knife for it?

Building "to show off technology" is like the former: you have a "legendary sword" in your hand (e.g., the latest AI model, the coolest architecture), you love it so much that you always want to do something with it. So, the product you build is essentially to find an application scenario for this sword. When introducing it to others, you can't help but start by saying, "My product uses XXX technology, it's incredibly powerful..."

Building "to solve a problem" is like the latter: you first identify a "pain point" (e.g., "It's annoying to stick receipts for every reimbursement," or "Too many dogs in the neighborhood, always afraid of stepping in poop when going out"). This pain point resonates with you, or you observe others suffering because of it. Only then do you start thinking: "What method can I use to solve this problem?" At this point, technology is just one option in your toolbox. Perhaps you need a good knife, perhaps scissors are enough, or you might even find that the best way is to tear it by hand.

Here are a few simple ways to help you determine:

1. How do you introduce your product to others? Do you first talk about the technology it uses, or the problems it solves for users? If your first instinct is to talk about technology, be wary. A good product should make it clear to non-technical people what its "use" is, right away.

2. If you remove the cool technology, does the problem still exist? Suppose you can't use AI, big data, or blockchain. Does the problem you intend to solve still cause users significant pain? Are users willing to solve it with a "dumber" but effective method? If the answer is yes, congratulations, you've found a real problem.

3. Who are your users? Have you talked to them? Find 10 of your potential users; don't rush to pitch your product. First, listen to their complaints, listen to what their biggest frustrations are in work or life. After listening, see if your product happens to solve the things they complained about. If they don't feel any pain from that problem at all, then your product might just be wishful thinking on your part.

Having a passion for technology is a good thing; it's the driving force behind innovation. However, a product that survives and grows big will ultimately be because it genuinely solved a problem for a certain group of people and provided value. Technology is a means to achieve value, not an end in itself.

Often, the most successful companies use the most mature, even "boring" technologies, but they solve a real problem.