| Name | Storytelling |
| Abbreviation | STT |
| Learning Cost | 80 |
| Playing Cost | 100 |
| Suggested Phases | 1 |
Engineers
| Mechanical Engineer | Industrial Design | System Engineer | Electrical Engineer | Production Engineer | Software Engineer |
| ✗ | ✔ | ✗ | ✗ | ✗ | ✗ |
Technique and Issue Views
| BusinessNeeds | Stakeholder | Stakeholder Needs | System Requirements | System Structure Architecture |
| ✗ | ✔ | ✔ | ✔ | ✗ |
| System Functional Architecture | Detail Hardware Design | Detail Service Design | Detail Software Design | Manufacturing Operations |
| ✗ | ✗ | ✗ | ✗ | ✗ |
Technique Traits
| Identify Stakeholders | Elicit Needs | Remove Ambiguity | Layman's Terms | Technical Terms | Teamworkings |
| 2 | 2 | 1 | 4 | 0 | 1 |
| Traceability | Prioritizing | Exploring Breadth | Inside the Box | Outside the box | V&V |
| 1 | 0 | 0 | 0 | 0 | 0 |
Verification and Validation
| Analysis | Calculus | Inspection | Demonstration | Test |
| ✗ | ✗ | ✗ | ✗ | ✗ |
Storytelling is as old as human civilization. In the field of design, storytelling is widely used to “get insight into users, build empathy and reach them emotionally” [1]. By building on the use of Personas and inserting them into a complex and realistic setting of user experience, storytelling allows to imagine, analyze, and gain insight into possible scenarios and conflicts. By doing this, it is possible to preemptively individuate problem areas, change features and add new aspects that will improve overall user experience. [2]
