Overview
How might we design processing time estimates so people can trust and act on AI output?
When to use
- Perfect for AI operations with variable processing times, image generation tools, and applications where wait time transparency improves user experience.
When to skip
- Instant completions where estimates are noise.
- Tasks so unpredictable that any number would be dishonest (say “variable” and show progress instead).
- Background jobs already covered by notifications.
Rules
Exact clocks that constantly jump.
Underestimating so progress hits 99% forever.
No update when the plan adds long tool steps.
Hiding cancel while showing a long ETA.
Evidence
| Product | Implementation |
|---|---|
| Midjourney | Queue and render time expectations for images. |
| DALL·E / ChatGPT images | Wait states for image generations. |
| Adobe Firefly | Progress and timing cues for generative fills. |
| Claude | Long-run indicators for extended thinking or tools. |