Most designers make things look good. I get hired when a product has grown so complicated that nobody can use it anymore — and someone has to make sense of it.
I came from IT before I came to design. That means I don't hand over a screen I can't explain to an engineer.
Most of my work lives inside products that other people have to operate every day — a recruiter running 200 candidates through a pipeline, an HR admin closing payroll, an ops team reconciling an ERP. These products don't fail because they're ugly. They fail because nobody mapped the actual workflow before designing the interface.
So I start where the mess is: the edge cases, the permissions matrix, the state nobody documented. Then I design the system that holds all of it — components, patterns, and rules that stay consistent as the product grows past the screens I drew.
I work best embedded with a team, close to engineering, over a long enough window to actually see decisions ship and get corrected.
Mapping real operational flows before drawing a single screen.
Component libraries and patterns built to survive team handover.
Dense data, permissions, multi-role dashboards, admin tooling.
Specs engineers can build from without a follow-up meeting.
iOS, Android, and web from one coherent system.
