There's a version of the product development story that gets told on podcasts: brilliant idea, scrappy team, rapid prototyping, launch. It's about 20% of the actual experience. The other 80%? That's the middle part — and it's where most products quietly die.
The journey from sketch to screen looks tidy in retrospect. The middle was anything but.
Welcome to the Middle
When we started VOSS, the first few weeks were exciting. Architecture decisions felt consequential, wireframes came together fast, and the initial prototype gave everyone a jolt of momentum. Then came the reality:
Six weeks on one offline sync bug. VOSS needs to work without connectivity — exam rooms, hospital basements, rural clinics. Our sync logic worked in testing. In production, with intermittent connectivity and interrupted writes, it broke in ways we didn't predict.
The App Store rejection. Not a code issue — screenshot dimensions from an outdated template. Fix, resubmit, wait three days. Absurd and completely our fault.
The third redesign. The examination summary view was correct but didn't feel right. Two neurologists said so independently. The final version had subtle spacing changes that took days. But it felt right, and that mattered.
The middle: no screenshots to share, no demos to give. Just silent progress on better foundations.
What Kept Us Going
User conversations. Every neurologist who said "when can I use it?" made the middle bearable. Real demand is the best antidote to doubt.
Small milestones. We stopped measuring progress by features shipped and started celebrating problems eliminated. "We fixed the sync issue" became as meaningful as any launch.
Stubbornness. Sometimes you keep going not because the numbers say to, but because you said you would.
The first message from a neurologist who used VOSS in an actual patient encounter — "this saved me time today" — made the middle worth it.
Advice We'd Give Ourselves
- Budget for the middle. It takes longer and costs more than you think — timeline, money, and emotional reserves.
- Stay close to users. Regular user conversations are not optional when you're deep in edge-case fixes.
- Ship ugly versions early. The sooner it's in hands, the faster you learn what matters.
- Celebrate invisible work. Security, performance, architecture — they deserve recognition even without good tweets.
The middle is where products are actually built. The beginning is just the promise. The end is just the receipt.
Building Something and Stuck in the Middle?
We've been there. Whether you need a technical partner or just want to talk through it.
Let's Talk About It →