← Build log

The Product Insight That Changed Everything: Dogfooding, AI, and the Discovery of Flow State

May 31, 2025

Published: May 31, 2025
Read Time: 10 minutes


There’s a moment in every product journey when you stop building what you think users want and start building what you actually need. For VoiceCatcher, that moment came not from user interviews, market research, or competitive analysis—it came from me using AirPods to dictate a message and having them cut me off mid-thought after 30 seconds.

That interruption made me lose my train of thought entirely. And in that moment of frustration, I discovered the most important insight about our product: the real job-to-be-done isn’t transcription accuracy—it’s protecting flow state.

This is the story of how daily dogfooding, combined with AI as a thinking partner, led to a strategic decision that completely changed our product direction.

The Frustration That Started Everything

I’ve been using voice-to-text tools for years. Google Docs transcription, Otter.ai, built-in iOS dictation, you name it. But there was always something that bugged me about them—they felt… interruptive.

The breaking point came during a particularly intense brainstorming session. I was using my AirPods to dictate some ideas while walking, and just as I was getting into a really good flow of thinking, the system cut me off. Thirty seconds. That’s all I got before it decided I was done talking.

I lost that thought completely. Not just the words—the entire thread of reasoning that had been building. Anyone who’s done creative work knows that feeling. You’re in the zone, ideas are connecting, and then… nothing. Back to square one.

That’s when it hit me: interruption is the enemy of voice productivity tools.

The Daily Discovery Process

Here’s the thing about building products—you can interview users all day long, but nothing beats actually living with your own creation. I use VoiceCatcher every single day. For blog posts, for thinking through product decisions, for capturing random thoughts while cooking dinner.

And after weeks of daily use, I started noticing something profound:

VoiceCatcher never interrupted me.

It just… listened. For as long as I needed to talk. No arbitrary timeouts, no “are you still there?” prompts, no cutting off mid-sentence. I could start a thought, pause to think for 30 seconds, continue talking, and it would capture everything seamlessly.

More importantly, when I finished talking, the transcript appeared exactly where I needed it—in my clipboard, ready to paste wherever I was working. No app switching, no copy-paste dance, no friction.

I was experiencing something I’d never felt with other voice tools: true flow state.

The AI Thinking Partner

But here’s where this story gets interesting. Having a breakthrough insight is one thing—understanding its implications and acting on it is another. That’s where AI became an invaluable thinking partner.

I started bouncing ideas off AI about this flow state concept. Not just “what do you think?” but deep, structured exploration:

  • What does this mean for our product strategy?
  • How does this change our competitive positioning?
  • Should we still build real-time transcription if it might break flow state?
  • What frameworks can help us evaluate this insight?

The AI helped me organize my scattered thoughts into coherent frameworks. We ran through SWOT analysis, Jobs-to-be-Done thinking, opportunity cost evaluation. The AI didn’t just validate my insight—it helped me understand why it mattered and what to do about it.

The Strategic Revelation

Through this AI-assisted analysis, we discovered something that completely changed our product direction:

Real-time transcription optimizes for reassurance, not performance.

Think about it. When you see words appearing as you speak (like in Google Docs), it feels reassuring. You know the system is working. But it also creates a cognitive split—part of your brain is watching the text, proofreading, getting distracted by typos or corrections.

You’re not fully present with your thinking anymore. You’re multitasking between idea generation and quality control.

VoiceCatcher’s batch processing approach—record everything, then transcribe—actually enables superior cognitive performance. You stay 100% focused on your thoughts. No visual distractions, no proofreading while thinking, no interruption anxiety.

We discovered we weren’t competing on transcription quality. We were competing on cognitive experience.

The Decision Framework in Action

This insight led to one of the most important strategic decisions in VoiceCatcher’s development. We were considering implementing real-time transcription (like every other voice tool has). It would have taken 6-9 weeks of development time.

Using structured decision frameworks—guided by AI—we evaluated:

Real-time transcription approach:

  • High technical complexity (dual engine architecture)
  • Commodity feature (everyone has it)
  • Cognitive performance cost (breaks flow state)
  • 9 weeks of development time

Enhanced trust-building approach:

  • Medium complexity (confidence indicators, onboarding)
  • Unique positioning (flow state optimization)
  • Superior cognitive performance
  • 4 weeks of development time

The analysis was clear: reject real-time transcription. Double down on flow state.

The Bigger Lesson: Solve Your Own Problems First

This experience taught me something fundamental about product management:

The most effective products solve problems you actually have, not problems you imagine others have.

I wasn’t building VoiceCatcher for some abstract user persona. I was building it for me—someone who gets frustrated when voice tools interrupt my thinking, who needs seamless integration with my workflow, who values cognitive performance over reassuring feedback.

And here’s the beautiful thing: turns out lots of other people have the same problem. They just didn’t know how to articulate it.

The AI Collaboration Effect

What made this breakthrough possible wasn’t just dogfooding—it was having AI as a thinking partner throughout the process.

AI helped me:

  • Organize scattered insights into coherent frameworks
  • Validate hunches with structured analysis
  • Explore implications I might have missed
  • Communicate findings in persuasive, actionable ways

This wasn’t AI replacing human insight. It was AI amplifying human pattern recognition and helping translate intuition into strategy.

Why This Matters for Technical Product Managers

If you’re building user-facing products, especially at startup speed, here are the key takeaways:

1. Dogfood Relentlessly

Use your own product every single day. Not just testing—actually relying on it for real work. Your users’ pain is your competitive advantage waiting to be discovered.

2. Pay Attention to Friction

The things that annoy you daily are probably annoying your users too. But more importantly, the things that don’t annoy you might be your secret sauce.

3. Question the Obvious

Just because every competitor has a feature doesn’t mean you need it. Sometimes the obvious solution optimizes for the wrong thing.

4. Use AI as a Thinking Partner

Don’t just ask AI for answers. Use it to explore ideas, organize thoughts, and validate insights through structured frameworks.

5. Solve Your Own Problems First

Build for yourself, then validate that others have the same problem. It’s much easier than trying to imagine what others need.

The Result: A Competitive Moat

This insight didn’t just change a feature decision—it changed our entire positioning.

We’re no longer “another voice transcription tool.” We’re “the voice productivity tool that protects your flow state.” That’s something competitors can’t easily copy because they’re stuck in the real-time feedback paradigm.

More importantly, our users are discovering something they didn’t know they wanted: the ability to think without interruption.

Looking Forward

This experience reinforced my belief that the best products come from solving real problems you experience daily. But it also showed me the power of AI as a thinking partner in the product development process.

We’re not just building features anymore. We’re building experiences that respect human cognition and optimize for creative flow.

And every day I use VoiceCatcher, I’m reminded that sometimes the best product decisions come not from what users ask for, but from what they actually need—even when they can’t articulate it themselves.


Takeaway: Next time you’re frustrated with a tool you use daily, don’t just grumble and move on. Dig deeper. That frustration might be the key insight that transforms your product.

And when you have that breakthrough moment, don’t keep it in your head. Use AI to help you think it through, organize it, and turn it into action.

Your users—and your business—will thank you.


This blog post was written using VoiceCatcher, naturally. No interruptions, no broken flow state, just pure thought-to-text transformation. The kind of experience every voice tool should provide, but somehow, most don’t.