About
Many things these days, but not always a product designer.
My name is Dan and I'm many things these days—a cyclist, an aspiring chef, a husband, a father of two amazing daughters, an adult fan of lego (AFOL)—but I haven't always been a product designer, and my path was anything but straight.
My obsession with problem solving and design first manifested through the built environment. Studying urban design and landscape architecture, I was fascinated by how our surroundings could facilitate collaboration, art, and environmental sustainability. This path took me into the realm of technology as I explored the canvas of public spaces through social networks, sensors, and energy generation—designing accompanying digital experiences increasingly became an essential part of my process.
Somehow on the other end of this all—in very uncertain economic times—I was able to start earning a living designing and building websites instead of drafting plans inside an architectural firm. After spinning up an iPhone accessory business with some friends, returning to school for an MFA, and embarking on a freelance Creative Technologist journey that included helping design a spacesuit, I found that despite having little exposure to training in traditional User Experience that my process—one rooted in research, iterative design, and analysis—was a perfect fit for industries where UX was emerging as an essential function.
I quickly found working in UX and product design to be fulfilling, not just in championing the needs of users within a digital space but in making an impact in the businesses that increasingly blended the boundaries between our physical and digital lives. The roles that I took on deepened my knowledge of design practice across the full spectrum of the design process, from research and IA to interaction design and design operations.
Process
The shape is never symmetrical.
The double diamond is a useful framework to articulate the anatomy of a project — Discover, Define, Develop, Deliver. I wish it were this simple in practice, but nothing ever aligns perfectly with this process. The shape is never this symmetrical.
Some projects live almost entirely in the problem space, where the answer is mostly about getting the framing right. Others run tight on discovery and live in the back half — iteration, system, handoff. Each case study's side nav carries a small diamond glyph showing its actual phase weight.
Symmetric (the textbook)
Almost no project actually moves like this.
Discovery-heavy — Platform as unifier (TM1)
Long-running, cross-org problem space; the answer was mostly about getting the framing right.
Develop-heavy — SMARTS
Domain understood quickly; most of the effort lived in iterating the visualizations and workflows.
Delivery-leaning — PeerStreet
Tight scope from day one; design system + handoff carried as much weight as the design itself.
A second axis
The know/do spectrum.
Another thing that guides my work is where a given project falls on the "know" and "do" spectrum. Designing for each often involves different heuristics — and I've never known a project to completely encapsulate them both.
The know can be found externally and the do in-product — and vice versa, the product providing the know but a collection of external tools to provide the do. In each of these situations and the many in-between, it really is a spectrum. It's important to consider the overall journey, the jobs to be done, and where design can effectively intervene. It may sound intuitive, but I've encountered platforms and products that suffer an identity crisis in their failure to understand their positioning.
Strengths
How I show up at work.
I recently had the opportunity to take Gallup's CliftonStrengths assessment to better understand the characteristics that guide me at work and life more broadly. The characteristics felt familiar — I had never put a name to them. I found it incredibly insightful, especially in discovering them alongside my product and design peers, and feel they're an interesting glimpse into how I approach problems and what I bring to any organization or team I work with.
TL;DR
I'm an information sponge and I love to learn about new things and domains. I use this information to approach problems from unique angles, creating compelling visions that simplify the complex, formulating strategies grounded in analysis of evidence (qualitative and quantitative), building consensus through collaboration, and ideating on solutions that focus on simplicity, clarity, and reusability — ultimately delivering high impact outcomes.
How I work
Working together.
[Draft] Beyond full-time employment, a few formats I'm open to for side projects and consults. The shape and length flex with the problem.
Advisory call
30 min[Draft] A focused conversation about a specific design, product, or strategy challenge — useful when you need a sounding board, not a deliverable.
1-week sprint
1 week[Draft] Diagnostic, strategy memo, or focused design exploration. Good for de-risking a direction before committing to a longer engagement.
MVP build
4–8 weeks[Draft] Concept to working product across design and code. Best fit for 0→1 work where you need fewer hands and more ownership.
Fractional design partner
Ongoing[Draft] Embedded design leadership for a small team — strategy, system, and IC craft as needed.
Best fit
[Draft — describe the kinds of projects, teams, and problems where you do your best work. e.g. founder-led 0→1 product, a complex enterprise tool, a research-heavy strategy engagement.]
Not a fit
[Draft — describe what you'd politely turn down. Filtering up front saves everyone time.]