I work on the parts of a product that are hard to make simple: design systems that have drifted, search and filtering nobody can use, compliance workflows with legal consequences, and machine-learning tooling where the interface has to communicate uncertainty. Eleven years in enterprise software at HP, Micro Focus and Smarsh, first as a front-end engineer and later leading design. I read the codebase, and I hand over work engineers can build from.
Engagements
Design system audit
Two to four weeks
Your component library was right when it was written. Then three teams shipped under deadline, and now there are four buttons, two date pickers and a documentation page nobody trusts. I find the drift, quantify what it is costing you in rebuild time, and give you a structure to converge on.
You get
- An inventory of what exists, what duplicates what, and what is actually in use in production
- Recommended component structure, variants, states and naming
- A documentation model your engineers will read
- A prioritised sequence, so the work can be done in slices rather than a rewrite
UX audit of a complex product
One to two weeks
For products where the difficulty is density rather than polish. Search and filtering, dense tables, dashboards, bulk actions, multi-step flows, permissions. I go through it the way your users do, and tell you which problems are costing you the most and which ones only look bad.
You get
- Findings ranked by user cost and implementation cost, not by severity theatre
- Annotated walkthroughs of the flows that are hurting most
- Concrete recommendations, with the trade-off named where there is one
- A short readout session with your product and engineering leads
AI and ML tooling interfaces
Scoped per project
Model evaluation and comparison, classification review, human-in-the-loop workflows. The hard question in these products is rarely visual. It is where you set the threshold at which the system decides alone, what you show the person who has to overrule it, and how you communicate confidence without implying certainty you do not have.
You get
- Interface design for evaluation, comparison and review workflows
- A defensible position on what the machine handles and what escalates to a person
- Ways of showing error and confidence that survive contact with a regulator
Discovery and concept sprint
About a week
You have a written requirement, or an argument that has been going in circles for a month. I turn it into something concrete quickly, so the team can disagree about an artifact instead of a paragraph. I build these fast, using AI tooling where it earns its place, which is why a week is realistic.
You get
- Wireframes or a clickable prototype, depending on what the argument needs
- The open questions written down, including the ones nobody wanted to raise
- A recommendation, not just options
Embedded design support
Ongoing, part time
For teams who need a senior designer in the room but not a full-time hire. I work alongside your front-end engineers at 20 to 30 hours a week, on your tools, in your standups. Prototypes over specifications.
You get
- Design across features as they come up, at a pace your team sets
- Handover engineers can build from, because I have been one
- Design system contributions that stay consistent with what you already have
How I work
- I write down what I think is wrong before I redesign anything. If we disagree about the diagnosis, the design is a waste of both our time.
- I do not remove things quietly. In regulated products, a control that vanished is a support ticket at best and an audit finding at worst.
- Suggest, never assume. A filter the user did not knowingly apply is a defect, not a convenience.
- I hand over work engineers can build. Eleven years of shipping alongside front-end teams, four of them writing the code myself.
- I tell you when a thing is not worth doing. Including when it is the thing you hired me for.
- Fixed scope where I can price it honestly, hourly where the work is genuinely open ended.
Where I am useful
Starting a conversation
Tell me what is going wrong and I will tell you whether I am the right person for it. If I am not, I will usually be able to say what kind of person is. Available from mid-September 2026, 20 to 30 hours a week, fully remote across the US.
Email meOr see selected work first.