Momentum Before Mastery: How Imperfect Action Built My First App
- 7 days ago
- 3 min read
By Courtney Johnston
I spent months perfecting the concept for Listless in my head. The idea was solid, the science was there, the positioning felt right. But the app remained theoretical — a beautiful idea that lived in a few rough sketches and Google Docs.
Then I did something terrifying: I started telling people about it.
The Power of External Accountability
My first real momentum didn't come from having the perfect product. It came from opening my mouth. When I told friends and family I was building a wellness app that helps overwhelmed people overcome decision paralysis about how to use their time, something shifted.
Suddenly, this wasn't just my private project—it was a commitment I'd made publicly. That external accountability transformed my relationship with the work.
But the real catalyst came when I stopped talking to people who already loved me and started seeking out strangers who might actually use it. I posted in Reddit communities and Facebook groups, nervously sharing early concepts with people experiencing the exact problem I was trying to solve.
Their responses weren't always what I expected, and that was exactly what I needed. While each story was unique, the underlying need for an app like Listless to support people experiencing burnout, overwhelm, decision paralysis, ADHD and executive dysfunction was clear. Each conversation validated that I wasn’t alone in the problem I was trying to solve. That I was onto something.
Launching Before "Ready"
The hardest decision was hitting publish on the App Store when I knew the product wasn't perfect. There were features I wanted to add, designs I wanted to refine, edge cases I hadn't fully tested. But I launched anyway.
That imperfect action opened the floodgates. Real users started completing real sessions, and their behavior told me things no amount of internal testing ever could. I learned which features resonated, what confused people, and which capabilities actually mattered versus which were just nice-to-haves in my mind.
It also forced me to check my ego. Some days, user feedback stung. Other days, analytics showed concerning drop-off rates. Running your own business means embracing the ups and downs without attaching your self-worth to every metric. I had to learn the difference between users who genuinely needed what I was offering right now and users who might be a fit later but aren't early adopters.
Learning when to listen to feedback and when to stay focused on my core users only came from putting imperfect work into the world.
What I'd Start Sooner
If I were starting again, I'd talk to customers one-on-one and in-depth about how they’re using the app as soon as possible. I spent too much time building things I thought users wanted, when a few conversations could have validated or redirected that effort. Your early users aren't just customers; they're co-designers if you let them be.
If I could go back, I'd also tell my earlier self to stop sitting in imposter syndrome and accept that I do have the capabilities to be a founder. Not because I knew everything (I didn't), but because the willingness to learn while building is more valuable than waiting for mastery before starting.
The Lesson
My app exists today not because I waited until I felt ready, but because I started before I was. Every imperfect release, every awkward outreach message, every piece of feedback that challenged my assumptions — that's where the real momentum came from.
Mastery is seductive. It promises that if we just wait a little longer, learn a little more, polish a little harder, then we'll be ready. But momentum doesn't come from perfection. It comes from taking the first tiny step and putting something into the world.
Connect With Courtney
Comments