Now Assist Suite | UX research case study
Nancy Nguyen
UX research case study
Company: ServiceNowProduct: ServiceNow Store

Now Assist Suite: Evaluating a New Feature to Streamline App Deployment Before Launch

In a complex enterprise system, a single app update can cause a domino effect that breaks surrounding tools. To prevent this, I spearheaded pre-launch research, testing a new app-bundling feature with real system admins.

🔒 Some internal names, participant details, and figures have been generalized to respect confidentiality.
Desktop monitor showing the Now Assist Suite install window, with a Suite version picker and the related apps that will be updated

Role

UX Research Intern

Timeline

3 months

Skills

  • Concept testing
  • Research planning
  • Synthesis and analysis
  • Workshop facilitation

Tools

Figma
Miro
Great Question
Zoom

Results at a glance ✨

Easier Deployments, but Less Control

Simpler deployments were a clear win for admins. The tradeoff was control: when one update touches several apps at once, they needed to know exactly what would change before they'd trust it.

Validated the concept before launch

All participants could explain the new bundle correctly after a single try, giving the team confidence to move forward.

Shaped the launched design

7 recommendations are visible in the launched product, from upfront error warnings to a simpler version layout.

Improved the help content customers use

Reviewed drafts of the public setup guide for Suite, shaped by what admins told me they were missing.

Aligned the team on a design plan

Led a prioritization workshop with the designer, PM, and engineering team, where we aligned on recommendations and when to act on each.

Executive summary slide: key takeaways on strong support for Suite, gaps in communication and visibility, and the importance of error notifications

My role

UX Research Intern
Sole researcher on this study, from planning and recruiting to analysis and final delivery

Nancy Nguyen introduced as an Emerging Talent UX Research Intern at the ServiceNow intern showcase
  • Created a research plan and interview guide to test whether admins could understand Suite and see its value without any explanation.
  • Designed task-based prototype tests across 3 common admin tasks.
  • Translated findings into design recommendations, ranked by user impact and split into quick wins and longer-term opportunities.
  • Facilitated a prioritization workshop with the designer, PM, and engineering team to agree on what to fix and when.
  • Presented final recommendations and insights to leadership by the given deadline.

🌱 Why I took this on

The ServiceNow Store team planned to finalize designs by October for a December launch. They needed research to validate the concept, but no one owned the research. And that's where I came in!

Background

One update could quietly break everything else

Now Assist is ServiceNow's family of generative AI apps, with a separate app for each team, like IT service, HR, and customer service. Most companies run several of them side by side. They look like separate products, but behind the scenes they all rely on the same shared components.

The problem? If you update one, the rest may fail.

Solution

Now Assist Suite bundles compatible versions together into a safe, one-step installation.

Application Manager
Launched Review Installation Details screen: pick a Suite version, see each app's status, app version, and a demo data option
Suite today: pick one bundle version, and every related app updates to versions tested to work together.

Why it mattered

Suite supports three goals for ServiceNow as an AI platform company:

✨ Easier AI adoption

Customers want AI without a complicated setup. Simpler installs make it easier to start using it.

📈 Managing many apps at scale

Bundling can extend beyond Now Assist to other products with shared components.

🧩 Less complexity and cost

Fewer errors, fewer support tickets, and less time spent on updates.

Research approach

What we needed to know before launch

Problem

Customers were frustrated because their Now Assist capabilities were randomly breaking after updates.

Admins were frustrated because they had to spend extra time troubleshooting.

Goal

Evaluate the usability, comprehension, and perceived value of Now Assist Suite, and identify pain points and opportunities to improve the experience.

Research questions

  • What are the overall impressions of the new Suite concept?
  • Can users comprehend the term "Suite" as a function to manage Now Assist applications in a single bundle?
  • Are users able to describe the relationship between the Suite and App versions?
  • Do the install and update flows match user mental models and expectations?

Research journey

Validating the concept with real users

6 admins, 3 real scenarios, 2 weeks: I watched how people actually moved through the new flow, then turned what I saw into recommendations the team could act on.

  1. Phase 1PlanRecruit the right admins
  2. Phase 2Test6 prototype sessions
  3. Phase 3SynthesizeFindings and workshop
  4. FinalOutcomeLaunched in the admin tool

