Travel Management System

Travel Management System

Unified two disconnected systems into a single modern application.

summary

One of our internal product suite's is modernizing its tech stack as crucial systems and processes become outdated and fragmented

Travel and export compliance had become bloated over time. The goal was to use human-centered design to simplify how people request, manage, and report travel, and to shrink our digital footprint along the way.

  • Client: Software Engineering Institute

  • Role: Lead Researcher and Designer

  • Length: 1.2 years

  • Location: Pittsburgh, PA

  • Tools: Figma, Mural, Lyssna

  • Team: 1 product manager, 2 backend developers, 3 frontend developers

A snapshot of the redesigned travel dashboard

A snapshot of the redesigned travel dashboard

problem

One of our internal product suite's is modernizing its tech stack as crucial systems and processes become outdated and fragmented

Travel and export compliance had become bloated over time. The goal was to use human-centered design to simplify how people request, manage, and report travel, and to shrink our digital footprint along the way.

  • A 20+ year old system held together by retroactive patches, comprised of 2 applications, 4+ bloated forms, and 10+ apps/tools

  • Tasked with consolidating and retiring old apps, while building on the design system

A snapshot of the old travel system form

A snapshot of the old travel system form

Discovery

To fix the system, we first had to see how people actually used it

Uncovered user friction and baseline system performance through direct observations and contextual inquiry.

  • 8 contextual inquiries with developers shadowing as silent observers, producing 98 findings

  • Evaluated international and domestic workflows across creation, submission, and review phases

  • Adapted IBM’s PSSUQ survey to benchmark baseline usability metrics

A snapshot of the old travel system form

A (blurred) snapshot of our final affinity map session

define

I led the team in turning scattered findings into a shared understanding of the problem

Led prioritization and synthesis sessions to establish shared alignment across the cross-functional team.

  • Synthesized 21 raw interaction patterns into 5 core themes

  • Built a user-validated journey map identifying friction points and intervention opportunities

  • Drafted a current-state service blueprint to align stakeholders on system dependencies

Our complex user flow (top), and high-level journey map (bottom)

Our complex user flow (top), and high-level journey map (bottom)

turning Themes into insights

Reframed 5 observational themes into actionable design principles to guide our solution

Reframed 5 observational themes into actionable design principles to guide our solution

  1. User's build custom forms: The less details received at the beginning of the process, the more time and effort is required. Provide a consistent way for arrangers to receive details.

  2. Estimating costs can be challenging: Providing accurate estimates creates confusion, slows the process, and provide no value. Forms should be used to approve trip purpose, not estimated costs.

  3. Arrangers enter fake data into forms: Entering fake data wastes time and runs risk of submitting wrong data. Form must be easily saved and not require overly specific details.

  4. Manual facilitation for last minute trips: The more time spent on the approval process, the more likely plans will change. Remove unnecessary stakeholders from approvals and avoid chronological approaches.

  5. Booking travel can be time-consuming: The more variables exist, or the more complex the system/processes are, the longer it takes. Simplify pre-trip approval process to reduce turnover.

Form audits

We knew the current forms weren’t working, so I set out to see why, and were, they were breaking down

We knew the current forms weren’t working, so I set out to see why, and were, they were breaking down

I led 14 stakeholders (financial analysts, arrangers, travelers, security specialists, and more) through two one-hour sessions, reviewing every field across both forms.

  • 267 form fields and elements down to 65 (76% reduction)

  • Uncovered opportunities to improve helper text, pre-fill fields to reduce manual entry, auto-generate service desk tickets, and better align with security practices

A snapshot of decisions being made in real time during an audit of the old form

A snapshot of decisions being made in real time during an audit of the old form

ideation

Co-creation helped us land on ideas that were useful, viable, and technically feasible

Co-creation helped us land on ideas that were useful, viable, and technically feasible

I led a session with stakeholders, users, and teammates to generate as many solutions as possible, then rapidly prototyped the strongest to expose weaknesses early.

  • Creative matrix: Built around the 5 themes, generating 57 ideas

  • Round robin: Participants built on each other’s ideas

  • Speed dating: 57 ideas became 7 concepts tested with real users, leaving 4 validated solutions

