Enable participants to understand how some interfaces are better than others at handling different interactions around personal data.
We know that we need to build data-driven services with people in mind. Given the constraints of designing for mobile screens and people's limited attention, we need more than the power of words alone to communicate and demonstrate trust, transparency and control.
There are a range of design methods to achieve this, but what are they? Which design constraints around interfaces, interactions and timings are most suited to the core functionality of a data-driven service on mobile? How are these design constraints dependent on specific goals: to provide people with information about how their personal data is used, get them to engage with it, and give them control over it?
This exercise gives participants the opportunity to sketch design solutions for a mobile app.
Participants work in small teams on the same data-driven service and its core functionality, but each team is given a different goal in terms of asking people for consent, informing them or allowing for control.
Teams are asked to complete the sketching task by selecting design constraints around interface, interaction and timing to come up with solutions for their given goal.
Collaborate with the organiser on the following:
Facilitators should look at all of the service scenarios beforehand: there are twelve fictional data-driven services with three different missions for each service.
Choose one data-driven service. This could be a service that is closest or complementary to your product, or simply one that you find particularly interesting or challenging. Use the set of three scenarios for this service.
Facilitators should familiarise themselves with all of the interface, interaction and timing cards beforehand.
Divide the group into 3 small teams. Explain that this exercise consists of 3 main steps: discovery, sketching and sharing feedback.
Explain the selected data-driven service and its core functionality.
Each team will focus on the same service and functionality, but a different goal.
The aim is to meet the designated goal for the service's core functionality with one team focussing on asking people for consent, another team focussing on informing people and the final team focussing on allowing for control.
Ask each team to understand their service and its core functionality. They should discuss and clarify their particular goal as a team.
Now each team should consider and select three design constraint cards - one for interface, one for interaction and one for timing - that they feel will be relevant to their goal.
Now introduce the sketching task. Ask each team to sketch ideas by using their three design constraints from their chosen cards.
Explain that each team should rapidly and collectively sketch on mobile templates to get to a preferred design that meets their given goal for the service's functionality.
Gather everyone and lead the discussion around the designs that each team has made.
Explain that each team has 1 minute to present their designs based on their goal and their selected design constraints.
Encourage the other teams to listen and give quick, constructive feedback as to why they think some of these decisions are good or where they may need improvement, drawing comparisons between other designs.
In the discussion, consider prompting each team as needed with the following questions:
This tool and any associated downloadable assets are provided under aCreative Commons Attribution-Share Alike CC BY-SA 4.0 International License.
Preparation 30 mins
Delivery 15 mins
Preparation 30 mins
Delivery 90 mins