Choose the task
Choose one reader task from the CSV. State the starting point and excluded operations; do not add product behaviour you do not know.
Concrete output: One reader, one task and a scope note.
FICTIONAL LEARNING EXERCISE
Write a fictional task guide
Turn eight requirements for a sample notes app into a clear guide. There is no real product, account or system to access.
Inspect the sample file
8 sample rows · 5 columns
| requirement_id | task | interface_label | expected_result | error_note |
|---|---|---|---|---|
| T01 | create-note | New note | blank editor opens | — |
| T02 | title-note | Title | title appears in list | title required |
| T03 | save-note | Save | note stored in sample list | — |
| T04 | find-note | Search | matching titles shown | — |
The table shows the first four rows. The file is fictional; some exercises intentionally include missing or conflicting values. Do not interpret them as real operational outcomes.
Download fictional sample CSV ↓Draft the steps
Use one action per step. Link each relevant step to the supplied requirement ID and keep interface labels consistent throughout.
Concrete output: Short instructions linked to requirements.
Expose the gap
Find the missing error description in the CSV. Record a question to resolve rather than filling the gap with an invented product rule.
Concrete output: An open question and bounded review checklist.
Make one revision
Review the draft against the reader’s starting knowledge. Rewrite one ambiguous sentence and briefly explain the reason for your change.
Concrete output: Before/after sentence and reasoning.
My own project narrative
Write what you actually did and its limits in your own words rather than copying a prewritten achievement.
Ask yourself before saving
- Can readers see the basis of the steps?
- Did I invent missing product behaviour?
- Is the document clearly fictional?