An observed friction as the initial hypothesis
Having a problem yourself doesn't automatically make it a market opportunity. What it does give you is a head start: you know the exact moment the frustration shows up, the shortcuts you try and the words people use to explain it.
In this case, an encyclopedia of music theory wasn't needed. What was needed was instant feedback while practicing and a short guide while playing. That difference between "learning about something" and "needing to do something" ended up defining the product.
From individual experience to a testable pattern
Your own experience is the start of the research, not a substitute for it. Then you have to ask who else lives with that friction, when it shows up, what alternative they use and what price they pay for not solving it. That's where an interesting story separates from a problem that deserves a product.
For EscalaImprov, that observation led to separating two moments that seemed the same: Study, to understand scales, chords and intervals; and Jam, to play with a short guide, resting notes and a click. It wasn't an aesthetic decision: they were two different jobs.
Reusable capabilities as a product asset
Building something of your own doesn't just leave a published application behind. It leaves a way of looking at the next problem. In this case, designing a study tool forced me to really understand the circle of fifths, instant feedback and why playing with a mouse is awkward.
The same pattern repeats across very different domains. MiCuota left a foundation for auditable payments; Patio, multi-tenancy decisions; WebSpec AI, a flow for specifying. The most interesting asset isn't always the product: sometimes it's the reusable capability left behind.
Domain engine
- Scales and keys
- Harmony and intervals
Study mode
- Trainer
- Visualization and feedback
Jam mode
- Resting notes
- Guide and BPM click
Interaction
- Web Audio
- SVG and keyboard
A shared scale engine powers two experiences. Study prioritizes understanding and feedback; Jam prioritizes quick decisions, keyboard navigation and rhythmic backing.
Product principle: your own experience doesn't replace validation, but it produces better initial hypotheses and helps separate features from the user's real jobs.