Hi, I’m Neomi Livshitz

I design the tools enterprise teams build their automations in

Senior product designer at ServiceNow, working on enterprise workflow automation and the design system behind it.

I design for the platform owner who needs control and the person building a flow who needs it to work, and I take it through to shipped code on iOS and Android.

View my work

Case studies

A selection of projects where I untangled complex systems and took a product end to end, from framing the problem to designing and shipping the solution, using the latest AI tools.

The Triggers list in Workflow Studio, with published and draft statuses side by side

Workflow Studio: Trigger Architecture

Designing an enterprise-grade trigger experience for modern workflow orchestration
One finding, with what was on screen beside what was meant to replace it

The AI-Powered Delivery Model

Driving cultural transformation from multi-tool review queues to designers owning the repository, with delivery roughly ten times faster
A flow on the canvas, with one branch collapsed to a badge showing its step count

Diagram View Revamp

Years of design debt, scoped into one vision
The Warranty Keeper item list, with the time left on each warranty drawn as a bar under it

Warranty Keeper

A live app, redesigned for clarity

About

I’m Neomi.

I’ve been designing for about seven years. Currently I design workflow automation at ServiceNow: the tools enterprise teams use to build, govern and run the automations their business depends on. There are always two people in the room: the platform owner who needs control, and the person building a flow who needs it to work. I decide where the line between them falls, and I argue for it.

Before that I led the redesign of Warranty Keeper on iOS and Android, including the product and company rebrand.

I’m based in San Jose, and in my free time I like to sew, bake and eat good food :)

How I work

Six principles that guide every project, from initial framing to production.

Start with the problem, not the request

Feature requests rarely describe the actual problem. I trace them back to the underlying friction: who is doing what, how often, and at what cost. Solving the root cause beats shipping seven separate patches that entrench the same broken pattern.

Ground the scope in evidence

Direct research with the people using the tool, paired with hard data: drop-off rates, usage metrics, and systematic audits of existing workflows. Scope is defined by user and system constraints before a single screen is drawn.

Map every persona the decision touches

A shared workflow object serves authors, consumers, technical extenders, and adjacent teams. I map their conflicting constraints upfront and treat those trade-offs as the core design challenge, not edge cases to solve later.

Design complete systems, not isolated screens

I map end-to-end paths first: creation, consumption, bulk updates, divergence, and deletion. An interface that looks clean in isolation often breaks on path four. Finding that mismatch in an architectural flow is vastly cheaper than discovering it in code.

Specify behaviours and edge states explicitly

A thorough spec covers every state visually: empty, error, permission limits, and destructive actions with downstream dependencies. Friction is scaled to risk, every rule includes its rationale, and unresolved edge cases remain explicitly labelled until closed.

Prototype early and build close to the code

Prototypes exist to test assumptions with engineering and research before decisions harden. Every finding gets tracked to an outcome: resolved, filed, or escalated. I bridge design and implementation directly, whether that means pairing on technical edge cases or contributing directly to the front-end codebase.

What I work in

Design
  • Figma
  • Illustrator
  • Photoshop
  • After Effects
  • Blender
Collaborate
  • Miro
  • Notion
  • Microsoft Loop
Code
  • VS Code
  • Terminal
  • Git
AI
  • Claude Code
  • ChatGPT
  • Gemini

What people say

Recommendations written on LinkedIn, quoted in full.

Every project I work on with Neomi, I’m impressed. She brings thoughtful questions to our meetings. Her design artifacts are well thought through, center the user, and deftly solve complex problems. I’ve seen her calm, and cheerful under a lot of pressure.

Neomi is at the forefront of her field as a design engineer, moving with ease between Figma and Claude Code. She was one of the designers leading the code revolution on our team, with multiple PRs merged into our code base each week. She took designs from early problem space to that final 10% polish in the codebase. Truly impressive and a joy to work with.

Marli Renee Senior Product Designer Same team, August 2026
Neomi’s creative design has allowed us to break out of an old stale look. We took her as a product designer for our mobile app and she has taken our core values and incorporated them into a design that gives a professional and pleasing look.

Her designs and creative ideas breathed new life into the product. She was there through the creative conception to the delivery. Working with her is a pleasure!

Yaron Malin Engineering Team Lead, Melio Was my client, February 2022

Awards

Net New Innovation Days is the ServiceNow Platform organisation’s annual three-day event for building new ideas for the platform.

First place at Net New Innovation Days 2024, and the UX-cellence Award

I am thrilled to share that myself and my team Kiran Ramanna, Lyena Solomon, Neomi Livshitz and Jatinder Bains won 1st place at our 2024 Net New Innovation Days last week! Alongside this achievement, we also bagged the UX-cellence Award!

Monicaa GopiKrishna Senior Product Designer at ServiceNow Announced the win, April 2024
ServiceNow 2024 Net New Innovation Days winner card The prize: a Net New Innovation Days bottle, notebook and stickers

Let’s talk

Write if you want to talk about product design in automation-heavy software, or about any of the work above.