Skip to main content
HB
Hiram BarskyDesigner and Developer
UX / UI Design

Design for products people have to use all day

Most enterprise tools are not competing with other software — they are competing with the spreadsheet someone already trusts. I design the version people actually switch to.

Complex products fail on the boring parts: where the data lives, what happens when it's wrong, and whether the person using it can defend the decision they just made. That's the work.

What you get

Research that changes the build

Interviews and workflow shadowing aimed at one question: what would make someone abandon the tool they have now? Findings come back as design decisions, not a slide deck.

Information architecture

Structure first — what belongs on a screen, what belongs a click away, and what should never have been a feature. Most of the win is in what gets cut.

Interaction and interface design

Real states, not happy paths: loading, empty, error, permission-denied, and the half-filled record someone left open on Friday.

Design systems that survive handoff

Components and tokens built to be implemented, with the edge cases already specified so engineering isn't guessing.

Common questions

Do you do research, or just the interface?

Both, and the research is the part that changes what gets built. If a project has no budget for it, I'll say what I'd do instead rather than skip it and guess.

Can you work from an existing design system?

Yes. Most enterprise work starts inside constraints someone else set. I'd rather extend a system consistently than introduce a second one.

Tell me what you're building

A 30-minute call is usually enough to tell whether this is a fit. If it isn't, I'll say so and point you somewhere better.