click-test-plan
owl-listener/designer-skills
Design first-click and click tests to measure findability and navigation clarity.
What is click-test-plan?
A skill for designing and structuring click tests that evaluate whether users can locate information and features in interfaces. Use this when testing findability, navigation clarity, or first-click behavior; for broader task-based observation, use test-scenario instead.
- Design first-click tests to identify where users click first for a given task
- Create click-path tests to measure the full sequence of clicks needed to complete a task
- Structure navigation tests to verify users can find items using the nav structure
- Plan five-second tests to measure what users remember from a design
- Define success criteria including correct first click, time to click, confidence rating, and click distribution heat maps
- Analyze results using first-click success rates, click patterns, time hesitation, and confidence correlation
How to install click-test-plan
npx skills add https://github.com/owl-listener/designer-skills --skill click-test-planHow to use click-test-plan
- 1.Define your test objective: what navigation or findability question are you answering?
- 2.Prepare stimuli: identify which screen designs or prototypes to test and which pages/states to show
- 3.Write clear, goal-oriented tasks without UI hints (e.g., 'Where would you click to change your email address?')
- 4.Define success criteria before testing: target click areas, acceptable time thresholds, and confidence scales
- 5.Recruit participants (typically 20-50 for quantitative testing) and identify any segmentation needed
- 6.Conduct the test and collect first-click data, click paths, timing, and confidence ratings
- 7.Analyze results: calculate first-click success rate (aim for above 65%), examine click distribution patterns, and correlate confidence with accuracy
Use cases
- Test whether users can find a specific feature or setting (e.g., email address change) in a new interface design
- Compare alternative navigation structures by running the same tasks against different designs
- Measure findability of key information in a redesigned website or app
- Evaluate whether a new feature is discoverable without explicit UI hints or instructions
- Identify navigation confusion points by analyzing click distribution and hesitation patterns
- UX researchers and designers
- Product managers evaluating interface clarity
- Teams conducting usability testing
- Anyone measuring navigation effectiveness or information findability
click-test-plan FAQ
A first-click test measures only the user's initial click for a task, indicating immediate findability. A click-path test tracks the full sequence of clicks needed to complete a task, revealing navigation efficiency and recovery from wrong choices.
Typically 20-50 participants for quantitative click tests, depending on your confidence requirements and whether you're segmenting by user type.
A first-click success rate above 65% generally indicates good findability—most users can locate the target without trial and error. Below 65% suggests navigation clarity issues.
Use realistic content, not lorem ipsum. Real content helps users make natural decisions and provides more valid test results.
Best practice is to test one task per screen to avoid confusion and get clear results for each navigation question.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: click-test-plan
description: 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.
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
Related skills
More from owl-listener/designer-skills and the wider catalog.
color-system
Build accessible, systematic color palettes with tonal scales, semantic roles, and WCAG contrast compliance.
competitive-analysis
Systematically analyze competitor UX patterns, features, and gaps to inform design strategy.
component-spec
Write complete, implementable component specifications for design systems.
content-strategy
Define what content a product needs, how it's structured, and who owns it.
critique-brand-consistency
Audit UI screens against brand guidelines (mood, voice, tokens) for compliance and consistency.
critique-color
Audit colour contrast, palette coherence, and semantic meaning on a single screen.