The approach
Early design testing, before a line of code.
I tested initial designs with target users before the MVP was built. This let us validate core features, identify points of confusion, and surface unmet needs while changes were still inexpensive. The findings directly shaped design refinements ahead of development.
Post-launch interviews on the live MVP.
Once the MVP launched, I conducted interviews with users working in the real product. This showed where early assumptions held up under actual use, where they didn’t, and what mattered most once compensation cycles were underway rather than hypothetical.
Ongoing testing of new features.
As the product team prioritized new capabilities, I tested those designs with users before they moved forward. Research became a standing input to the roadmap instead of a one-time checkpoint.
The impact
Research informed every stage of the product’s evolution, from initial design through launch and into feature expansion. Early testing reduced the risk of building the wrong thing; post-launch interviews grounded the team in real-world use; and ongoing feature testing kept new work aligned with actual user priorities rather than internal guesses.