👆 Select a phase to see how it unfolded.

🧩 Phase 1 | Planning and recruiting

Finding the people who manage these updates

Suite was a brand-new idea, so feedback had to come from people who actually live with these updates. I recruited 3 customers who manage their own ServiceNow setup and 3 implementation partners who install apps for their clients, all with hands-on experience with these AI apps.

🔬 Research methods
  • Participant screening
  • Research plan
  • Discussion guide

🧭 The rationale

Why customers and partners

Customers live with the results of an update. Partners run updates across many clients. Together, they covered both everyday and at-scale use.

Why hands-on experience mattered

Most participants had also customized their apps, which let me test the trickiest scenario: updating an app that no longer matches its original version.

Participant overview: 3 Now Assist customers and 3 implementation partners, with job titles and whether they manage customizations
Who I talked to: 3 customers and 3 implementation partners. Company names are blurred for confidentiality.

Key insights

What admins needed to trust a bundled update

Four insights, each tied to a change the team made.

1

Once people tried it, they understood it

The word "Suite" meant little at first. After one pass through the prototype, all 6 participants could explain it as a bundle of app versions that work together. They just wanted that explanation upfront, where they already look for details.

"There should be detailed documentation: 'What does this Suite mean?' so that it doesn't confuse the admins."

✅ Outcome

ServiceNow published public setup guides for Suite. And I was invited to review the draft.

What launched
ServiceNow documentation page: Now Assist suite versions in the Application Manager
ServiceNow KB article, view here
Support article: Install Now Assist Using the Suite Model, with step-by-step instructions
Instructions to use Suite, view here
2

Admins wanted a safe preview before big changes

One bundle update could change many apps at once. Admins wanted demo data so they could test the new version before it touched real work. I shared this directly with the engineering and product teams.

✅ Outcome

Demo data moved from a small corner option to its own column beside every app on the install screen.

What launched
Launched install screen with a Demo data column beside each app
3

Trust meant seeing the impact before clicking Continue

Most participants liked doing fewer manual updates. What made them hesitate was losing control: a bundle could update apps they never planned to touch.

"Understanding that compatibility is important... not having that granular control freaks me out."

✅ Outcome

The PM strongly agreed this was a priority. Today, admins can track exact changes in the monthly Now Assist Suite release notes.

What launched
Monthly Now Assist Suite release notes, March to September 2026
4

Errors had to show up early

Participants found out about missing licenses deep in the flow, after they had already invested time. They wanted problems flagged before they started.

"I would appreciate seeing [errors] straight away so I can deal with the problems before I go through my rabbit hole."

✅ Outcome

The launched install screen flags the exact blocked app at the top and greys out Install until the issue is fixed.

What launched
Launched install screen with an Installation blocked label on one app in the Suite
Launched install screen with a red message to install dependent apps first, a Needs to be purchased label, and a disabled Install button

Challenges

What made this hard

⚠️ The challenge

Before sharing my report, I was eager to take as much advice from researchers as possible. And by trying to satisfy every piece of feedback I got, my story completely lost its focus.

Steps I took to overcome it

  • Trust the research. I had to have confidence in my findings and the story they told.
  • Sort the feedback. Not all feedback is created equal. I grouped comments into three buckets: critical, secondary, and stylistic opinion.
  • Strip it back. I wasn't afraid to cut the report down to its outline and make sure the essentials came first.
  • Prioritize the goal. Every slide had to serve what the study set out to answer.

Reflection

This project laid my foundation in UX research.

I'm grateful for the trust and autonomy my manager gave me to lead the study end to end, and for a team that always made time to answer my questions. Two lessons stuck with me:

Lesson 1

🔍 Report what you saw, not how people felt

My first draft said participants "liked" Suite. My director pushed me to state the observation and what it means instead. "All 6 could explain Suite after one try" says far more than "they liked it."

Lesson 2

📋 A readout isn't the finish line

The final readout didn't mean my job was over. Laying out next steps and scheduling a dispositioning meeting with design, product, and engineering made sure the research was heard.

"I'm really impressed [with] how you've approached this entire project... this is above and beyond."Feedback from my manager (UX Research Director)