Tidal Cyber · Interaction Design · Case Study

Global Navigation &
Panel Wayfinding.

Expanding panels in a dense analytical interface were causing the page to jump — losing spatial context for power users who relied on positional memory to work efficiently. I redesigned the panel expansion behavior to preserve anchor context, and proposed user-customizable panel ordering to give analysts control over their own workspace.

Company
Tidal Cyber
My role
Lead Designer · Sole designer
Scope
Navigation · Interaction · Spatial UX
Timeline
2025
Interaction prototype / annotated Global navigation — Panel expansion with preserved anchor context
The redesigned panel behavior. Expanding a panel no longer causes the page to re-anchor. Spatial position is preserved — the analyst stays where they were.
~25–35%
Fewer layout-related usability complaints
Efficiency for power users managing dense dashboards
Dev-ready designs implemented by engineering leads
The problem

The page was losing its place every time a user opened something.

Dense analytical interfaces depend on spatial memory. Power users — analysts moving through multiple panels in a session — build a mental map of where information lives. When expanding a panel caused the page to jump and re-anchor, that mental map broke. Users lost their place, had to reorient, and lost efficiency on every panel interaction.

This wasn't a catastrophic failure. It was a persistent low-level friction that compounded for heavy users — the exact people whose productivity the platform needed to protect.

Why wayfinding is a trust issue
Power users who rely on spatial memory to be efficient are implicitly trusting the interface to stay predictable. A layout that jumps unexpectedly breaks that trust — not dramatically, but in a way that accumulates.
How I approached it

Preserve position. Give users control.

The core problem was that panel expansion was treating the expanded panel as the new reference point and re-anchoring the page around it. The fix required changing the expansion behavior to preserve the user's current scroll position rather than jumping to the expanded element.

Interaction comparisonBefore — Panel expansion causes page to re-anchor, losing spatial position
User expands a panel. The page jumps to center on it. The analyst has lost their place and must reorient before continuing.
Interaction comparisonAfter — Panel expansion preserves scroll position and spatial context
User expands a panel. The page doesn't move. The analyst's spatial reference is maintained.

Beyond the anchor preservation fix, I proposed user-customizable panel ordering — giving analysts direct control over the layout of their workspace. This addressed the underlying cause of some of the jump behavior (panels appearing in an order that didn't match analyst workflow) and gave power users the agency to optimize for their own working patterns.

Interaction designUser-customizable panel ordering — drag to reorder interface
Drag-to-reorder panel interface. Analysts set the panel sequence that matches their workflow — reducing the navigational overhead of moving between panels that aren't in the order they work.
Key decisions
Treated anchor preservation as a correctness requirement, not a polish improvement
The page jumping on panel expansion wasn't an aesthetic problem — it was breaking a core interaction model that power users depended on. Framing it correctly made it easier to prioritize.
Proposed customizable panel ordering as a long-term power-user feature
The immediate fix was anchor preservation. The deeper fix was giving analysts control over panel order so the interface matched their workflow rather than requiring them to adapt. Dev leads requested implementation sync on both.
Prepared dev-ready designs before the PM request
Getting ahead of implementation by having dev-ready designs ready shortened the cycle from agreement on the fix to shipping it.
What I took from this
Spatial stability is a feature. For power users in dense analytical tools, the interface staying predictable is as important as any individual interaction being well-designed.
Low-level friction is worth fixing. Problems that don't generate dramatic complaints can still meaningfully degrade efficiency for the people who matter most to the product's value.
Dev-ready designs accelerate trust. Having implementation-ready artifacts before they're asked for signals design maturity to engineering and shortens the delivery cycle.