I don’t start with features. I start with clarity.
Most product friction isn’t caused by bad engineers or bad ideas—it’s caused by misalignment. Teams solving different problems, working from different assumptions, or optimizing for different outcomes.
My job is to remove that friction by making things clear: what we’re solving, why it matters, and how we’ll know it’s working.
That clarity shows up everywhere—roadmaps, APIs, architecture decisions, backlog priorities, and communication across teams.
When clarity leads, teams move faster, build better systems, and trust each other more.
Transitioning a legacy desktop application into a scalable SaaS platform required more than a technical rebuild—it required aligning product, engineering, and business around a new way of operating.
I focused on reducing friction by improving clarity across the system:
The result was clearer decisions, more consistent delivery, and a stronger foundation for scaling the product.
A front-end project built to create a simple, structured experience around exploring Wisconsin through a home page and city-focused pages.
I focused on structuring content and navigation in a way that reduces friction and makes information easy to explore.
The project gave me a concrete way to connect technical learning with user experience, structure, and communication.
View Project on GitHub →