Task understanding
Translate natural-language goals into task signals before matching products.
A recorded usability test, one measured improvement and a repeat check.
Start step one ↓My learning →Prompt library →
A working site and a few willing testers. You can use a notebook; analytics software is optional.
These guides are free. Use the free/manual route for practice; optional upgrades are your choice. Account access and app screens can vary.
Choose one starting tool. You do not need every product here. Check its current plan before starting; these are editorial matches, not measured product rankings.
0 of 3 steps checked
Choose an action you can observe, such as finding a service or reaching a contact page.
Task: Find how to ask about a drawing session Success: Reach the public contact route Baseline example: 2 of 5 found it without help These numbers are fictional practice data.
One focused change makes the result easier to interpret.
Observed obstacle: “Let’s talk” was not recognised as Contact. Change: Rename it “Contact” in the main menu. Keep the page content the same for this test.
A small test can reveal problems, but it cannot prove that every visitor will behave the same way.
Review template Before: __ successes out of __ After: __ successes out of __ What differed: __ Decision and reason: __
That is your three-step guide. Keep practising, or try the next level when you feel ready.
THE OTHER FEW — Test whether your website helps visitors Level: advanced https://theotherfew.co.uk/learn/start/website/advanced STEP 1: Define one visitor task Choose an action you can observe, such as finding a service or reaching a contact page. 1. Write the task without naming the link to press. Choose a success condition and a point where the test ends. 2. Invite up to five willing people to try it individually on a phone. Explain that you are testing the site, not them. 3. Record success, obstacles and approximate time. Do not prompt them during the task or collect private details in your notes. EXAMPLE Task: Find how to ask about a drawing session Success: Reach the public contact route Baseline example: 2 of 5 found it without help These numbers are fictional practice data. SELF-CHECK: I have a clear task and a baseline or a labelled practice record. STEP 2: Change the biggest obstacle One focused change makes the result easier to interpret. 1. Group the observed problems. Pick the one that blocked the most people from finishing. 2. Change one thing, such as the menu label or location of the next-action link. Keep a copy or record of the original. 3. Check the changed page on phone and desktop. Test links and keyboard focus before publishing. EXAMPLE Observed obstacle: “Let’s talk” was not recognised as Contact. Change: Rename it “Contact” in the main menu. Keep the page content the same for this test. SELF-CHECK: I changed one obstacle and recorded exactly what changed. STEP 3: Repeat and decide what to keep A small test can reveal problems, but it cannot prove that every visitor will behave the same way. 1. Repeat the same task with new willing testers where possible. Use the same success condition. 2. Compare successes and obstacles with the baseline. Note if the people or devices differed. 3. Keep, adjust or undo the change based on the evidence. Put one follow-up test in your calendar. If nobody is available yet, keep your test plan ready and do not invent results. EXAMPLE Review template Before: __ successes out of __ After: __ successes out of __ What differed: __ Decision and reason: __ SELF-CHECK: I recorded real results or left an honest test plan for later. Self-review only; this is not a qualification.
Saved only in this browser when storage is available. Clearing browser data removes it.
Try the same process on your next project. Use the evidence you collect to choose the next small improvement.
Our examples and practice tasks are original. These references support the platform instructions. Checked 17 October 2026; screens and account features may change.
Workspace and creative photography from Unsplash.
Explore AI tools, software and technology through official sources, clear trade-offs and practical comparisons, so you can find the few that matter to your task.
Recently added to our catalogue, with a reason to explore each one.
Editorial alternatives with a specific reason to consider them.
Describe the outcome, not the software. The Other Few turns the job into a practical stack, keeps overlaps visible, and explains the trade-offs.
We'll break it into jobs, choose the fewest sensible tools and show the trade-offs.
The shortlist now explains the fit, the trade-offs and what to do next.
Translate natural-language goals into task signals before matching products.
Show why a tool fits this search instead of presenting a permanent product score.
Move naturally from shortlist to profile, alternatives, compare and saved tools.
Browse editorial collections when you want to explore rather than solve one task.
The recommendation layer connects tasks, constraints, products, alternatives, workflows and evidence without turning the catalogue into a popularity ranking.
These are the relationships the engine can reason over as the catalogue grows.
With your permission, we use Google Analytics cookies to measure visits and interactions, such as page views, project progress, downloads and link clicks. This sends usage information to Google. You can reject analytics and still use the site, or change your choice using Analytics settings at the bottom of any page.