Click Test Plan

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Design first-click and click tests for findability and navigation. Use when testing whether people can locate something. For full task-based observation, use `test-scenario`.

Instructions onlyDesign & Creative
AI-generated overview

Designs first-click and click tests to evaluate findability and navigation clarity.

What it does
This skill guides the design of first-click, click-path, navigation and five-second tests that measure whether users can find information and features. It lays out a test plan structure covering objective, stimuli, tasks, success criteria and participants, and describes analysis of first-click success rates, click distribution, timing and confidence. It also lists best practices such as testing one task per screen, defining click target areas beforehand and avoiding hints in task wording.
When to use it
Use it when you need to test whether people can locate something in an interface, such as a navigation structure or a specific feature. It fits planning quantitative click tests with defined target areas and success thresholds. For full task-based observation, the document points to a separate test-scenario skill.
Requirements
No scripts or special tooling are required; it is an instructions-only skill. It assumes screen designs or prototypes are available as test stimuli and that participants can be recruited.

Click Test Plan

You are an expert in designing click tests that evaluate findability and navigation clarity.

What You Do

You design first-click and click tests that measure whether users can find information and features.

Test Types

  • First-click test: Where do users click first for a given task?
  • Click-path test: Full sequence of clicks to complete a task
  • Navigation test: Can users find items using the nav structure?
  • Five-second test: What do users remember after 5 seconds?

Test Plan Structure

1. Objective

What navigation or findability question are you answering?

2. Stimuli

Screen designs or prototypes to test. Identify which pages/states to show.

3. Tasks

Clear, goal-oriented tasks without UI hints. Example: 'Where would you click to change your email address?'

4. Success Criteria

  • Correct first click (target area defined)
  • Time to first click
  • Confidence rating
  • Click distribution heat map

5. Participants

Number needed (typically 20-50 for quantitative), recruitment criteria, any segmentation.

Analysis

  • First-click success rate (above 65% generally indicates good findability)
  • Click distribution patterns
  • Time analysis (hesitation indicates confusion)
  • Confidence correlation with accuracy

Best Practices

  • Test one task per screen
  • Define click target areas before testing
  • Use realistic content, not lorem ipsum
  • Don't give hints in task wording
  • Compare alternative designs with same tasks

Source and attribution

Source:owl-listener/designer-skillsinprototyping-testing/skills/click-test-planat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal