SIDM · APPENDIX
Appendix IV — SIDM Project Knowledge Capture and Retrospective Checklist
Use this checklist to determine whether project evidence and lessons can actually support the next project. Each check derives from requirements for…
Use this checklist to determine whether project evidence and lessons can actually support the next project. Each check derives from requirements for inputs, reviews, delivery, retrospective analysis, and standards in the main text. First locate the records and evidence; then use matching item numbers to identify responsibility, status, remaining issues, and reverification requirements. The project manager consolidates the results and each responsible person confirms their own scope.
Project name: ____________________ Project version: ______________ Review date: ______________
Consolidated by: ____________________ Confirmed with: ____________________
Records and Evidence Verification
| No. | Check and evidence required | Complete? | Evidence location or version |
|---|---|---|---|
| 01 | Inputs and direction: Design Direction Definition; the four parties; objectives; user tasks; customer perception; brand rules; manufacturing, cost, and schedule boundaries | ☐ Yes ☐ No ☐ Partial | File location, version, or evidence ID: __________ |
| 02 | Design translation and concepts: brand core, expression rules, protected and adaptable features, CMF, quality and interaction rationale | ☐ Yes ☐ No ☐ Partial | __________ |
| 03 | Reviews and changes: objects and versions, specialist confirmation, authorized decisions, risks, impacts, and reverification | ☐ Yes ☐ No ☐ Partial | __________ |
| 04 | Structure and manufacturing: part interfaces, doors/windows, hardware, processes, assembly, precision, quality checks, shipment and reassembly | ☐ Yes ☐ No ☐ Partial | __________ |
| 05 | Four perspectives: recognition, physical close-up quality, real tasks, manufacturing trace—results, causes, and realization path | ☐ Yes ☐ No ☐ Partial | __________ |
| 06 | Five evidence categories: outcome, rules, execution, external, business—with sources, time, object, scope, and retrievable location | ☐ Yes ☐ No ☐ Partial | __________ |
| 07 | Delivery and observation: project delivery checks, specialist acceptance references, separate design-service and equipment-delivery approvals, buyer/user feedback | ☐ Yes ☐ No ☐ Partial | __________ |
| 08 | Retrospective and rules: usable lessons, matters needing observation, project-specific exceptions, obsolete rules, standards owner, next verification object | ☐ Yes ☐ No ☐ Partial | __________ |
| 09 | Team operation: templates/case library, training, authorization, effective version, superseded documents, update triggers, next-project reuse | ☐ Yes ☐ No ☐ Partial | __________ |
Responsibility and Follow-Up Verification
Use the same numbers as above. Current status may be Not started, In progress, Awaiting confirmation, Awaiting reverification, or Closed. These are project tracking states, not maturity levels. If no issue remains, write “None” rather than leaving an ambiguous blank.
| No. | Responsible person/organization | Current status | Outstanding issue | Condition for reverification |
|---|---|---|---|---|
| 01 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
| 02 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
| 03 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
| 04 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
| 05 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
| 06 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
| 07 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
| 08 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
| 09 | Name / organization: ____ | ____ | Issue, impact, deadline: ____ | Trigger, object, verifier, evidence: ____ |
Closure basis and confirmation date: __________________________________________________
Completion may be confirmed only when required evidence and actions within the stated scope have been checked. Proposing a solution is not the same as closing an issue. If further field or long-term use evidence is needed, record current restrictions, receiving owner, and reverification conditions. Archiving alone does not close an issue.
External use of project cases requires the enterprise's authorization. The equipment enterprise's product standards and the design-service organization's working methods must retain separate ownership. Engineering, manufacturing, and organizational resources should be classified according to their actual contribution rather than automatically labeled as brand equity.
KEEP READING





































