Navigation booking tool - Code the Change YYC x Salvation Army

Designing a scheduling & booking tool to coordinate transportation for those who need it most

UX Design, UX research, cross-functional collaboration, shipped

fall 2025

Navigation booking tool - Code the Change YYC x Salvation Army

Designing a scheduling & booking tool to coordinate transportation for those who need it most

UX Design, UX research, cross-functional collaboration, shipped

fall 2025

Navigation booking tool - Code the Change YYC x Salvation Army

Designing a scheduling & booking tool to coordinate transportation for those who need it most

UX Design, UX research, cross-functional collaboration, shipped

fall 2025

Timeline

2 months, Fall 2025

Role

Lead product & UX Designer

team

Engineering Tech Leads & Salvation Army Admin Staff

skills

UX Research, User Testing, Cross functional collaboration, Design Systems

overview

Creating tools to study the interaction between humans and AI

overview

Creating tools to study the interaction between humans and AI

The Salvation Army’s Navigation Centre (SANC) offers free transport to the most vulnerable populations in Calgary. Our booking tool allows Admin staff to spend less time managing the overhead of bookings and more time focusing on other critical tasks.


As the lead product & UX Designer working with student developers at Code the Change, I conducted various user interviews, created prototypes, worked cross-functionally with engineering teams and stakeholders to iteratively create a tailored booking management app for the Salvation Army.

Impact: how we improved the process

3x less

Booking overhead time

2x less

Dropped bookings

2x less

Time swapping apps

context

The Salvation Army’s Navigation Centre offers free transport to those who need it most

context

The Salvation Army’s Navigation Centre offers free transport to those who need it most

The Salvation Army offers free transport to Calgary’s most vulnerable populations via the Navigation Centre, helping them receive reliable transport to important appointments like job interviews or medical appointments. This offering is actively changing lives in our city in a time where public transport can be unreliable.

user problem

Admin staff are spending too much time managing appointments

user problem

Admin staff are spending too much time managing appointments

The Salvation Army intended their administrative staff to be “background actors” and not spend too much time managing appointments for this system. The existing concept is simple: agencies would work with clients to book appointments with the Salvation Army Admin staff, and the Admin staff would schedule the appointment for pickup and the driver would do the rest on the appointed date

FIG. 1

A visualization of the current booking process

FIG. 1

A visualization of the current booking process

In reality, they were spending a lot of time filling out information manually across different forms and spreadsheets, which was a time consuming process prone to mistakes and causing great frustration.

FIG. 2

The complicated reality of the current manual system.

FIG. 2

The complicated reality of the current manual system.

design process

How did we arrive at our solution?

design process

How did we arrive at our solution?

Discover

Learning about the current booking process

I interviewed Salvation Army Admin staff and observed parts of their current workflow to learn more about their current booking process, workflow, and concerns to develop a strong foundation for future design work.

Key insights & highlights:

Key insights & highlights:

Client privacy is a serious concern

This has prompted admin staff to opt for a manual system with themselves as the coordinators.

Client privacy is a serious concern

This has prompted admin staff to opt for a manual system with themselves as the coordinators.

Too many forms are being used

Over 7 manually filled forms and schedules were used to manage bookings, but were often redundant

Too many forms are being used

Over 7 manually filled forms and schedules were used to manage bookings, but were often redundant

Constant back and forth

Agencies were unable to directly view available timeslots to request bookings.

Constant back and forth

Agencies were unable to directly view available timeslots to request bookings.

Overall frustration

Admin staff were growing increasingly frustrated using the manual booking system.

Overall frustration

Admin staff were growing increasingly frustrated using the manual booking system.

Overall frustration

Admin staff were growing increasingly frustrated using the manual booking system.

Define

Problem Definition & User Groups

The Design Challenge:

The Design Challenge:

How might we develop a streamlined process to manage transport requests with minimal administrative intervention, while preserving client privacy?

