UX Writer

2024

Swing Education

Optimized onboarding

Copy

Design

Microcopy

Research

As the UX writer, I worked closely with a UX designer, engineers, and product managers on this project.

Screenshot of a divider page in an question flow.

Problem

Prospective subs struggled to understand complicated steps and their understanding of where they are the process.

Solution

A re-designed onboarding experience with simplified copy, visual cues, and clear status updates.

Impact

The modernized experience added clarity to the process for users, and allowed for quick iterations. It reduced the average time to onboard from 42 days to 30 days.

My process

1. Understand the problem

To understand the key problems with our previous onboarding experience, I talked to relevant stakeholders, analyzed data, and built a comprehensive understanding of the flow and requirements.Specifically, I idenfiied   key pain-points for the support and operations teams, analyzing key drop-off points and ticket content, and reviewing the full end-to-end experience.

We identified these key problems:

I took this information and collaborated with our designer to create our initial iteration.

Email communication

A screenshot of a bunch of sticky notes grouped by themes and sub themes.
Affinity map of analysis notes

2. User research

Gathering feedback was a key part of validating ideas and ensuring our solutions were solving the problems we were setting out to solve.

Usability testing

This project was a year long effort that involved multiple rounds of user testing at different points to validate ideas, and iterate on things that weren't working.

Card sort

A screenshot of a cluster map showing tasks sorted into 5 different groups.
Cluster map of task grouping

3. Iterate

This project involved a consistent iteration based on testing, and feedback from internal support teams.

Decisions

Communicating key info on cards

Throughout the design process, I removed as much content as possible, particularly from the overview cards. The goal was to prevent information overload while allowing users to gain key status information and set expectations right from the landing page.

Simplifying content and chunking information

Substitute teachers have to complete a series complicated, state specific, tasks to teach. I decided a key element of for a successful onboarding  would be to chunk information, only displaying the most relevant info at each point in their journey.

Naming tasks

I drew insights from the card sort, and observing user's language during testing to inform naming tasks. I opted for consist, friendly, and action-oriented language. I used the card sorting results to determine when to use more fun vs. serious language.

A tone scale for Application and About Swing showing that those titles fit with a more fun and creative tone.
A tone scale for background check, covid, and TB showing that those task fit with a more formal and serious tone.
Tone scale for naming tasks

Implementation and updates

Managing content in the code

A pillar of our implementation process was to set it up in a way that allows for as much product ownership as possible. I handled the front-end configuration files, and supported with attribute mapping.

Updating all off platform communication

I managed the design, content creation, and implementation for all of the onboarding notification including segments and triggers.

Highlights

Conversational tone

The previous onboarding experience was cold and a bit too formal. In the new onboarding experience, I brought in a more conversational tone by utilizing casual language and questions.

Phone mock showing an opening page for a task called "Tell us about yourself" with conversational language shown.
A phone mock with a question about a CA teaching credential shown using a conversational tone.

Communicating value

I used specific moments in the onboarding journey to clearly communciate what we do with the data provided, and remind subs of why they are going through this process.

A phone mock with a divider page shown communicating that sharing your teaching interests helps Swing make recommendations.
A phone mock with a divider page saying that there's a few questions left and that the final ones help you complete the following tasks smoothly.

Bringing clarity to complex tasks

I used simple language, chunked content, and FAQs to break down complex tasks into manageable tasks. For example, I utilized an accordion structure to share key resources related to tuberculosis testing. This allowed users to explore the answers if they wanted, but allowed other users to breeze through this steps if the content wasn't applicable. I also added opening content descriptions to address common questions up front.

A phone mock showing a description of Form I-9 and WorkBright.

Revamped notifcations

The revamped notifications have clear actions, and continuously drove users back to the platform, rather than relying on notification as the main source of information.

A map of 11 email campaigns.
Map of email campaigns
An email saying that the next step of onboarding tasks have been unlocked.
You've unlocked a new task email
An email saying that there's action required for a teaching credential.
Action required email

Check this out next

UX Writer and Designer

Ongoing

Swing Education

Engaging emails

Led end-to-end strategy and execution for 30+ product email campaigns, including platform migration and implementation.

Strategy

Design

Copy

Microcopy

A laptop with an email loaded called Swing Scorecard. Stats are shown: 86 classes covered, 12% feedback completed and 99 sub quality score.

© Katja Kleine