Helpful Error Messages
Project workbook ยท Path 99

Rewrite a set of interface errors with accurate causes, actionable recovery and a consistent review checklist.

The case

A fictional upload form accepts PDF files up to 5 MB. The draft errors are Invalid, Something went wrong and Access denied. The system can distinguish unsupported file type, excessive size and insufficient permission, but it cannot always determine the cause of a network failure.

ConditionKnown factRecovery available
Wrong typefile is not PDFchoose a PDF
Too largefile exceeds 5 MBchoose a smaller PDF
No permissionaccount cannot uploadask an administrator for access
Network failureupload did not completecheck connection and retry
STAGE 1

Understand the recovery goal

An error message should explain the problem at the level the audience can use and offer a feasible next step. It should not expose internal details merely to sound precise. Start from what the system actually knows. The writing course focuses on messages rather than implementation, and this project follows that boundary.

Your task

Map the four conditions to known facts and available actions.

Required output

Error context table

Record your result and evidence here or in a separate file.

Review gate

No message asserts a cause beyond the known condition.

If the gate is not met

Separate observed failure from a guessed explanation.

STAGE 2

Write specific and actionable copy

Name the relevant object and the correction without unnecessary blame. A file-type error can specify PDF; a size error can state the actual limit. Avoid vague pronouns when several fields or files are present. Keep the primary message concise and use supporting detail only when it helps recovery.

Your task

Rewrite the type and size errors in one or two sentences each.

Required output

Two validation messages

Record your result and evidence here or in a separate file.

Review gate

Both messages state the rule and a feasible correction.

If the gate is not met

Replace invalid with the specific condition that failed.

STAGE 3

Handle permission and uncertainty

Some failures cannot be fixed by changing the current input. A permission message should explain the available route without promising access will be granted. A network failure should not be described as a bad password or server outage without evidence. Preserve uncertainty while still offering a useful retry path.

Your task

Write permission and incomplete-upload messages.

Required output

Two recovery messages

Record your result and evidence here or in a separate file.

Review gate

The network message says the upload did not complete and does not invent a cause.

If the gate is not met

Use a known effect plus a practical next step.

STAGE 4

Review consistency and accessibility

Review terminology, tone, length and placement across the set. Do not rely on a red border or icon alone. An implementation would need to associate messages with fields and announce relevant updates; the writing package specifies these requirements without claiming they were implemented.

Your task

Create a review checklist and annotate where each message belongs.

Required output

Message specification

Record your result and evidence here or in a separate file.

Review gate

Every message has a trigger, location and recovery action.

If the gate is not met

Connect copy to the exact state that displays it.

STAGE 5

Test the copy against scenarios

A scenario review asks whether a reader can identify the problem and next action from the message. It is not a substitute for actual usability research. Use the supplied conditions to test accuracy and create a plan for future user review. Do not invent participant feedback or support-ticket reductions.

Your task

Review all four messages and record one revision with its reason.

Required output

Error-copy handoff

Record your result and evidence here or in a separate file.

Review gate

Claims of effectiveness are limited to the review actually performed.

If the gate is not met

Replace performance promises with a testable question.

Final project

Deliver the condition table, four final messages, trigger and placement notes, checklist and scenario review. Add a fifth condition where retrying is unsafe and explain a different recovery instruction.

Critical condition

Every stated cause is supported by the known condition and every recovery step is feasible in that state.

CriterionPointsEvidence
Evidence and correctness30Calculations, source use and results match the supplied case; limitations are honest.
Required artifacts30All five stage outputs and the capstone handoff are present and inspectable.
Reasoning and decisions20Choices, assumptions, alternatives and the case-specific critical condition are explained.
Reproducibility10A reviewer can follow the stated steps and distinguish expected from observed results.
Clear communication10Labels, units, structure and evidence references make the work easy to review.

Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.

Worked reference

For an oversized file: This PDF is larger than 5 MB. Choose a smaller PDF and try again. For an unknown network cause: The upload did not complete. Check your connection and try again. The second message avoids claiming that the server or the user caused the failure.

Boundaries

This is a content-design specification, not implemented interface behavior or measured reduction in user errors.