MODULE 6 OF 6 · ABOUT 20 MINUTES

Plan, test and review a small automation

A bounded workflow plan, test table and final review of your six-part workbook.

0 of 6 module checklists reviewed.

Jump to your practice task ↓
A developer workspace with a laptop displaying code.
Course map · six modules

After this module, you should be able to…

  • Describe an input, a rule and an observable output.
  • Test normal, blank and duplicate inputs.
  • Distinguish a tested plan from a connected live workflow.
The shared project source cards · fictional practice material

North Street Studio and its session are invented for this course. These cards are the evidence for the exercises, not an advertisement for a real event.

People studying at wooden tables in a bright library.

Source A · session notice

North Street Studio is hosting Saturday Sketch Club for adults trying drawing. The session is on Saturday, 11am–noon, in the North Room. Bring a pencil and paper.

People studying at wooden tables in a bright library.

Source B · organiser’s practice note

Capacity is eight adults. Attendees bring their own pencil and paper; materials are not supplied. Price, booking link and access arrangements have not been supplied in these practice notes.

UNDERSTAND THE METHOD

Automate a rule you can explain

Our final job is a practice enquiry sorter. Its input is an enquiry ID and a fictional subject. Its rule assigns a category; its output is one row in a practice list. We are not asking a tool to answer customers or make bookings. This bounded result is easier to test than “handle all enquiries”.

Use an explicit rule for this exercise. Trim surrounding spaces and ignore letter case when checking the subject: a subject containing “materials” goes to Materials; one containing “booking” goes to Booking; anything else goes to Needs review. If a subject contains both words, choose Needs review. A fixed rule like this can be planned and tested without generative AI.

UNDERSTAND THE METHOD

Plan the awkward inputs before the live connection

A normal example is not enough. Decide what should happen with a blank subject or a repeated ID. Our brief requires one result per enquiry ID, so a repeat must not silently add another row. Keep the original input visible when something fails, so a reviewer can inspect it.

The test table below is a manual plan. It does not connect a real inbox, form or automation service. If you want to learn the movement of values between steps, our Make practice course covers mapping. If you want a practice form, the Tally course covers that separately. Connecting those pieces is additional work, with its own permissions, settings and tests.

UNDERSTAND THE METHOD

Finish with evidence of what you checked

Predict each test result before running the rule by hand. Compare your results with the worked table. If you later build the workflow in software, run those same cases and inspect the actual stored output rather than assuming that a green run indicator proves the intended result.

Finish the flagship project by reviewing all six outputs: task boundary, prompt and revision, claim table, content kit, plan and workflow test table. Name what remains unknown and what would need to happen before any real publication or app connection. You can finish this course with a notes app or paper; no live customer process needs to be enabled.

The idea made visible

Manual tests for the fictional enquiry sorter
Practice inputCaseExpected result
E01 · “Materials for sketch club”New ID; materials subjectOne Materials result.
E02 · blank subjectMissing informationOne Needs review result.
E01 · same subject againRepeated IDNo extra result.
E03 · “Booking link”New ID; booking subjectOne Booking result.
E04 · “Booking and materials”Two category wordsOne Needs review result.

Compare the two versions

A notebook and fountain pen ready for a first draft.DRAFT TO INSPECT

“When a message arrives, use AI to deal with it.” No ID, expected output, duplicate policy or review point is defined.

A developer workspace with a laptop displaying code.WORKED VERSION
Practice input: enquiry ID + subject. Categorise by the written rule. Blank, ambiguous or unknown subjects go to Needs review. Repeated IDs do not create another result. Keep a test record before considering any live connection.

Common pitfall: A successful test of one mapped value does not prove that a whole enquiry workflow is connected, deduplicated and ready to use.

Words worth knowing

Trigger
The event or action that starts a workflow.
Mapping
Using a value from one step in another step.
Duplicate
A repeated input that needs a defined handling rule.
BUILD YOUR PROJECT · KEEP YOUR OUTPUT

Your practice task

  1. Write the sorter’s input, rule, output and duplicate policy in your workbook.
  2. Run the five supplied tests by hand. Keep your predicted and observed result for each case.
  3. Review the outputs from all six modules. Add one next action for a real task you might try after the course.

You can use the fields below or keep your work in your own notes. Your written work is not uploaded or automatically marked.

Up to 1,600 characters per field. Saves only in this browser.

Review what you made

0 of 3 review checks complete.

Reflect: Which single part of this course will you reuse next week, and what evidence will tell you it helped?

CHECK YOUR UNDERSTANDING

One decision before you move on

E01 arrives for a second time. Your brief requires one result per ID. What should your plan do?

This checks one decision. Your module checklist is a separate review of your own work.

Lesson authorship and background reading

