Discover
Our research consisted of 7 user interviews with people who send out event details to various groups.
Script: https://bit.ly/3zxh2NI
The answers to the interview questions were then sorted out in an affinity map.

Affinity Map to extract insights
Insights:
- Content to be distributed — Content structure varies across senders based on audience and content
- How senders distribute — Senders are left to their own devices when deciding on the process of how to send out information
- After the content is distributed — Senders want visibility in seeing who has read messages in a group so they know who has received and read it
- Preference on how information is presented — Users want information and payment to be together so they don’t forget that they have to pay and if they do, they can find it and pay at the source of the information
- Struggles receivers have — Users are overloaded with the amount of information they receive and are fearful of missing notifications and want to be able to action events at the source e.g. accept/decline, add to calendar
- Wish as receivers — Users want to be able to share their calendars with their children so everyone has visibility of each other’s schedule
- Senders care about whether receivers have understood their message
We also created empathy maps to be clear on who our senders were. There are three groups of senders, namely full-time parents, organisational users, and the old fashion. I will just showcase the full-time parents' empathy map here as it is the main empathy map that we built for our app.

Full-time Parent
Define
In addition to writing the problem statement, we also selected the 4 most important insights and created “How might we” statements to have a clearer idea of the problem we are solving for.