Wide tables lose context too fast.
As users move across dense list views, important columns can disappear off-screen, making comparison slower and decision-making less confident.
Project / 05
A focused ServiceNow exploration on how pinned columns can feel clearer, more predictable, and more useful inside dense list workflows.

I partnered with Michael to explore how column pinning could work more clearly inside ServiceNow list views, where data density and horizontal scrolling make orientation especially important.
The project looked beyond the pinned state itself and focused on the surrounding signals that make the interaction understandable: dividers, shadows on scroll, icon placement, and the balance between discoverability and visual noise.
Discuss this project ↗Context
Column pinning looks simple on the surface, but inside dense enterprise tables it quickly becomes a question of discoverability, visual noise, and how users keep context while scrolling.
As users move across dense list views, important columns can disappear off-screen, making comparison slower and decision-making less confident.
I explored when to show dividers, how shadows should animate on scroll, and where the pin icon should appear so the pattern feels discoverable without becoming visually heavy.
The explorations helped compare a more explicit “easy pin” approach against a quieter “no icon” direction, making the design tradeoffs much easier to discuss and evaluate.




Directions
Instead of deciding too early, I treated the sprint as a side-by-side evaluation of two different interaction philosophies, then used the mockups to clarify what each one gained and lost.
This direction leaned into stronger affordances so users could immediately understand what was pinned and how the table would behave while navigating across the list.
This alternative tested whether the interface could communicate pinned behavior more elegantly through layout, motion, and dividers rather than additional iconography.
This sprint taught me how much clarity in enterprise UX depends on restraint, especially when designing within existing system patterns and implementation constraints.




Outcome
Even without building the full production feature, the sprint created a clearer language for how pinned behavior should look, when it should announce itself, and how subtle motion can support orientation.
Dividers, shadows, and icon behavior ended up being more important than the pinned state alone because they determined whether the pattern felt predictable.
The sprint made it easier to compare a louder but more teachable pattern against a quieter solution that relied on stronger visual discipline.
This project reminded me that seemingly minor interaction surfaces can meaningfully affect speed, orientation, and trust when users work inside dense data-heavy environments.