I’m a senior product designer at ServiceNow, working on the tooling enterprise teams use to build and govern their automations.
Eleven projects below, each shown at the stage it is actually at. Open any one for the customer problem, the brief, who it was for, what was designed, and how it gets measured.
Find me on LinkedIn, or say hello at neomigraphics@gmail.com.
Six at ServiceNow · five from earlier
Four years designing enterprise automation, and a few more before that in consumer product and brand.
Almost everything I design is workflow automation: the tooling enterprise teams use to build, govern and run the automations their business depends on. The interesting part is that it always has two audiences at once. The platform owner needs control and visibility. The citizen developer needs the thing to just work. Most of my decisions are about serving both without asking either to compromise.
It also means working at the level of the system rather than the screen, so accessibility and design-system consistency hold across product lines instead of one feature at a time.
I work in an AI-augmented process. I brainstorm, prototype and write production front-end code with Claude Code, then deploy to pre-prod alongside engineering instead of handing over a spec and waiting to see what comes back. It shortens the distance between a design idea and something a person can actually click. This site is one output of that process.
Before ServiceNow I led the end-to-end redesign of Warranty Keeper across iOS and Android and ran its product and company rebrand, and spent three years freelancing brand and product work for startups and small businesses.
Five things that show up in every project above, whether it shipped or not.
Repeated small bugs usually share a root cause. I trace them back and get alignment on the cause before code is touched. The alternative is seven pull requests that each reimplement the same fix and lock the pattern in.
Fixed, filed, or needs a decision. Engineering should not receive a flat list to triage themselves. And “reviewed and fine” should never look the same as “not yet reviewed.”
A first publish is light. A publish with dozens of consumers shows its blast radius. A delete with dependents blocks outright. Keep the common path fast; put the guardrails only where they earn their cost.
A one-time audit became a checklist anyone could run. A status doc became a dashboard that scaled from 7 stories to 40. The method should outlive the project.
Discovery-stage work stays labelled discovery. Targets stay labelled targets. A seam in the system gets documented rather than papered over, and a prior decision gets challenged when the evidence contradicts it.
Open to conversations about product design in complex, automation-heavy software, or about anything above.
