How I work
Every design decision balances four forces: the business, the customer, the product, and the technology. Getting that balance right, again and again, is the work.
The four forces
Business
Does the design move the numbers? Every call ties back to revenue, retention, or cost.
Customer
Does the design solve a real problem? Research proves the need before anything gets built.
Product
Does the design raise the bar? The work has to strengthen the product, not just ship.
Technology
Can the design be built well? Design that engineers can ship on time, AI included.
The foundation
The fundamentals hold up under pressure: research, craft, and systems, done right. I'm formally trained in leadership and management at Harvard Business School Online, and I lead the way I work: set the bar, back the team, and hold quality through delivery. That approach showed up as 100% team retention through the Sentry integration.
Toolkit
Nielsen Norman Group certified (UX Management). Harvard Business School Online, Leadership & Management. BFA, Digital Arts.
Capabilities
The why
Design is the fulcrum. The business, the customer, the product, and the technology all meet in the experience, and the design of that experience is where a good decision pivots them into a result. Get the pivot right and everything downstream moves.
That is a measurable effect, not a philosophy. Move a decision to the moment the customer is ready for it and change its default, and adoption climbs, because you have stopped fighting how people behave: they scan, they satisfice, they take the path of least resistance (Jakob's Law, Hick's Law). Show less at once and reveal detail only when it is needed, and revenue per visit rises, because the customer is no longer spending attention to think (progressive disclosure; Miller on working memory). Rebuild a high-stakes flow around clarity instead of completeness, and the conversion rate and the value of each conversion climb together.
The figures are real: one repositioned decision more than tripled adoption; one screen, reworked to show less at once, raised revenue per quote 9%; a core flow rebuilt around clarity closed 6% more at a higher average premium, under budget. The figure is the evidence, not the point. Each came from a specific judgment: which friction to remove, which default to set, what to hide until later, what the research showed people were already doing. That judgment is the work.
Judgment is also the part that does not get automated. AI has made producing nearly free: variants, copy, prototypes, whole flows in minutes. That shift does not lower the value of design; the value moves onto the judgment. When any version can be generated, the only edge left is knowing which question to ask and whether the answer holds up. I build AI into the pipeline to move faster and to widen what a small team can ship. I do not mistake speed for judgment, or treat speed as a reason to cut the people who supply the judgment.
So the standard is simple. Start from the business need. Prove the direction with research. Treat the design of the experience as the fulcrum it is, and move the outcome on purpose.
No. AI replaces the producing, not the deciding, and the deciding was always the job.
AI can generate variants, copy, prototypes, and whole flows in minutes. That is a real change: the cost of making something has fallen to near zero. But making was never where the value sat. The value sits in the judgment a model has no access to: which problem is worth solving, which friction to remove, which default to set, and whether the result actually moved the number or just looked like it did.
When any version can be generated on demand, the scarce skill is not production. The scarce skill is knowing which question to ask, and telling a right answer from a plausible one. So I use AI the way you would use any fast, tireless producer: to widen what a small team can ship and to reach a testable version sooner. I do not hand AI the decisions, and I do not treat AI as a reason to cut the people who make them. Cheaper production raises the value of good judgment and does not remove the need for judgment.
Only when design can't point to a number. Once design can point to one, the function stops being a cost center and becomes one of the cheapest ways you have to grow.
Design decides what the customer actually meets: what gets asked, in what order, what is set as the default, and what stays hidden until needed. Those are not cosmetic choices. They decide whether someone adopts the feature, finishes the flow, or leaves. Change them well and adoption, conversion, and value per customer move, with no new feature shipped.
So I run design like a business unit, not a service desk. Design takes a target, is measured against revenue, retention, and cost, and defends its budget with outcomes like any other function. That also means saying no to work that looks busy but moves nothing, and putting the effort where the number is.
The test is simple, and I hold my teams to it: can you point to the outcome this changed? Design that can't is overhead. Design that can is growth you already own, waiting in the flow.