How might we develop a streamlined process to manage transport requests with minimal administrative intervention, while preserving client privacy?

User groups definition

To design with users in mind, I identified key user groups that needed to be involved in the process, and focused on those who would use the system:

Agencies

Conversations with a defined goal

  • Work directly with clients to send bookings to administrative staff

  • Main point of contact to client

Trip planning with friends and business meetings both aim to accomplish certain tasks.

Drivers

Conversations with a defined goal

  • View all drop-off appointments for the day

  • Log all trip information & distance travelled

Trip planning with friends and business meetings both aim to accomplish certain tasks.

Admin Staff

Conversations with a defined goal

  • Manage all booking information

  • Manage logistics

Trip planning with friends and business meetings both aim to accomplish certain tasks.

Key tasks for all users

To design with users in mind, I identified key user groups that needed to be involved in the process, and focused on those who would use the system:

FIG. 3

A set of tasks each user group should be able to perform

FIG. 3

A set of tasks each user group should be able to perform

develop

Problem Definition & User Groups

User flows

Based on the tasks each user group would need to complete and their goals, I created user flow diagrams to help organize my ideas first.

FIG. 4

Admin user flow diagram sample

FIG. 4

Admin user flow diagram sample

Low-Fidelity prototyping

To better communicate my visions to my team and stakeholders, I created low-fidelity prototype sketches and used them as opportunities to ask more questions and iterate based on feedback.

FIG. 5

Sample low fidelity screens created in early stages

FIG. 5

Sample low fidelity screens created in early stages

Medium-High Fidelity Prototyping

After working with admin staff and our tech team with my sketches, I worked on medium-high fidelity prototypes alongside a design system to allow the team to better visualize and experiment with different interactions on the prototype. After creating these prototypes, I conducted several rounds of user testing to validate my assumptions and further iterate on the prototypes.

FIG. 5

Sample high fidelity screens created before user testing

FIG. 5

Sample high fidelity screens created before user testing

deliver - solution

Final design highlights and features

Video prototypes on the way!

Video prototypes on the way!

I'm currently working on video prototypes to showcase here. In the meantime, I've placed images of the UI. Feel free to contact me for more details.

I'm currently working on video prototypes to showcase here. In the meantime, I've placed images of the UI. Feel free to contact me for more details.

Three different workspaces for each user group

To ensure each user group only had access to only the necessary information and preserve client privacy, I created 3 distinct views.

To ensure each user group only had access to only the necessary information and preserve client privacy, I created 3 distinct views.

Cutting out the middleman

By allowing agencies to directly view available time slots, they can make bookings without any bottlenecks

How do we prevent cognitive overloading, and only provide value when needed?

Supporting drivers and convenience

Offering a mobile-focused view and daily schedule suits their daily needs, with navigation redirects allowing for reduced tab swapping. In-app surveys also reduces the number of paper forms used.

How do we prevent cognitive overloading, and only provide value when needed?

Powerful, unified management tools

Admin staff have access to a live-updating database of bookings, now all in one place, so they can focus on more critical tasks outside of this service.

How do we prevent cognitive overloading, and only provide value when needed?

conclusion

Final reflections

Challenges

I had a lot of fun learning to navigate the unique challenges that followed converting a manual process to a digital one alongside real clients, while working cross-functionally with our tech team. In particular, I had to figure out how to:

  1. Fully understand and empathize with users to develop a deep understanding of the problem and streamline the booking process.

  2. Navigate user testing coverage, as some user groups were unavailable for testing.

  3. Design and organize my files for smooth developer hand-off.

Learnings

  1. Draw things out, think things out yourself, but don't be afraid to ask clarifying questions! This helps move things out faster and creates mutual understanding.

  2. Think about the future: systems and user needs adapt, so designs should accommodate these changes to the best extent possible.

  3. A picture is worth a thousand words, but an interaction is worth even more: visual and interactive communication is key to success!