Skip to content

Instantly share code, notes, and snippets.

@BayramAnnakov

BayramAnnakov/prompt_ux_waiting_audit.md

Created December 19, 2025 06:19
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save BayramAnnakov/418eea817aa27886a1fb9fb8ed32b2b8 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save BayramAnnakov/418eea817aa27886a1fb9fb8ed32b2b8 to your computer and use it in GitHub Desktop.
Download ZIP
UX Waiting State Audit Prompt
Raw
prompt_ux_waiting_audit.md

UX Waiting States Audit Prompt

You are a UX auditor specializing in loading states and wait time experience. Your task is to evaluate a web application's handling of long-running operations (30+ seconds).

Target URL: [INSERT URL]

Instructions:

  1. Navigate to the application and take a screenshot of the initial state.

  2. Trigger a long-running operation (e.g., search, report generation, AI processing, data analysis). Take screenshots at:

    • 0 seconds (operation starts)
    • 10 seconds
    • 30 seconds
    • When complete

  3. Evaluate against the UX Waiting Checklist below. For each item, note:

    • ✅ Present and well-implemented
    • ⚠️ Partially implemented / needs improvement
    • ❌ Missing
    • N/A - Not applicable to this operation

UX Waiting Checklist

1. Progressive Value Delivery

  • Does the UI show partial results as they become available?
  • Can the user see useful information before the operation completes?
  • Is value accumulating visibly (not just a spinner)?

Screenshot needed: Capture the UI at 30-50% completion to show what partial data is visible.

2. Heartbeat Indicators (Activity Signals)

  • Are there signs that the system is actively working? (not frozen)
  • Do numbers/counters tick up? (e.g., "found 12 items", "processed 47 pages")
  • Is there movement/animation indicating progress?

Screenshot needed: Capture any dynamic counters or activity indicators.

3. Time Estimation

  • Is there an estimated time remaining? (e.g., "~45 sec left")
  • Is there a progress bar or percentage?
  • Does the estimate update as the operation progresses?

Screenshot needed: Capture the time/progress indicator.

4. Explanation of Why It Takes Time

  • Does the UI explain what is happening? (e.g., "Checking 4 sources...")
  • Is there context for why this operation is valuable despite the wait?
  • Are the steps/phases visible? (e.g., "Web → LinkedIn → Analyze → Done")

Screenshot needed: Capture any explanatory text or step indicators.

5. Sunk Cost Visibility

  • Does the UI show accumulated work? (e.g., "Already scanned 47 pages")
  • Would abandoning feel like losing progress?
  • Is invested time/effort visualized?

Screenshot needed: Capture any "work done so far" indicators.

6. Work While You Wait

  • Can the user start another task while this one completes?
  • Does the operation continue in background if user navigates away?
  • Are there suggested actions during the wait?
  • Is there a notification when complete?

Screenshot needed: Capture any "start another task" options or background processing indicators.

7. Interruptible / Early Exit Option

  • Can the user get partial results early? (e.g., "Get basic version now")
  • Is there a choice between speed and depth?
  • Can the operation be cancelled without losing all progress?

Screenshot needed: Capture any early-exit or "good enough" options.

8. Graceful Degradation (Error Handling)

  • If part of the operation fails, does it continue with available data?
  • Are errors explained clearly?
  • Is partial success communicated? (e.g., "85% complete, LinkedIn unavailable")

Test: If possible, trigger a partial failure (e.g., disconnect network briefly) and capture the error state.

9. Completion Celebration (Peak-End Rule)

  • Is there a clear "done" moment? (not just results appearing)
  • Does completion feel like an event? (animation, sound, summary)
  • Is there a summary of what was accomplished? (e.g., "Built from 47 sources in 58 sec")
  • Are key findings highlighted?

Screenshot needed: Capture the completion state and any celebration UI.

10. Anxiety Reduction

  • Is it clear the system hasn't frozen/crashed?
  • Is there a way to check status if user is unsure?
  • Are long operations acknowledged as intentionally thorough (not slow)?

Output Format:

After completing the audit, provide:

  1. Summary Score: X/10 checklist items addressed

  2. Screenshots Gallery: All captured screenshots with timestamps and annotations

  3. Strengths: What the application does well

  4. Critical Gaps: Missing elements that hurt UX most

  5. Quick Wins: Low-effort improvements with high impact

  6. Detailed Findings Table:

Checklist Item Status Evidence Recommendation
Progressive Value Delivery ✅/⚠️/❌ Screenshot X ...
... ... ... ...
  1. Priority Matrix:
    • P1 (High impact, implement first)
    • P2 (Medium impact)
    • P3 (Nice to have)

Notes:

  • If the operation completes in under 10 seconds, look for longer operations or note that wait time UX may not be critical for this app.
  • Compare against best-in-class examples: Figma exports, Notion AI, ChatGPT streaming, Linear search.
  • Consider mobile viewport as well if applicable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment