Building the research function from scratch
I joined a company with no formal UX research and built one the team now reaches for by default.
Context
When I joined Independence Pet Group, there was no formal UX research function. Decisions were made without a shared way to learn before a launch or validate after one.
Where I started
I led with analytics reporting and, more importantly, with people. Before pushing any process, I spent time getting to know teams and earning trust, because a research practice only sticks if the people around it want it there.
What I built
I prioritized the two gaps that were costing the most: teams shipped without learning first, and whatever we did learn vanished after each project. So I onboarded the company's first user-testing tool and introduced a habit that hadn't existed: pre-launch ideation through usability and customer research, so teams could learn before they built rather than after. I created a research intake process that grew into a searchable dashboard where the whole team can track and dig through live and past studies. The experimentation side of the practice grew into a program of its own, covered in its own case below.
Going broad
I ran brand-focused survey and interview research across several of the portfolio's top-performing brands, surfacing dozens of insights that led to multiple successful design changes, including the plan repackaging detailed in the next case.
Impact
By being a reliable partner and always offering a hand, trust and understanding of the research process compounded. I reached a point where people propose tests on their own and come straight to me with the questions they want answered. I present findings regularly to the CMO, CFO, and President, and several have circulated independently among the executive team because of their strategic relevance.
What I learned
Building a research function from the ground up taught me that kindness and always offering a helping hand are fundamental to building a practice that non-researchers are invested in. The methods matter, but the relationships are what make the methods count.