Shift Alarm · UX Strategy + Activation

Finding why users struggled to reach value during onboarding.

Shift Alarm helps shift workers manage rotating schedules and alarms. I was brought in to audit the onboarding experience, identify where users were getting stuck, and recommend opportunities to improve activation.

By combining behavioral analytics, funnel analysis, session recordings, product walkthroughs, and messaging analysis, I found that the central problem wasn’t simply onboarding length:

Users were being asked to learn Shift Alarm’s scheduling system before experiencing the outcome they came for.

Role
UX Research · Product Strategy
Scope
Onboarding Audit · Behavioral Analysis · Funnel Analysis · Session Analysis · UX Strategy · Messaging

Behavioral research

Start with what users actually do.

I combined quantitative and qualitative behavioral evidence to understand where onboarding friction occurred and why.

65+

Session recordings analyzed

Funnel analysis

Identified major onboarding drop-off points

Event analysis

Examined behaviors including resets, replays, undo actions, and backtracking

Product walkthrough

Evaluated the onboarding, subscription, and messaging experience end-to-end

Reframing the problem

Users didn’t come to build a rotation. They came to make sure they wouldn’t miss work.

The onboarding experience was organized around the mechanics of Shift Alarm’s scheduling engine. But the user’s underlying job was much simpler:

“Help me reliably manage my schedule so I don’t miss work.”

Product model

Learn rotationsPaint schedulesPreview patternsLock patternConfigure alarms

User goal

Tell Shift Alarm when I workMake sure my alarm is ready

Five steps of system learning, set against a two-step goal.

The core finding

The onboarding taught the system before delivering the value.

The largest onboarding friction appeared during schedule setup. But the behavioral evidence suggested users weren’t simply disengaged.

Many were actively trying to succeed.

  • Tutorial replays
  • Practice resets
  • Undo actions
  • Backtracking
  • Abandonment during schedule configuration

These behaviors suggested effort without confidence: users were trying to complete setup, but weren’t always sure they were doing it correctly.

01 · Value before complexity

Reorganize onboarding around the outcome, not the scheduling engine.

The existing onboarding required users to understand shift types, rotations, pattern creation, off days, previews, and calendar behavior before reaching the alarm experience.

Onboarding analysis · Behavior + Activation

Current

Select shiftsLearn rotationsPaint schedulesReview patternsLearn premium featuresTrial

Proposed

Define shiftsConfigure alarmsApply shiftsPreview protected shiftsTrial

02 · Mental models

Users were learning Shift Alarm’s vocabulary while trying to learn the product.

Terminology such as Paint, Rotation, Practice, Preview, and Lock Pattern reflected the system’s internal model more than the user’s real-world task.

Product languageUser goal
Paint a rotationAdd my work schedule
Lock patternConfirm my schedule
Start practicingCreate my schedule

Users should learn by doing, not by studying the system.

Mental model analysis · Terminology + Cognitive load

03 · Conversion

The trial asked users to make a decision before the consequences were clear.

The trial experience presented pricing, features, subscription language, and multiple actions while leaving important questions ambiguous:

  • What happens if I skip?
  • When does billing begin?
  • What functionality remains available?
  • What exactly happens when I start the trial?

Recommended simplification

Start my 30-day free trial

$4.99/month after trial

Continue with limited features

An audit recommendation, shown as a concept.

Conversion analysis · Trial + Subscription

Positioning

One clear reason to care before explaining everything the product can do.

Existing messaging communicated scheduling, alarms, pay forecasting, bills planning, overtime tracking, exports, widgets, and security simultaneously. The audit recommended a progressive messaging hierarchy:

  1. 01

    Never miss a shift

    Wake up with confidence, even when your schedule changes.

  2. 02

    Built for rotating schedules

    An alarm experience designed specifically for shift workers.

  3. 03

    Plan around your shifts

    Forecast pay and upcoming expenses once the core need is solved.

Positioning analysis · Value proposition

From findings to strategy

Move the value moment earlier.

Before

  1. Learn the system
  2. Configure the system
  3. Understand premium features
  4. Make a subscription decision
  5. Experience value

Recommended

  1. Define my shifts
  2. Protect my next shift
  3. Experience value
  4. Discover advanced capabilities
  5. Make an informed subscription decision

The recommendation wasn’t simply to shorten onboarding. It was to change the order in which users experienced complexity, value, and monetization.

Roadmap

Separate quick wins from structural changes.

Phase 1 · Reduce friction

  • Clarify trial expectations
  • Simplify terminology
  • Reduce information density
  • Reduce competing controls and instructions

Phase 2 · Improve activation

  • Reorient onboarding around user outcomes
  • Move alarm configuration earlier
  • Re-evaluate trial timing
  • Explore value-before-monetization models

Deliverable

Turning behavioral evidence into an activation strategy.

The audit translated onboarding analytics and observed user behavior into a prioritized set of product recommendations spanning interaction design, onboarding architecture, monetization, and messaging.

Rather than treating individual usability issues in isolation, the recommendations addressed the larger relationship between user motivation, product complexity, value realization, and conversion.

Closing insight

When users keep retrying, resetting, and going backward, the problem isn’t necessarily motivation. Sometimes the product is making them work too hard to understand how to succeed.