The decision
A manual test lets you discover the work hidden behind a polished demo. Offer a narrowly defined result to a small number of suitable users, explain that it is a test, and record how you produce it. You are learning which steps repeat and which require judgment. The test does not need to become a service business if your goal is a self-serve product.
A worked example
For client updates, ask for one anonymized approved note and return a draft with supporting source excerpts. Time preparation, drafting, factual checks, and revisions separately. If the draft is fast but verification takes twenty minutes, your product must help with evidence checking rather than simply generate more text.
How to put it into practice
- State what you will receive, produce, and exclude. Obtain permission for the data and any model processing.
- Define success before seeing the result: supported facts, acceptable tone, and editing time.
- Keep a step log so you can identify stable work suitable for automation.
- Ask the user to compare the result with their current process, then discuss an explicit next commitment.
A failure to plan for
A bespoke result can hide the fact that a self-serve workflow will fail on messy input. Repeat the test with varied examples and minimal guidance. Record how often you have to intervene and what information was missing.
Try it on your project
Deliver three manual examples with the same input and output contract. Write down every intervention. Choose one repeated step to automate and leave exceptional judgment with the user until you have a safe design.
Keep the next step small
Use the free demand scorecard or planning tools to make your assumptions explicit. The $19 launch kit brings the blueprint and seven editable worksheets together.