The “Why is this form so long?” moment
I’ve watched brilliant people freeze in front of a simple request form. Not because they can’t do the work, but because the portal threw twenty fields at them in one go. Some were relevant. Most weren’t. The user’s brain did what it always does when it feels trapped. It looked for an exit. That exit is usually by email.
This is one of the most common adoption killers in ServiceNow portals. Overload creates avoidance. Avoidance creates tickets. Tickets create cost.
Progressive disclosure is the opposite approach. It gives users what they need, when they need it, and nothing more.
The pain point you hear from every department
- HR leaders hear: “I tried, but I didn’t know what to choose.”
- IT leaders hear: “The form is a nightmare, I’ll just call.”
- Finance leaders see: More rework, more misrouted requests, more time spent on admin.
The root issue is the same. Too much information up front.
What progressive disclosure means in plain English
Progressive disclosure means you show the essentials first, then reveal extra detail only when needed. It keeps users moving.
Think of it like a good conversation. You don’t start by asking every question you could possibly ask. You ask one, listen, then ask the next.
Where to use progressive disclosure in ServiceNow
1) Topic pages
Topic pages are perfect for this. Separate “Requests” from “Articles” so users don’t have to scan a mixed wall of content. Then add FAQs to handle the quick questions that would otherwise become tickets. This is a simple structural win:
- Users find the right thing faster
- Search results feel cleaner
- Deflection improves because answers are easier to spot
2) Catalogue items and record producers
Long forms create fatigue. Form fatigue kills completion. Use progressive disclosure patterns so the form unfolds as the user goes:
- Start with the core request
- Reveal extra fields only if the user selects something that needs them
- Group fields into sections with clear headings
- Use tabs or accordions so users can focus
3) Order Guides for multi-step journeys
Some requests are naturally complex. New starter setups, equipment bundles, onboarding, departmental moves. Order Guides can help you break big tasks into small, manageable steps. Users stay oriented. They can see progress. They feel in control.
That feeling matters more than you think. It’s the difference between “this is easy” and “this is a hassle”.
The real goal: Reduce cognitive load
Cognitive load is the mental effort required to complete a task. When you overload a page, users slow down and make mistakes. Progressive disclosure reduces cognitive load by:
- making pages scannable
- reducing decision fatigue
- keeping attention on the next best action
- lowering error rates and abandoned requests
This is why it improves time to task and satisfaction, not just “design”.
A simple pattern leaders can push into the backlog
If you want one practical change that pays back fast, do this:
- Identify your top five catalogue items by volume
- Review each form and remove any field that does not change fulfilment
- Hide conditional fields until needed
- Group what remains into clear sections
- Add a short FAQ block on the topic page to catch obvious questions
This is small, safe work. It also changes behaviour quickly.
How to tell if you’ve gone too far
Progressive disclosure is not about hiding everything. It’s about sequencing. If users have to click ten times just to complete a basic request, you’ve created a new kind of friction. The right balance is simple:
- Essential steps first
- Optional detail later
- Clear headings and progress cues throughout
Part of the ServiceNow UX Guide
This blog is part of our ServiceNow UX Guide, written for leaders who want portals people choose, not portals people tolerate. Want all the practical tips in one place?
Quick answers for busy leaders
Q: What is progressive disclosure in ServiceNow?
A: It’s a UX method that shows essential info first and reveals extra detail only when needed, reducing overwhelm and improving completion.
Q: Where should we use progressive disclosure first?
A: Start with your highest-volume forms and topic pages. Those are the fastest wins for time to task and deflection.