3 of 4 co-created solutions ideated during a round robin (left) turned into low fidelity mockups for speed dating (right)

3 of 4 co-created solutions ideated during a round robin (left) turned into low fidelity mockups for speed dating (right)

co-creating the dashboard

Because I’m not an everyday user, I let users design their ideal dashboard themselves

Because I’m not an everyday user, I let users design their ideal dashboard themselves

I ran a co-creation session with 7 users of varying experience to learn which actions and widgets they expected to see. 

  • Radar: Users identified and ranked desired features (avg. 13 per user)

  • Co-creation: Users sketched their ideal dashboard on a blank mockup

  • Prioritization matrix: The team ranked features by implementation difficulty, producing a roadmap balanced by feasibility and impact

User generated priorities (top), user designed dashboards (bottom)

User generated priorities (top), user designed dashboards (bottom)

redesigning the forms

This redesign would have been in vain without effort on the forms

This redesign would have been in vain without effort on the forms

With 76% of the form removed, I redesigned the core experience using, and extending, the design system’s form components.

  • Desk research: Best practices from sources like NN/g

  • Comparative analysis: Learnt what modern forms are expected to do

  • Validation testing: Usability test of static mockups scored 4.4 / 5, a 37.5% increase over baselines they expected to see. 

Solution

Working in parallel with developers, we released a single system that gives every stakeholder the tools to manage travel.

A snapshot of the redesigned dashboard (v1)

A snapshot of the redesigned dashboard (v1)

An actionable dashboard that puts the most important information first

An actionable dashboard that puts the most important information first

We shipped v1 with role-specific data tables built from co-creation findings. A customizable dashboard with 6 initial widgets is in development.

A snapshot of the redesigned travel form

A snapshot of the redesigned travel form

Two forms became one, with autofill and built-in comments

Two forms became one, with autofill and built-in comments

Additional features, e.g., comments and documentation uploads, were built as reusable “mini apps” that other applications can share.

A snapshot of 1 of 4 redesigned administrative tools

A snapshot of 1 of 4 redesigned administrative tools

Four separate apps became one admin experience

Four separate apps became one admin experience

Redesigned and integrated four administrative tools without breaking existing mental models.

A snapshot of the redesigned search experience

A snapshot of the redesigned search experience

Complex search that never loses your place

Leveraged the newly designed panels to keep users on their current page while they build queries.

A snapshot of the nested export compliance application

A snapshot of the nested export compliance application

Unifying export compliance processes

As part of the integration, I redesigned and linked an export compliance application to keep users within the same ecosystem.

Org-wide priorities shifted our attention from post-release usability testing, but the application is live (v3) and has been met with praise from both stakeholders and users alike.

design system contributions

Rather than building from scratch, I found opportunities to leverage and enhance our in-house design system

Rather than building from scratch, I found opportunities to leverage and enhance our in-house design system

  • Designed a Data Table* built to handle dense data with inline sorting, filtering, pagination, and nested rows

  • Introduced a Combobox* input with integrated category filtering and multi-selection

  • Designed a compact Action Button* designed for secondary workflows

  • Introduced a stylized Callout* to share contextual messages

  • Redesigned Layout Application template to modernize our apps

  • Modernized Tabs to support underline, block, and folder styling

  • Redesigned File Uploader to introduce expected functionality (e.g., enhanced previews, contextual messaging, etc.)

  • Introduced an Avatar Stack* while modernizing our Avatars (e.g., size, border radius, color, etc.)

* Component or pattern newly introduced as part of this effort

A collection of redesigned and newly created components and patterns

A collection of redesigned and newly created components and patterns

Learnings and takeways

Finding the sweetspot of design by balancing what users need, what’s technically feasible, and what the organization wants

Finding the sweetspot of design by balancing what users need, what’s technically feasible, and what the organization wants

  • Involve devs early and often to create alignment

  • Strong stakeholder relationships opens up the door for honest communciation a difference

  • Continue to guard against scope creep with prioritization and

  • Find the right rabbit holes to push for improvements

© 2026, Marlon Zoir Mejia

© 2026, Marlon Zoir Mejia

© 2026, Marlon Zoir Mejia