Skip to main content

Review Writing Guide (User Confirmation of Delivery Results)

Goal and Positioning​

  • This guide is used after development is complete to confirm the delivered result with the user.
  • Core objective: collect and record user feedback, analyze the gap between what was implemented and what was expected, and record the necessary modifications requested by the user.

References​

  • Draft: business goals and user flow
  • Plan: technical acceptance checklist and execution scope
  • Code / Iteration: actual implementation and test results

Flow​

  1. User feedback
  • Walk through the user flow from Draft as the review script and let the user describe feedback.
  • Record fields: title, content, category (Bug / Design / Copy / Performance / Accessibility / Suggestion), priority / severity, page / module, device / language / theme if applicable, operation path / reproduction steps, expected result, actual result, and evidence.
  1. Difference analysis
  • For each feedback item, explain the gap between expected and actual behavior.
  • Record fields: difference type (deviation / missing / misunderstanding / experience), reference (Draft / Plan), root-cause category (requirement / implementation / design / data / environment), impact scope, and suggested action (fix / iterate / defer).
  1. Corrections
  • Register correction items for feedback that the user confirms should be changed.
  • Record fields: change summary, involved files, contract / type synchronization (yes / no + note), UI / copy change (yes / no + note), verification record (operation / assertion), and status (todo / in progress / done).

Recording Points (Used with the Template)​

  • Only record these three categories:
    1. User feedback (title / content / category / priority or severity)
    2. Difference analysis (expected vs actual and short reason)
    3. Correction items (change summary, involved files, and contract / type synchronization if any)

Definition of Done (DoD)​

  • The three categories of records are complete: user feedback, difference analysis, and corrections.
  • Correction items match the user's request. If further fixing is needed, enter Iteration.
  • A Review document is produced and can be used as the basis for later iteration or archiving.

Output and Filing​

  • At the end, output the document using the Review Template and provide an execution summary briefing.