doherty-threshold

Diagnose interface latency against the 400ms Doherty Threshold and design feedback patterns for slower responses.

2.5k|358|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill doherty-threshold
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doherty-threshold
Source: https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/doherty-threshold
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill doherty-threshold

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interfaces that respond too slowly break user flow and make products feel sluggish, but teams often lack a concrete latency target or a plan for what to show when fast responses are impossible. This Skill applies the Doherty Threshold to pinpoint where response times degrade the user experience and prescribes the right feedback pattern for each latency band.

Core Features & Use Cases

  • Latency Diagnosis: Maps response times to user perception bands (instant, fast, slow, broken) to identify which interactions violate the sub-400ms target.
  • Feedback Pattern Selection: Prescribes immediate visual acknowledgment, loading indicators, progress bars, optimistic UI, or skeleton screens based on how long an operation actually takes.
  • Performance Budgeting: Helps set latency budgets for high-frequency interactions like transitions, autocomplete, search, and button feedback.
  • Use Case: When reviewing a search feature that takes 800ms to return results, use this Skill to determine that a skeleton screen should appear immediately while results load, rather than leaving the interface unresponsive.

Quick Start

Ask the AI to audit your interface's key interactions against the Doherty Threshold and recommend feedback patterns for any response that exceeds 400ms.

Frequently Asked Questions about doherty-threshold

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Doherty Threshold in UX design?

The Doherty Threshold states that system responses under 400ms keep users in flow and increase productivity, based on 1982 IBM research by Doherty and Thadani. Above 400ms, users notice the wait and their cognitive engagement with the task degrades.

How do I design loading states for slow responses?

Acknowledge the action within 100ms with a visual state change, show a loading indicator for waits of 400ms to 3 seconds, and show determinate progress for anything longer. For content with a known layout, prefer skeleton screens over spinners.

When should I use skeleton screens instead of spinners?

Use skeleton screens when the loading content has a known layout, because they preserve spatial context and feel faster than spinners. Spinners are appropriate only for short, indeterminate waits between 400ms and 3 seconds.

Does the 400ms threshold apply to animations and transitions?

No, the threshold applies to perceived wait time, not intentional motion. A deliberate 250ms entrance animation is fine; the threshold governs how quickly the system must acknowledge and respond to a user action.

What should I do when the system cannot respond under 400ms?

Acknowledge the interaction immediately with visual feedback, then use optimistic UI to update the interface before server confirmation, or show skeleton screens and progress indicators. The goal is minimizing perceived waiting, not guaranteeing sub-400ms API responses.