Spencer Stuart – Quest Mobile (Always-On Executive Search)

Native Mobile
Written By B K

Role
Senior UX Designer

Domain
Native Mobile · Enterprise Tools · Global Search

Skills
Native Mobile UX · Workflow Design · Offline-First Design · Cross-Platform Patterns · Information Architecture · Stakeholder Collaboration

Overview

Quest Mobile was Spencer Stuart’s first always-on native mobile application, designed to support executive search consultants working across regions, time zones, and travel schedules.

The goal was to provide fast, reliable access to candidate and search data in situations where desktop access wasn’t practical — including meetings, travel, and low-connectivity environments — while maintaining the confidentiality and rigor required in executive search.

The Problem

Prior to Quest Mobile:

  • Consultants relied primarily on desktop tools

  • Mobile access was inconsistent and limited

  • Key information wasn’t easily accessible on the go

  • Offline access was minimal or nonexistent

  • Internal tools were not designed with mobile workflows in mind

Consultants needed a purpose-built mobile experience — not a responsive afterthought.

My Role

I served as the UX/UI designer on Quest Mobile, collaborating closely with Product, Engineering, and internal stakeholders. My responsibilities included:

  • Designing the end-to-end mobile experience for iOS and Android

  • Translating complex executive search workflows into mobile-appropriate patterns

  • Applying iOS and Material Design conventions appropriately per platform

  • Designing for offline and low-connectivity use cases

  • Establishing navigation and information hierarchy for small screens

  • Ensuring usability for a global, frequently traveling user base

This work required careful balance between depth of information and speed of access.

Research & Insights

Key insights emerged from stakeholder interviews and usage scenarios:

  • Consultants often needed to reference information quickly during meetings

  • Connectivity could not be assumed, especially while traveling

  • Mobile usage focused on lookup and review, not heavy data entry

  • Trust and confidentiality were paramount

  • Users wanted consistency with desktop terminology, but not desktop complexity

These insights shaped a focused, task-oriented mobile experience.

Design Approach

1. Native-First, Not Desktop-Shrunk

Rather than shrinking the desktop experience, the design focused on:

  • Core mobile use cases

  • Reduced feature scope with high relevance

  • Clear prioritization of key information

  • Touch-friendly interactions

This resulted in a product that felt intentionally mobile.

2. Offline-Aware Design

Quest Mobile was designed to remain useful without a constant connection:

  • Cached recent searches and records

  • Clear indicators for sync status

  • Graceful handling of offline states

  • Predictable behavior when reconnecting

This was critical for real-world consultant workflows.

3. Cross-Platform Consistency with Platform Respect

The app supported both iOS and Android, requiring:

  • Shared interaction principles

  • Platform-appropriate navigation patterns

  • Respect for native gestures and UI conventions

Users felt immediately comfortable regardless of device.

4. Clear Information Hierarchy

On small screens, clarity mattered more than completeness:

  • Key details surfaced first

  • Secondary information progressively disclosed

  • Consistent labeling and structure

  • Minimal visual noise

This supported quick scanning and confident use.

Key Design Decisions

  • Prioritized read-only and lookup workflows over editing

  • Designed navigation for speed and muscle memory

  • Treated offline support as a core requirement, not an edge case

  • Avoided over-feature-ing the app

  • Maintained consistency with Spencer Stuart’s internal systems while simplifying the experience

Solution

Quest Mobile App

  • Native iOS and Android applications

  • Fast access to searches, candidates, and records

  • Offline-capable browsing of recent data

  • Clean, focused UI optimized for consultants on the move

User Experience Outcomes

  • Reduced friction when accessing critical information

  • Increased confidence using mobile tools in client settings

  • Improved adoption of mobile access across the firm

Impact & Results

  • Delivered Spencer Stuart’s first production native mobile app

  • Enabled consultants to work more effectively while traveling

  • Established a foundation for future mobile initiatives

  • Demonstrated that internal tools could be both powerful and usable

While narrower in scope than later enterprise work, this project demonstrates strong mobile fundamentals and judgment.

What I Learned

  • Mobile UX demands ruthless prioritization

  • Offline support changes how users trust a product

  • Native patterns matter, especially for professional users

  • Internal tools benefit greatly from mobile-specific thinking

  • Consistency builds confidence across platforms

Artifacts (Optional)

  • iOS and Android screen flows

  • Navigation structure diagrams

  • Offline state explorations

  • Cross-platform pattern comparisons

B K
Previous

Northwestern Medicine – Patient Self-Scheduling Platform
Next

Party Central Landing Page & Platform Improvements