# Task Success Rate

Task success rate is the proportion of observed task attempts that meet a predefined, verifiable success criterion.

- Type: metric
- Domain: Data, experimentation & growth
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/task-success-rate/>)

## What it means

Task success rate, also called completion rate, measures effectiveness in a usability study or live journey. For binary scoring, the number of successful task attempts is divided by all valid attempts and expressed as a proportion or percentage.

## Why it matters

A product cannot be considered effective if intended users cannot achieve important goals. Success rate is easy to explain, supports benchmarking, and directs attention to outcome completion rather than clicks, opinions, or interface activity that may not represent success.

## When to use it

Use task success rate in moderated or unmoderated usability tests, benchmark studies, or instrumented product journeys when success can be defined objectively. Choose representative tasks and determine criteria before observing results to prevent post-hoc scoring.

## How it works

1. Define the target users, task scenario, start state, allowed assistance, and observable success criterion before data collection.
2. Classify each valid attempt using a documented rule; if partial success matters, report it separately or use a prespecified graded scheme.
3. For binary scoring, divide successful attempts by total valid attempts and convert to a percentage if desired.
4. Report the number of attempts, uncertainty, assistance, critical errors, and results by task rather than only one pooled average.
5. Use observation and follow-up questions to understand why failures occurred, then repeat comparable tasks after design changes.

## A practical example

In a usability test of a benefits portal, success means submitting a dependent addition with the correct effective date without moderator help. Seven of ten participants succeed, so binary task success is 70%. The team also reports two assisted completions and observes that date terminology caused most failures.

## Where it breaks

Binary success can hide near misses, unsafe workarounds, errors, assistance, and poor experience. Rates from small studies have wide uncertainty, while lab tasks may not represent real motivation or context. Product analytics require careful instrumentation to distinguish completion from mere event firing.

## Common mistakes

- Defining success after seeing participant behavior.
- Pooling very different tasks into one rate without task-level results.
- Reporting a percentage without the sample size, assistance rule, or confidence interval.

## Sources

1. [NISTIR 7432: Common Industry Specification for Usability](<https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=51179>) — National Institute of Standards and Technology · Government usability specification
2. [Success Rate: The Simplest Usability Metric](<https://www.nngroup.com/articles/success-rate-the-simplest-usability-metric/>) — Nielsen Norman Group · UX research guidance
3. [ISO 9241-11:2018 Usability: Definitions and concepts](<https://www.iso.org/standard/63500.html>) — International Organization for Standardization · International standard

## Related topics

- [Time on Task](<https://wiki.soroush.uk/topic/time-on-task/>)
- [System Usability Scale \(SUS\)](<https://wiki.soroush.uk/topic/system-usability-scale/>)
- [Usability Testing](<https://wiki.soroush.uk/topic/usability-testing/>)
