Build What You Miss

Most products start with research. Market analysis. Competitor spreadsheets.

Mine start with being annoyed.

The Note I Never Wrote

A few months ago, I was on a call. Someone said something worth remembering. Not a task. Just a thought. The kind that disappears if you don't write it down immediately.

I opened Apple Notes. Waited for it to load. Created a new note. Picked a folder.

The thought was gone.

Not because I forgot it. Because it took too long. My brain had already moved on.

That night I started building Stik.

Build for Yourself First

I keep seeing the same pattern. In my work and in every product I actually like using.

The best things are not built for "users." They're built because someone got tired of a problem and decided to fix it.

Basecamp exists because 37signals needed a tool for their own client work. Craigslist started as Craig emailing his friends about events. Nobody ran a survey. Nobody did a focus group. They just solved their own problem.

Why It Works

When you use your own product every day, you can't fake it.

You know when something is slow. You know when a feature is useless. You don't need analytics to tell you. You feel it.

You also know the exact moment someone needs your product. Not "throughout the day." The exact second. For Stik, it's that tiny window when a thought hits you. Two seconds. That's all you get.

And you build only what you actually need. No extra features to make the landing page look better. No settings panel with 40 options. Just the thing that solves the problem.

The Trap

The moment your product works for you, you start thinking: "Let me make it work for everyone."

So you add options. Preferences. Customization. You try to cover every possible use case.

And slowly, the thing that was fast becomes slow. The thing that was simple becomes complicated. The thing that was yours becomes nobody's.

Someone suggested adding rich text to Stik. Someone else wanted folder hierarchies. Another person asked for cloud sync with ten different services.

All reasonable ideas. All wrong.

Stik captures thoughts. Fast. That's it. The moment I add a formatting toolbar, I become the thing I was running from.

Is Your Problem Worth Building For?

Not every frustration needs a product. Here's how I filter:

How often does it happen? Every day? Every week? If it's once a month, move on.

How much does it bother you? A small annoyance is not a product. If it makes you want to throw your laptop, that's different.

Does anything else solve it? If nothing out there works, that's a good sign. If something exists but you're too lazy to try it, that's not a good sign.

Can you explain the solution in one sentence? "Capture a thought in under two seconds." If you need a whole paragraph, you're trying to solve too many things.

The Question

Next time you have an idea, don't ask "is there a market for this?"

Ask yourself: "Would I use this tomorrow morning?"

If yes, and you'd be annoyed if it disappeared, you might have something.

Build what you miss. The market will find you.