Complexity,clarified.
As roles blur and tools turn over, the lasting skill is framing the right problem and thinking your way to an answer.
Areas of focus
Six threads of one practice. Any engagement pulls on several at once; the breadth is the point.
Experience strategy & design
Most work that fails isn’t ugly. It solved the wrong problem, beautifully. So I push on direction before craft: what are we actually trying to change, who for, and how we’ll know it worked. Get that part right and the design gets both easier and far more useful, because nobody’s guessing anymore about the things that matter. The flows, the words, the interaction patterns all follow from it.
Information & systems architecture
Underneath every large digital product are two kinds of structure: how the content and navigation are organized, and how the platforms and systems behind them connect. I work both. A sitemap running into the thousands of pages, a taxonomy spread across a dozen sites, a CMS still carrying decisions made years ago. When the architecture is sound, the product grows without strain. When it isn’t, every addition makes the whole thing harder to use and to maintain.
Research & behavioral insight
I came into design through behavioral psychology, so I’m wired to ask why people behave the way they do, not just what they clicked on. Opinions are cheap and meetings are full of them. I’d rather put the work in front of real users and let them prove me wrong early, while it’s still cheap to change course. Research earns its keep when it stops a confident team from confidently building the wrong thing.
Content strategy & operations
Launch is when content problems start, not when they end. Pages pile up, owners move on, standards drift, and a couple of years later nobody can find what they need or trust what they find. I treat content as a system: real models, editorial standards, and the governance to keep it healthy after the original team has scattered. It’s unglamorous, and it’s usually what separates a site that ages well from one that slowly rots.
AI strategy & operations
The more AI takes over the production, the more it all comes down to judgment, which is the one part it can’t do for you. I lean on it constantly: a prototype standing in minutes, a second opinion that pokes holes in my own thinking, the grunt work cleared so my attention goes where it counts. I’m still the one deciding what’s right, every time. And a good chunk of my work now is helping teams bring these tools in with some discipline, so they get the speed without quietly lowering the bar.
Leadership & delivery
I do my best work in the gap between an ambitious vision and what a team can actually ship this quarter. That means owning a piece end to end, turning business goals into requirements people can build against, and growing the designers around me as we go. As the specialties keep folding into one another, the people who matter most are the ones who can hold the whole picture and keep a cross-functional team pointed the same way. That connective role is the one I keep gravitating toward.
- 0+
- years
- 0+
- projects
- 0+
- organizations
Concentrated in healthcare & higher education
Toolkit
Tools change; the thinking transfers. The first in each group is the one I reach for.
Design, prototyping & systems
Where I model structure and behavior and make the system reusable. Fidelity scales with risk; the goal is understanding, not polish.
- Figma
- Sketch
- Axure RP
- Zeplin
- Claude Design
- Design tokens
- HTML / CSS
- Adobe Creative Cloud
Architecture, strategy & mapping
Where ambiguity is cheapest to remove. Taxonomies, inventories, governance tables, and decision-space mapping with teams in real time.
- Google Sheets
- Miro
- FigJam
- MindNode
Content strategy & operations
Content as a system, not a pile of pages: inventories, models, editorial standards, and the governance that keeps it healthy at scale.
- Airtable
- GatherContent
- Hemingway
Enterprise CMS & platforms
Real platforms with legacy decisions, governance constraints, and long-term consequences. Complex content models and multi-site ecosystems.
- Drupal
- Sitecore
- Webflow
- Framer
- Optimizely
- Contentful
- Ingeniux
- WordPress
SEO & organic discovery
Technical SEO and the structure that makes a large site findable, not just crawlable.
- Screaming Frog
- Google Search Console
- Semrush
- Ahrefs
Research, testing & analytics
Signal that ties to decisions, not debate, across generative and evaluative, qualitative and quantitative.
- GA4
- Adobe Analytics
- Google Tag Manager
- Optimal Workshop
- UserTesting
- UserZoom
- Qualtrics
- Hotjar
- Crazy Egg
Accessibility
Built in, not bolted on: auditing and testing against WCAG so the experience works for everyone.
- axe DevTools
- WAVE
- Lighthouse
- Stark
- Siteimprove
Delivery & collaboration
Translating intent into buildable work with clear ownership, and documentation that survives the sprint.
- Jira
- Confluence
- Slack
- Microsoft Teams
- Asana
- Monday
- Smartsheet
- Notion
- GitHub
Data & AI
Leverage, used carefully. Synthesis, drafting, prototyping, and QA, to give judgment more time, never to replace it.
- Claude Code/Cowork
- ChatGPT / Codex / Atlas
- Gemini / NotebookLM / Stitch
- Midjourney
- v0
- Cursor
- Relume
- n8n
How I work
The questions clients and hiring managers actually ask, answered straight.
How do you work differently?
I spend more time at the start than people expect. Before I’ll commit to a direction I want to understand the problem well enough to explain it back in plain words, and that usually means asking the questions everyone else skipped past. I judge the result by whether people can actually do what they came to do, not by how the deliverable looks in a review.
What does your process look like?
There’s a loose rhythm to it. Discover, define, design, deliver, then iterate. I bend it to fit the project instead of running it like a checklist. Mostly I’m chipping away at the unknowns one at a time, until the team has enough confidence to ship without crossing their fingers.
How does AI fit into your process?
It’s in most of my working day now. A prototype standing by the end of a meeting, a second opinion that argues back, the production work cleared so my attention goes to the decisions. The judgment stays mine: what’s worth building, what good looks like, what actually ships. And a growing part of my practice is helping teams adopt these tools with enough discipline that the speed doesn’t cost them their standards.
How do you work with cross-functional teams?
I get in with engineers, PMs, and stakeholders early, not at handoff. Work goes sideways when design happens off on its own and gets tossed over a wall, so I’d rather everyone own it together from the start. In practice that’s writing things down clearly and keeping feedback moving both directions, instead of showing up with finished answers.
How do you make sure the work drives impact?
I try to pin down what success looks like up front, then keep checking against it. Usability testing tells me one thing, analytics tells me another, and between them I can usually see whether a change actually helped anyone. If it didn’t, I don’t treat it as done.
What kinds of projects are the best fit?
Complex ones. Content-heavy platforms, legacy systems with years of decisions baked in, organizations where a dozen stakeholders each own a piece of the problem. Most of my work lives in healthcare and higher education, where the constraints are real and the stakes are personal. If a landing page would solve it, I’m more than you need. If nobody can draw the whole system on one whiteboard, that’s exactly where I want to be.
Why bring you onto the team?
Because the production part keeps getting easier and the thinking part keeps getting harder. As the roles blur, what teams need is someone who can figure out what’s worth building and then carry it through the parts where things usually stall. I’m good at walking into a tangled problem and getting people moving again. The work tends to come out better for it, and people end up proud of what they shipped.
Background
The short version.
Psychology first, then a master’s in user-centered design, then ten years of practice. The full timeline and education live on the about page.
- Current role
- Director of Experience, Primacy
- Education
- M.S. User-Centered Design, BrandeisB.S. Behavioral Psychology, UMass Boston
- Experience
- Eight years at Primacy, individual contributor to Director
Let’s untangle something complex.
If you need a partner to bring order to a complicated digital problem, that’s exactly the work I want. See how it goes in practice, or get in touch.