I need to be aware of the difference between solving a small problem and a big problem. Small and rare problems rarely work out, even if the product is beautiful.

The usual reaction to a small problem is to consider ad revenue, but ads won't work if the problem is rare and users aren't engaged enough.

If a product solves a rare problem, it may not have enough demand to sustain itself. Frequent problems, like workplace communication, are where real engagement happens.

It's important to avoid creating a product that requires excessive consulting time from the founder, as this indicates the product isn't truly scalable. If you're solving a small, rare problem, even a billion people in the addressable market may not be inclined to pay real money for it.

You can adjust the price point or even choose a different problem to address, as different groups have varying needs that your software might fulfill.

A good problem to solve is one that is acute and significant enough that people care about it, like the need for corporate credit cards for startups, which was previously unmet.

Some people reach for global problems they don't encounter in their daily lives, making it hard to measure their impact or improvement.

It's crucial to solve a real problem; you should talk to potential users early to ensure that the problem you're addressing is significant for them as well.

If you know a problem exists but haven't found a solution, it may not be clear that design can solve it. Sometimes, the issue could be a business or technology problem rather than a design problem.