Get to Know Me
I look beneath the visible experience to understand the systems, decisions, and assumptions shaping it.
For more than 20 years, I have worked at the intersection of customer needs, business priorities, and the systems connecting them. I have learned that what appears on the screen is often the result of decisions made much earlier, such as how information is organized, how responsibilities are divided, which assumptions went unchallenged, and whose needs were prioritized.
That perspective shapes how I enter the work. I begin by understanding the environment surrounding the problem rather than assuming the initial request tells the whole story.
What shapes my work
I am drawn to complex environments where structural issues, competing priorities, and fragmented workflows influence the experience long before a customer or employee encounters it.
I care about the human side of systems and how they shape the experiences of the people who use them. Products do not exist separately from the people, processes, policies, and business decisions surrounding them. When those elements do not work together, the effects eventually appear as confusion, added effort, missed expectations, and lost value.
My approach is to examine those relationships together. I ask how the experience came to work as it does, who is affected by it, and what conditions would need to change for a better experience to become possible.
Where I create the most value
I have applied this perspective to complex financial products, enterprise platforms, customer service ecosystems, subscription services, and connected experiences.
Although the environments differ, the challenges often share familiar patterns: disconnected information, unclear ownership, workflows shaped around internal structures, and product decisions made without a complete view of the customer or employee journey.
I create the most value when a team knows something is not working but has not yet reached a shared understanding of why. I help distinguish visible symptoms from underlying causes, identify which problems are worth solving, and establish a clearer strategic direction before the team commits to a solution.
How I work
My approach blends analytical discipline with visual thinking. I use research, mapping, synthesis, facilitation, and design to organize what the team knows, expose what is still uncertain, and show how different parts of the experience influence one another.
I do not apply the same process to every engagement. I draw from experience strategy, product strategy, service design, information architecture, and product design, depending on the situation.
The goal is not simply to produce an artifact. It is to give the teams I work with a useful way to understand the problem, make informed decisions, and translate those decisions into work we can prioritize and carry forward.
I am also exploring how AI can support this process through synthesis, workflow assistance, and decision clarity. I approach it with the same discipline I bring to other technologies: determining where it strengthens human capability, where human judgment remains essential, and where automation may introduce new friction.
A personal note
I am a maker, a visual thinker, and a persistent problem-solver. I believe good work should carry both integrity and humility. It should make difficult ideas easier to examine without pretending the complexity does not exist.
My experiences through an unexpected career change have also influenced how I work. It has made me more attentive to uncertainty, more willing to question assumptions, and less likely to treat one expected path as the only possible path forward.
That perspective carries into my work and the teams I work with. I try to leave people with greater clarity, stronger decision-making capacity, and more than one viable way to a solution.
To learn more, I write about this at greater length in The Practice newsletter on skills-based careers and independent strategy work.
