Four years of data-heavy dashboards, operational workflows, and internal admin tools — mostly for large-scale organizations in healthcare, industry, utilities, and government. I'm good at finding the clear process hiding inside the mess of data, conflicting requirements, and legacy decisions — partly because I used to be the user of tools like these myself (more below).
Food R&D at Tzabar, regulatory affairs at Abbott, project management at Sher, and three years at Intel as a process engineer. In every one of those roles I was the end user of complex enterprise software.
The exposure to many kinds of organizations, production floors, and people is the part I actually carry into design. I'm comfortable talking to engineers, operators, and managers — I've sat in rooms with all of them from the other side.
Every complex product has a clear process underneath — but it's usually hidden beneath forms, tables, and legacy decisions. Surfacing it is most of the work.
A lot of enterprise tools rely on "ask Sarah, she knows how." When a new hire can't navigate the system on week one, the complexity is in the wrong place — in their head instead of in the interface.
Most projects jump straight into Figma before anyone has mapped the actual workflow on paper. I try to stay out of Figma as long as I can — and it saves a lot of rework later.
