About
I design enterprise software that earns trust — and lead the cross-functional teams that make it happen.
12+ years. Regulatory platforms, FinOps tools, data privacy systems, civic tech — software most people never think about until it breaks.
Background
I design for the kind of software most people never think about until it breaks: regulatory review platforms, cloud cost governance tools, data privacy systems, civic engagement infrastructure. High-stakes, data-dense, expert-user products where the interface is the trust layer.
I'm currently at FINRA, designing the workflows examiners use to investigate broker-dealer compliance across millions of financial records — and building working prototypes directly in the engineering environment so design decisions get tested in real code before they get written into requirements. Before that, I built the product design practice at CloudBolt from the ground up, helping take a FinOps product line from $1M to $10M in ARR. Earlier in my career I was a founding designer at WireWheel (later acquired by Osano) and led the redesign of Phone2Action's civic tech platform (later acquired by Quorum) — both cases where getting the UX right early became part of why the company was worth acquiring.
I like problems where the users are experts, the data is dense, and the stakes for getting it wrong are real. If that's the kind of work you're hiring for, let's talk.
Experience
The numbers matter less than what they represent:
Industries
I've worked across industries where design complexity is the norm, not the exception:
Enterprise Software & Cloud
FinOps, DevOps, cloud management, privacy compliance
Financial & Regulatory
Financial services, capital markets, FINRA, international development banking
Defense & Intelligence
GEOINT, DoD cyber training, joint operations, intelligence community
Government & Civic
U.S. courts, U.S. Census, federal HR, civic technology
Healthcare & Life Sciences
Healthcare administration, pharmaceutical
Telecom & Infrastructure
Telecommunications, network operations
Consumer & Retail
E-commerce, advertising, consumer brands
Education
EdTech, K–12, higher education
How I Work
Research first, always.
Every engagement starts with understanding who's using the product, what they're actually trying to accomplish, and where the current experience is making that harder. That means user interviews, usability sessions, behavioral analysis, and competitive review — whatever it takes to replace assumptions with evidence.
Design as a systems problem.
Enterprise software breaks when treated as a collection of individual screens. I work at the interaction pattern level: identifying shared components, decision models, and structural inconsistencies that make complex products learnable and consistent across workflows.
Ownership across the stack.
I'm comfortable holding design, product, and research responsibilities simultaneously — not because I'm trying to do everything, but because that's often what it takes to ship something that actually solves the right problem. In practice this means I write PRDs, run sprint planning, manage stakeholder reviews, and still get into Figma every day.
Tradeoffs made visible.
Good design decisions require shared understanding. I document rationale, surface options clearly, and build alignment so that the decisions we make together hold up under pressure — including pressure from engineers, product leads, and executives who weren't in the room when the problem was first framed.
Building, not just designing.
I prototype in code and ship using AI tools. That means I can take an idea from concept to working product without waiting for an engineering handoff — validating real interactions, catching problems early, and staying grounded in what's actually buildable. This portfolio is an example: designed and built in Next.js, committed to git, deployed to production.
Currently
Building products with AI.
At FINRA, I'm building working prototypes directly in the engineering environment using Kiro — AWS's AI IDE — so design decisions get tested in real code before they get written into requirements. That's a different kind of design practice: closer to the system, earlier in the process, and accountable to what actually ships.
The shift doesn't replace the design practice — it extends it. Research still drives direction. Systems thinking still determines what gets built. But the gap between concept and working product has collapsed in a way that changes what's possible early in a project, and how fast you can validate whether you're solving the right problem.
I'm building a case study around what this actually looks like in practice.
Let's Work Together
I'm available for senior design leadership roles — full-time, contract, and fractional engagements. I'm especially interested in enterprise software where the users are experts, the data is dense, and the stakes for getting it wrong are real.
If that's what you're looking for, I'd like to hear about it.