My path to UX research wasn’t exactly a straight line.
Long before I became a researcher, I was fascinated by the ways stories and experiences shape how children understand the world.
Some of my earliest influences were The Muppets, Sesame Street, and Mister Rogers’ Neighborhood. As a child, I experienced firsthand how meaningful media created for children could be. These weren’t simply shows to me. They communicated that children mattered—that their questions, feelings, imaginations, and ways of seeing the world were worth taking seriously.
That idea has followed me throughout my career.
Stories, children, and an unexpected path
I started by studying English. I loved writing and literature and imagined that my future might involve writing young adult novels, teaching English, or some combination of the two.
But puppetry kept finding its way into my life.
While I was in college, I spent two summers volunteering in Nicaragua and the Dominican Republic, using puppetry as a way to engage and teach children. What had been a lifelong interest started to look like something I could pursue professionally.
Then I discovered the University of Connecticut’s graduate program in puppetry.
The program accepted only a handful of students each year, and when I had the opportunity to attend, my husband and I packed up our life in California and moved across the country to Connecticut with our one-year-old.
It wasn’t the most conventional career decision.
It turned out to teach me much more than how to make puppets.
Puppetry was my first education in user experience
Building a puppet is a design problem.
You’re designing for the audience—but you’re also designing for the puppeteer who has to operate it.
Something can look wonderful from the audience’s perspective and be exhausting or nearly impossible to perform. A mechanism can create an incredible effect but be too fragile to survive repeated use. Materials affect weight. Weight affects performance. A design choice that solves one problem can create another.
So you build. You test. You perform. You discover what doesn’t work. And you build again.
Puppetry taught me to prototype, iterate, and make trade-offs long before I used those words professionally.
It also taught me to design within real constraints.
Puppetry is physically demanding. Objects need to work reliably in performance, but they also need to be maintainable. If something breaks during a production that has rented a studio for a single day, an elegant design that takes three days to repair isn’t particularly useful.
You learn to ask: Who needs this to work? Under what conditions? What happens when it doesn’t?
And you learn to improvise.
There isn’t a store where you simply buy everything you need to create the thing you’ve imagined. Puppet eyes might begin as ping-pong balls. Plastic spoons become structural components. Foam, fabric, wire, adhesives, hardware, and unexpected objects get combined, tested, discarded, and recombined until something works.
You become comfortable looking at the materials and constraints in front of you and asking:
What can I make possible with what I have?
I didn’t realize it at the time, but that way of thinking would become foundational to how I approach both product development and research.
From creating experiences to understanding them
Puppetry also taught me to pay very close attention to experience.
A puppeteer is constantly thinking about the audience: Where are they looking? What do they understand? What are they expecting to happen? What captures their attention? Where does the illusion break?
And when the audience is made up of children, those questions become even more interesting.
My curiosity gradually expanded from creating experiences for children to understanding how and why those experiences worked.
That journey eventually took me to WGBH, where I interned with children’s media properties including Arthur and Between the Lions, and then deeper into the study of child development, learning, digital media, and human-computer interaction.
Ultimately, I earned an MA in Child Development from Tufts University and a PhD in Media, Technology, and Society from Northwestern University.
Researching children, families, and technology
At Northwestern, I studied the increasingly complicated relationship between children, families, and technology.
My research explored how young children interact with emerging interfaces, how parents and children use media together, how technology fits into family life, and how children’s developmental needs should inform the experiences we create for them.
I conducted qualitative and quantitative studies, contributed to national survey research, published peer-reviewed scholarship, presented at academic conferences, and taught cognitive development.
I loved understanding the why behind human behavior. But I increasingly wanted research to do something else, too.
I wanted it to change what we built.
From understanding experiences to building better ones
That brought me into product development.
At VTech and hand2mind, I worked on educational technology and learning products for children, families, and classrooms. I conducted research with children, parents, and educators and used what we learned to shape products from early concepts through development and launch.
Some of those products went on to become award-winning and commercially successful. More importantly, I learned something that has shaped how I practice research ever since:
Rigorous research matters. But research creates value when people can act on it.
The right evidence has to reach teams at the right moment. Findings have to make sense to people who weren’t part of the study. And researchers need to understand the product, technical, educational, organizational, and business realities surrounding the decisions they’re trying to influence.
Learning to navigate complexity
Consulting expanded that perspective.
At Sylver Consulting, my work took me across healthcare, education, technology, consumer products, and complex organizational systems.
I worked on questions involving human motivation and behavior with Cigna and Self-Determination Theory scholar Richard Ryan. I conducted Jobs-to-be-Done research following Cigna’s acquisition of Express Scripts. I led international research for Mary Kay.
And sometimes research meant sitting in a room with NASA engineers, scientists, and rover drivers helping them think through how humans might collaborate to operate a rover on the Moon.
The subject matter changed dramatically. The underlying research challenge often didn’t:
There was a complicated problem, incomplete information, different perspectives, and an important decision to make.
And frequently there wasn’t an established research playbook for answering it.
That’s where something I learned years earlier in a puppet studio became surprisingly useful.
Look at the problem. Understand the constraints. Use the tools available. Borrow from different disciplines. Prototype an approach. See what works. Adapt.
I’ve discovered that those are the problems I enjoy most.
Coming back to education
Today, much of my work has brought me back to the questions that interested me in the first place: children, learning, and how the experiences we create affect them.
At Lexia Learning, I conduct mixed-methods research across the K–12 ecosystem. My work takes me into classrooms and conversations with students, educators, administrators, and others who experience educational technology every day.
One project might mean sitting beside a kindergartner and watching where a digital experience becomes confusing. Another might involve surveying hundreds of students about motivation and engagement. Another might investigate why educators understand a new product feature differently than the team that created it.
Sometimes the research question has a familiar methodology.
Sometimes it doesn’t.
In those cases, I’m comfortable designing an approach rather than searching for a template—combining methods, adapting techniques to unusual participants or environments, and iterating until we have a way to generate the evidence the team actually needs.
I also work at the organizational level—building research practices, recruitment systems, repositories, governance, continuous-discovery approaches, and ways for teams to engage responsibly with research.
I’m interested in both doing excellent research and creating the conditions that allow excellent research to matter.
The question comes first
After working across academia, product development, consulting, and UX research, I’m not particularly attached to one methodology.
I’m attached to asking the right question and finding the right way to answer it.
Sometimes that means observing a child.
Sometimes it means interviewing a teacher.
Sometimes it means hundreds of survey responses.
Sometimes it means bringing people with very different perspectives into the same room.
And often, it means combining multiple forms of evidence until a pattern becomes visible.
That’s why I describe myself as an interdisciplinary researcher. I draw from behavioral science, child development, human-computer interaction, qualitative and quantitative research, design, product strategy, and systems thinking depending on what the problem requires.
A unique thread woven through varied experiences
My career has taken me from literature to puppetry, children’s television, academic research, educational toys, technology products, consulting, and UX research. On paper, that can look like an unusual path, but it feels surprisingly consistent to me.
I’ve spent most of my life interested in some version of the same questions:
- How do people make sense of the things we create?
- What do children and adults experience that the people designing for them don’t see?
- How do we design for the entire system—not just the most obvious user?
- And when there isn’t already a way to answer the question, how do we create one?
The materials have changed.
Once, they were foam, fabric, wire, and ping-pong balls. Today, they’re interviews, observations, surveys, behavioral data, workshops, and experiments.
The instinct is remarkably similar: understand the problem, work with the constraints, make something, learn from it, and make it better.