SERVICE DESIGN LEAD

I make complicated things make sense.

I'm Stacey — 20 years in design, the last 10 in service and product design across financial credit ratings workflow platforms, enterprise IT, cloud network operation platforms, and video streaming mobile app, including AI-enabled workflows. I turn stalled migrations and tangled workflows into journeys thousands of people can actually follow.

Service DesignProduct StrategyUX DesignEnterprise ITChange ManagementProduct Management
Portrait of Stacey Zhou
Selected Work

Two bets where strategy met craft.

Case Study 1
Service DesignEnterprise ITChange ManagementM&A
Case Study 2
Service Design0 → 1WorkplaceGlobal Rollout
Shots

Small changes. Measurable impact.

Service designUX writingServiceNow

One error message, rewritten to take an engineer out of the access queue

The “no access” screen on ServiceNow dashboards told people to contact the reporting engineer. They handled about 15 access requests a week by hand, which took time away from building dashboards.

15→0

requests / week
to the engineer

Before

Support Group Dashboard Access

If you cannot see any scores and require access to ServiceNow support group data, please contact John Doe to gain access to the dashboard.

After

Support Group Dashboard Access
1

Can’t see this dashboard?

You’re not a member of an assignment group for this dashboard in ServiceNow. Access requires group membership.
2

To join this assignment group

Search for this Request form via the Service Portal: "Manage ServiceNow Assignment Group", then:
3

1. Choose an assignment group that you would like to join2. Add or remove members from group
  • × No reason given for the block
  • × Sends every request to one person
  • × Skips the existing access process

1. Explains why. Tells the user what’s missing, not only that they’re blocked.

2. Uses the existing form. Points to the standard request instead of a person.

3. Lists the exact choices. Requests reach the right queue with the right category.

Request path · Before

Dashboard user
Reporting engineer

Handled manually, outside any queue · ~15 / week

Request path · After

Dashboard user
Access form
IT access team

Tracked in the standard queue · engineer back to building dashboards

How I Lead

I lead by doing what's right, not by being right. I set a clear direction, hold myself accountable to it, and stay humble enough to change course when the evidence says I should.

I help teams move from fuzzy intent to shipped product through strong strategy, practical collaboration, and systems that compound.

01Principle

Clarity over chaos

I turn high-pressure, ambiguous situations into a clear plan the team can actually execute, a roadmap they can follow even when the environment around them is still uncertain.

02Principle

Honesty over comfort

I lead by telling people the truth, even when it's uncomfortable, and I hold myself to that same standard. The best outcome for the product and services and the user matters more than being the one who's right.

03Principle

Ownership over task completion

I care less about whether a task got checked off and more about whether the team feels real responsibility for what we build and serve. People do their best work when they understand why it matters, not just what's due.

04Principle

Outcomes over output

A design that doesn't solve a real problem isn't doing its job, no matter how polished it looks. I anchor every decision to a measurable result, not to how impressive the work looks in a deck.

About

Calm under ambiguity. Specific about craft.

I'm a service design leader and hands-on contributor who specializes in turning fragmented, high-pressure enterprise initiatives into structured, human-centered systems that actually work. My background spans high-stakes sectors from financial credit ratings workflow, employees experience, to global enterprise operations where the cost of a broken workflow isn't just user frustration, it's measurable business risk. I've spent my career learning to operate inside that pressure rather than around it.

My leadership philosophy is built on humble ambition and radical accountability: doing what is right over simply being right. I don't just solve for the product, I solve for the trust between teams that has to exist for any large-scale transition to succeed. That means building the case, the coalition, and the plan that makes the right outcome undeniable, even when I'm not the most senior person in the room, and even when the first answer I get is no.

I treat culture as a team's operating system: if the "how" isn't intentional, the product built on top of it won't be either. When things go wrong and in complex and cross-functional work, my response isn't to deflect. It's to own the mistake immediately, fix it fast, and build a process so it doesn't happen again.

At the center of how I lead is a real commitment to my people's growth. I'm constantly looking for ways to help my team members succeed in their careers, creating opportunities for them to shine, and giving them the constructive feedback that helps them keep growing, even when that feedback is hard to hear. I never give up on a team member's growth. I see that as my responsibility, not a nice-to-have, and it doesn't stop at my direct reports. I show up the same way for people who report to me indirectly, because their growth matters just as much as a team working on the same project. I believe in transparency over simple honesty: being proactive about what I share, so the team stays informed, collaborative, and equipped to do their best work, not just told the truth after the fact.

Design, to me, is only valuable if it solves a real problem, otherwise it's just art. I use design to bridge the gap between user's needs and meeting business goals, and work directly with the engineering team through co-creation, not handoffs, and I translate usability into the language leadership actually responds to: reduced ticket volume, faster time-to-productivity, measurable ROI. I stay hands-on with technical feasibility long before development begins, pressure-testing ideas against real-world constraints, so strategic momentum never gets lost to a late-stage rip-and-replace.

I lead with psychological safety and radical candor because innovation only happens when people aren't afraid to fail, Design Thinking is one of the classic example for innovation to happen. And I measure my own success the same way I measure my designs: not by whether I was right, but by whether the outcome for the service, the product, and for my people was.

CONTACT ME

Let's talk design leadership

Open to senior design leadership roles that treat strategy, systems, and craft as equally important. Resume, references, and deeper case studies available on request.