User Onboarding Friction Audit

Template Overview

The first five minutes of user interaction dictate long-term retention. Unclear permissions, complex model setup, or confusing file storage options introduce friction that drives users away. The User Onboarding Friction Audit maps the end-to-end first-run experience, quantifies cognitive load, and highlights friction moments in plain Markdown.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Onboarding Friction Audit: [Version / Cohort]"
date: [YYYY-MM-DD]
auditor: "[[Lead UX Auditor]]"
application_version: "v1.3.4"
first_time_to_value: "3m 15s"
friction_severity_score: "Low / Medium / High"
tags: [ux-research, onboarding, friction-audit, product-design]
---

# User Onboarding Friction Audit — [Version / Cohort]

## 1. Audit Scope & Target Milestone
- **Core User Milestone:** First successful recording, on-device transcription, and template export.
- **Audited Cohort:** First-time Mac users running macOS Sequoia on Apple Silicon.

## 2. First-Run Step-by-Step Experience Log
| Step | Screen / Interaction | Cognitive Burden | Friction Description | Friction Level |
|---|---|---|---|---|
| **01** | App launch & welcome window | Minimal | Clean minimalist welcome screen | None |
| **02** | Microphone permission prompt | Low | Clear explanation of macOS security prompt | Low |
| **03** | Local Whisper model selection | Medium | User presented with 3 model sizes without clear hardware context | **Medium** |
| **04** | Local vault destination picker | High | Modal requires folder selection; defaults could be provided | **High** |
| **05** | First recording activation | Minimal | Large intuitive record button with keyboard shortcut hint | None |
| **06** | Transcript generation & preview | Minimal | Progress bar with immediate real-time feedback | None |

## 3. Detailed Friction Analysis
### Friction Point A: Vault Folder Selection (Step 04)
- **Problem:** Requiring new users to manually pick or create a folder on disk introduces hesitation. 40% of tested users paused to decide where notes should live.
- **Impact:** Delays first-time-to-value by an average of 45 seconds.
- **Solution:** Provide a sensible default (e.g., `~/Documents/Vault`) with an immediate 'Change Later' link.

### Friction Point B: Whisper Model Context (Step 03)
- **Problem:** Technical terms like 'FP16 quant' confuse non-technical users.
- **Solution:** Replace jargon with intuitive labels: 'Fast (Compact)', 'Balanced (Recommended)', and 'High Accuracy (Studio)'.

## 4. Friction Remediation Punch List
> [!TIP] Quick Win
> Pre-selecting a default vault folder and labeling the balanced model as 'Recommended' reduces first-run setup steps from 6 to 3.

## 5. Action Items
- [ ] Implement smart default vault directory creation on initial launch.
- [ ] Simplify model selection copy in onboarding wizard.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Onboarding Audit: Desktop Client v1.4"
date: 2026-10-07
auditor: "[[Priya Patel]]"
application_version: "v1.4.0-beta"
first_time_to_value: "1m 45s"
friction_severity_score: "Low"
tags: [ux-research, onboarding, friction]
---

# User Onboarding Friction Audit — Desktop Client v1.4

## 1. Audit Executive Summary
Priya Patel audited the refreshed v1.4 onboarding flow. Thanks to automatic default vault generation, first-time-to-value dropped from 3m 15s down to 1m 45s.

## 2. Key Observations
Microphone permission explanation resulted in 100% acceptance on first prompt. New users completed their first test dictation effortlessly within 2 minutes of app installation.

When to Use and When to Avoid

When to Use

• Use prior to major marketing launches to optimize conversion from install to active user.
• Use after redesigning sign-up, setup wizards, or initial permission request flows.
• Use to measure quantitative improvements in first-time-to-value across releases.

When to Avoid

• Avoid using to evaluate power-user advanced workflows like regex search or API scripting.
• Avoid using for post-onboarding retention and renewal analytics.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the onboarding session observations:
1. Identify all interaction steps where user hesitation or cognitive burden was documented.
2. Calculate total first-time-to-value duration and pinpoint the top friction causes.
3. Formulate concrete onboarding simplification proposals in structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.