RD P
HomeProjectsAbout

Evolved Navigation

Simplified Information Architecture, providing pattern flexibility in support of new products

The objective of this project was to simplify the Information Architecture (IA) found across TraceLink's expanding SaaS Platform.  

Business requirements presented to me endorsed a major overhaul of our current content organization, labeling and navigation paradigm.  

In my role as Senior Manager UX, I needed to align our patterns to customers’ goals and tasks.   I took a holistic and evidence-based approach, to re-organize and re-label content, while keeping in mind TraceLink's strategic vision of the "Network."

The result was a redesigned Navigation that established a more scalable and sustainable model and responded directly to the needs of our 1,300+ global customers, engaging with 60+ unique applications.
‍

‍

Challenge

Tracelink’s platform is based upon a "Network Paradigm" (an approach similar to providing group access to a shared folder or cloud drive).

This model allows unlimited organization-to-organization collaboration. Internally, this concept was labeled "multi-enterprise," and conceptually is a powerful premise in the intricate realm of supply chain logistics.

Unfortunately, current TraceLink Navigation patterns did not articulate that value. Customer feedback had always highlighted confusion around how these relationships were organized and labeled.

Furthermore, this project had failed before.  Senior Executives were partial to current patterns and unwilling to approve platform-wide updates without rock solid evidence and jaw-dropping design. The bar was set high.  

Primarily, this was an exercise in stakeholder management and executive communication.

‍
‍

Current Navigation

Drop-down Menus: 
Pattern can only show one choice,   meaning poor visibility and scanning of available options. Added impact on small screens

Hierarchical relationships:
‍
Menus work together to construct a hierarchical pathway. But their flat horizontal alignment give a false impression of their relationship.

Left Panel Overload:
‍
Unnecessary marketing material overwhelms secondary controls by showing unrelated pathways.

Process
Step 1 - Problem Validation and Feedback

Heuristic Evaluation and Competitive Analysis - Found TraceLink navigation patterns to be atypical, impacting usability. Competitor products utilized more familiar patterns and organizational principles for added predictability and find-ability.

  • All others organized content using categories, with separate environments for Administration and Customization (along with public sites for Marketing and Help Documentation).

Qualitative User Research - Customer outreach and stakeholder interviews enabled the team to better understand our problem space and articulate a "customer-first" perspective to stakeholders.

  • Able to identify and classify a wide Persona Spectrum and note the specific high-level goals of each group.
  • These findings informed KPI's and our post-release measurement features.
  • The TraceLink platform enables customers to create and customize applications. All customers consulted wanted similar controls related to navigation, including branding options.

Tree Testing - Other team members led moderated sessions that exposed widespread labeling gaps and categorization shortcomings, which allowed me to share with stakeholders via quantitative measures.

  • Test script based upon key personas (e.g., Supply Chain Managers, Compliance Officers, Quality Control Specialists) usage patterns.
  • Highlighting our most problematic use cases involved non-network scenarios (finding unlinked, customer only apps).


Collectively these core UX findings were assembled into a series of presentations and delivered to executive-level stakeholders for alignment and approval.  

Step 2 - Definition and Alignment

The problem space was well understood and our working team all shared a new customer-centric perspective.

Next, I produced a series of strategic deliverables so everyone could collectively envision our enhanced future state.

It was time to converge upon key principles…

Structure and categorization
Simplify our structure and use logical categories to organize features based upon customer needs and frequency of use.

Navigation Patterns
Implement consistent navigation, (while allowing for customer configuration) and employ progressive disclosure to reduce cognitive load and improve efficiency. 

Responsive Needs
Ensure scalable and consistent patterns across all devices, unlocking app development for tablets, and smartphones (supporting warehouse and facility management use cases).

Land, then Expand
Establish clear visual separation between global, platform-level navigation and local, specific controls that should appear in context.

Step 3 - Design and Test

I began by iterating and continuously presenting set-based design concepts to internal stakeholders review and approval‍.

Once concepts were approved inside TraceLink, we validated with real users (recruited from our persona groups) to ensure the new patterns meet or exceed expectations.
‍

I found 2 patterns to be the most effective…

Clear Design intent

Styling aspects on-sbrand

Responsive

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Accesible

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Internationalized / Localized

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Components

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Voice and tone

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Pattern 1

Horizontal Tabs

A common UI pattern that fuels categorization at the top of the page. Also affords flexibility and nuance within the second level of navigation. Power users can seamlessly switch between contexts efficiently.

  • Optimal for advanced users on larger screens (desktop)
  • Best supports data-rich layouts and tables
  • Improves efficiency for complex, multi-step tasks 
Pattern 2

Drawer Navigation

Revealed through user interaction (e.g. progressive disclosure) this pattern also supports categorization, but uses screen real estate more effectively, providing space contextual and focused actions.

  • Common pattern for smaller screens (mobile and tablet)
  • Navigation controls can easily draw back, allowing users to focus on one task at a time
  • Best supports repetitive, focused work (ex: warehouse, facilities, etc)
Outcomes
Another round of usability testing (with all persona groups), showed both patterns significantly improved upon task completion, success rates and reduced errors.

The biggest win was utilizing categories universally to disclose the different levels of information.  This organization promotes efficiency movement and aids in understanding, while still keeping the network context front- and-center.
‍
Tabs














‍

Side Nav














‍

Next Steps
Moving forward, our challenge is to learn more.

Design, test and repeat.

More immediately, I'm transitioning all tested patterns into configurable UI components. Working closely with Dev Teams and Product Management partners to plan releases and understand dependencies.

In addition, I'm preparing work for my design team to expose these navigation options inside our no-code platform. This will enable customers to choose and customize Navigational patterns that best suit their unique needs.

Scaling these patterns to enable and empower future development.
‍
‍

Contact me

I'm always interested in exploring new opportunities.
Please reach out. I'd love to chat.

(c) Copyright Ryan Patriquin