Previous steps: We wanted to change the mindset from documenting to ‘communicating your process’, because based on this insight we figured out the incentive for the writer to use the SCREAM! file.
The aim for this sprint is to implement a skeleton of the SCREAM! tool on the Design Method Toolkit website, based on the refined wireframes.
The minimal viable product for this sprint is a skeleton of the SCREAM! tool (where users can log, update projects and create/edit sprints) and the refined wireframes.
The conclusion of this sprint is that user experience is very important for the tool and it needs to be as intuitive and simple as possible.
Key insights
We defined the ‘aha’ moment for the reader and the writer
Why?
We defined for both the reader and the writer the moment they experience the added value of the tool (‘aha’ moment).
- For the reader it happens when he/she is able to find valuable information.
- For the writer it happens when he/she is able to extract (new) insights by writing.
We tried to minimize the steps towards achieving these ‘aha’ moments.
- For the reader this means that he/she should be able to search/filter and browse the projects to find the relevant projects. Besides that there is the sprint summary that gives the reader a quick preview of what happened in this sprint.
- For the writer we decided that there should be 4 phases instead of the 3 we created last sprint . Each phase should focus on one important action to make it less complex. Besides that, the phases should be part of the workflow of the writer
Which events led to this insight?
We researched user onboarding experiences and we refined our wireframes based on the findings.
The writer needs guidance to understand the process
Why?
- To feel how long/easy the process is
- To be able to navigate through the tool
- To understand why the tool asks for certain information
Which events led to this insight?
We researched onboarding and text framing and we refined our wireframes based on the findings. Besides that we did a user test last sprint for the writer’s SCREAM! file.
Results and references are in some cases needed for the reader to understand the process
Why?
For methods such as the literature review, it could be helpful to have a full summary with references. Therefore we have added a page for photo’s, files and links. The writer should always add a title and a description to the upload to make sure the reader is able to understand.
Which events led to this insight?
We have tested a reader’s SCREAM! file with another MediaLAB team that is working on a solution for the baggage reclaim area in Schiphol.
Next steps: Sprint 5 is over! This means only one more sprint to go. Crazy how fast things go. The last sprint will be all about designing the interface, building the skeleton and wrapping up the project!