Started keeping a list of things that pissed me off about six months ago. Not big stuff. Just the tiny annoyances you forget five minutes later. Airline apps that make you click through four screens to check in. Coffee shops with no visible line system. Calendar apps that can't figure out time zones.
Went back through it last week. About 40% of the entries? Someone built a company solving that exact problem. The other 60%? Still waiting.
Your brain already does market research all day. Every time you mutter "this is stupid" under your breath, you're identifying a gap between how things work and how they should. Most people just let those moments evaporate. Some people write them down.
The ones who write them down have an unfair advantage.
Why frustration works better than brainstorming
When you sit down to "come up with startup ideas," your brain does this weird thing. It reaches for what sounds like a startup idea. You end up with "Uber for X" or "AI-powered Y." Derivative stuff that smells like a pitch deck.
Frustration doesn't have that problem. You're not performing creativity. You're just documenting reality. The thing that annoyed you is real. The gap you noticed exists whether or not you turn it into a business.
I've watched this pattern across probably 15 companies now. The founders who started with "I kept running into this problem" ship faster than the ones who started with "I noticed a market opportunity." Different energy. One group is scratching their own itch. The other is building something they think other people want.
The itch-scratchers have this advantage: they know when the product actually works. They can feel it. The market-opportunity people? They're guessing until they get users.
The bug list mechanics
Here's what I tell people to track:
When you notice friction. Not big, obvious problems. The small stuff. Waiting for a receipt email. Explaining the same thing for the third time. Looking for a file you saved yesterday. These moments add up to thousands of hours across millions of people.
When you build a workaround. Any time you create a spreadsheet, write a script, or develop a manual process to get around how something officially works, write it down. Your workaround is a feature request in disguise.
When you pay for something that feels broken. You're already spending money on tools that don't work right. That's a qualified lead telling you exactly what they'd pay to fix.
One founder I know kept a running list in Apple Notes for two years. Just added one line every time something annoyed him. Never looked at it. When he decided to quit his job and build something, he had 200 entries. Three of them turned into prototypes. One became his company.
He didn't need to brainstorm. He already had the research done.
Why most people don't do this
There's something that feels small about documenting annoyances. Serious founders are supposed to identify massive market opportunities, not complain about their password manager.
But the biggest products often start with tiny irritations. Stripe started because online payments were a nightmare to implement. Slack started because internal team communication was a mess. Dropbox started because sending files between computers was harder than it should be.
None of these sound earth-shattering when you describe them. They're just... annoying. The annoying thing was happening to millions of people, though. And most people were just living with it.
The pattern: small frustration, repeated at scale, becomes a billion-dollar opportunity.
Most founders skip the documentation step because they don't think the small stuff matters. They're waiting for the big insight. Meanwhile, they're walking past dozens of real problems every day.
The test
Pull out your bug list (or start one right now). Look at the last five things you added. For each one, ask:
Am I still annoyed by this? If yes, other people probably are too.
Did I build a workaround? If yes, that's a feature.
Would I pay to make this go away? If yes, there's a price point.
You're not evaluating startup ideas. You're just being honest about what wastes your time. The startup part comes later, if at all. First, you're just collecting data on friction.
The companies that move fast don't start with perfect ideas. They start with real problems they've already felt. Then they build the simplest thing that fixes it. Then they watch if other people care.
Your frustration list is the first step in that sequence. Everything else follows from what you noticed when you weren't trying to be clever.