Screen 1.4: Voice Check

Prototype

The critical "does this sound like me?" moment

A/B Testing: Voice Check Flow

This is THE make-or-break screen. Aaron evaluates if captured content sounds authentic. Success signal: "Huh. That actually sounds like something I'd say."

A: Full card (3 options)B: Binary (Yep/Nope)C: Audio compare
Journey Phase: Skeptical Testing (Phase 1) • Aaron's State: Critical evaluation • Exit Risk: If output sounds generic/corporate

Voice Check

Here's what I captured from our conversation.

The only question that matters:

Does this sound like you?

Reviewing 1 of 2

Captured: The Turquoise

Your call
“The turquoise is from a family trip to Arizona when I was 12. My old man pulled over at this roadside stand — you know, one of those places with all the silver jewelry and pottery. Didn't buy anything for himself. Just handed me a chunk and said "put that somewhere you'll see it every day." Been on my desk ever since. Probably 30 years now. I don't even think about it most days. But yeah, I guess I touch it when I'm stuck on something.”

💡 What happens next

  • •"That's me" → Saved to your knowledge library
  • •"Close, but..." → Edit it until it's right
  • •"Not me" → Deleted. No trace. Gone.

Version A Design Notes:

  • Full capture card with three clear options
  • Progress indicator shows review status
  • Inline editing when "Close, but..." selected
  • Delete confirmation prevents accidental loss
  • Pros: Explicit control, clear progress
  • Cons: More clicks, might feel formal

Version A

Three clear options: approve, edit, reject. Progress tracking.

Risk: More clicks

Version B

Simple binary: Yep or Nope. Edit tucked away.

Risk: Edit feels hidden

Version C

Audio playback alongside text. Hear vs. read comparison.

Risk: Tech complexity