Learnings
Below are our learnings from the design sprint. In order:
Assign roles and involve the customer
Limit the design sprint team to a maximum of seven members
Brainstorm and sketch
Quality over quantity in testing
Film both the tester and the way he or she carries out the assignments
Involve end users and colleagues in testing
1. Assign roles and involve the customer
During a design sprint it is important to divide the roles and to state what is expected of everyone in a certain role. This way you can steer in a targeted manner during the design sprint. Furthermore, it is important to involve the client (in the case of an agency) in the design sprint, so that they can share substantive knowledge about their hospital email lists vision & company and make choices. We have divided and filled in the following roles during the design sprint:
Decider: representative from the client side who ultimately had the final say when choices had to be made. (Represented by de Jong & Laan)
Stakeholders: the most important representatives from the organization who had input into the product. (Represented by de Jong & Laan)
Facilitator: someone who knows the process well, monitors it and guides the team through the sessions during the design sprint. (Represented by us)
UX designer & designer: the team members who shape the prototype. (Represented by us)
Developer: to gain background information about the project and to think along in solutions. (Represented by us)
SEO specialist : to think along with the project from an SEO perspective. (Represented for a collaboration partner)
During the five-day sprint we worked together with the customer.
Decider & stakeholders
The client had the decision-making role where they were decisive in making choices regarding the product to be developed. Issues that you can think of are as follows.