Written by The Other Few · Original course and fictional exercises · Background references checked 17 October 2026. The sources support the general guidance; they do not endorse this course.

The workflow brief and test cases are original teaching exercises. Use the related short courses below for tool-specific practice.

Core exercises can be completed in these notes or on paper. Using an optional tool is a separate choice; check its current access and plan terms.

Optional practice in a tool or shorter lesson

THE OTHER FEW

Find the few things worth knowing.

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.

Popular searches:

🔥 Fresh Few

Recently added to our catalogue, with a reason to explore each one.

💎 Hidden Gems

Editorial alternatives with a specific reason to consider them.

📊 Popular Categories

More from The Other Few
Personal Few

Build the few tools that work together.

Describe the outcome, not the software. The Other Few turns the job into a practical stack, keeps overlaps visible, and explains the trade-offs.

Stack suggestions are task-fit decisions, not product rankings. Commercial relationships must never change compatibility.
READY

Tell us the outcome.

We'll break it into jobs, choose the fewest sensible tools and show the trade-offs.

Evidence-first: current pricing, feature availability and platform support should be shown only when verified from an appropriate source.
THE OTHER FEW · INTELLIGENCE LAYER

From task to decision.

The shortlist now explains the fit, the trade-offs and what to do next.

PERSONALISED FIT
✦

Task understanding

Translate natural-language goals into task signals before matching products.

GoalUse caseConstraints
◎

Compatibility

Show why a tool fits this search instead of presenting a permanent product score.

PlatformExperiencePriority
↗

Decision path

Move naturally from shortlist to profile, alternatives, compare and saved tools.

ExploreCompareSave
DISCOVERY

Go beyond the shortlist.

Browse editorial collections when you want to explore rather than solve one task.

Fresh FewOnly products with a genuine freshness signal.Explore →
Hidden GemsInteresting products that deserve a closer look.Explore →
Popular CategoriesStart with the job, then narrow to the Few.Browse →
VERIFIED SOURCES · EDITORIAL FIT · NO PAID RANKING
RECOMMENDATION GRAPH

See why the Few connect.

The recommendation layer connects tasks, constraints, products, alternatives, workflows and evidence without turning the catalogue into a popularity ranking.

GRAPH ACTIVE
YOUR TASKgoal + constraintsTASKFITTOOLEVIDENCE intentexperienceplatformpriorityproductalternativesourcefreshness
EXAMPLE DECISION PATH
1 · GoalBuild a website for a small business.
2 · ConstraintsBeginner · web · low-code · ease.
3 · Candidate setReplit · Lovable · Claude — narrowed before presentation.
4 · Trade-offLovable favours simplicity; Replit offers more control; Claude is broader rather than purpose-built for the build.
Compatibility is task-specific. It is not a permanent product rating.

Graph signals

These are the relationships the engine can reason over as the catalogue grows.

Goal / intentConstraintTask fitAlternativeWorkflow overlapEvidenceFreshnessSaved context
Important: the graph does not invent evidence. Unsupported claims remain unsupported until verified.
PERSONAL DECISION LAYER

Make the decision smaller.

Bring your goal, saved tools, workflows and fresh changes together. The Other Few narrows the decision without pretending there is one universal winner.
● Decision context ready
Launch a businessBuild a websiteCreate videosResearch & decide
GoalWaiting
ConstraintsWaiting
Your FewLocal saves
ChangesFreshness ready
Start with the outcome.

We'll turn it into a smaller, clearer decision using the intelligence already built into The Other Few.
Fit is contextual. Editorial judgement, evidence and commercial relationships remain separate.Private on this device.
Intelligence Core
Make the catalogue smarter, not just bigger.
The intelligence layer now treats products, tasks, constraints, alternatives and workflows as connected evidence. Expansion is staged into verification lanes rather than filling the catalogue with unverified entries.
18 core records · verification-first
18Core records
7Categories covered
14Relationship types
0Fabricated records

Connected catalogue

Core products are connected to the tasks and categories they are already structured to serve.

Expansion lanes

These are research lanes, not unpublished product claims. A lane becomes catalogue data only after source verification and taxonomy review.
Editorial rule: catalogue breadth never outranks evidence quality. A product can enter the research queue without entering the public Few.
Intelligence Core

One brain. Every decision.

The catalogue, Finder, Decision Engine, workflows, Your Few and freshness signals now have a shared conceptual layer. The goal is not more results — it is better decisions with fewer tools.
● CORE MODEL READY

Decision graph

The same product can play different roles depending on the user's outcome and constraints.
18core products
7active categories
0saved tools
0watched tools
GoalOutcome
IntentTask
ConstraintsFit limits
ProductsCatalogue
DecisionFew