For Product Teams
You don’t find out you built the wrong thing until it’s already shipped. By then it’s not a research problem, it’s a budget problem.
Roadmaps built on the loudest stakeholder’s assumption are expensive. I make sure the customer voice is in the room before the direction locks.
The problem
Most product teams don’t lack opinions. They lack evidence.
Roadmaps get built on the loudest stakeholder’s assumption, a competitor’s feature list, or last quarter’s guess that never got tested. By the time the data comes in, it’s usually a launch postmortem instead of a heads-up.
How I work
Fractional Research Lead. I plug in, run the work, and hand you something you can act on.
01
Understand the decision
Get clear on what your team is actually trying to decide and what evidence would change it. That shapes the entire research approach.
02
Design the research
I select methods and recruit participants that will get you the most useful answers, not the most comfortable ones.
03
Deliver findings that move
Key insights, archetypes, and prioritized recommendations tied directly to the decisions your team needs to make. Written to be acted on, not filed away.
Proof
Research that changed the direction before it was too late.
National Automotive Parts Supplier
Mapped motorists, repair shops, and parts stores into one shared customer view before a multi-year transformation plan locked in.
Read the case study →Small Business Marketing Platform
Found the real blocker in a confusing signup flow wasn’t technical, it was confidence. The fix changed before engineers touched a line of code.
Read the case study →Gaming Accessory Brand
Exposed the gap between what customers said and what they actually bought, before a new product category launch committed the budget.
Read the case study →Let’s talk
Got a roadmap decision you’re not fully sure about?
Most engagements start with a short conversation about what your team is trying to decide. From there I scope something that fits.
Atlanta-based, other places as needed