Healthy 365 Design Pitch Preparation
Understanding Healthy’s 365 users
After conducting preliminary exploration through interviews, my team decided to use a survey for secondary research on Healthy 365’s user demographic, user experience and pain points. My team split the app’s users into two groups: current and ex-user. Based on the user group, we identified a few key questions to ask the respective groups to understand the survey participants better. These questions gave us insights on how we can improve the usability and adoption of Healthy 365 amongst Singaporeans. The survey was circulated outside of our social circles to ensure that our feedback was as diverse as possible.
In the meantime…
Because of time constraint, my team started working on our presentation slides and pitch document while waiting for the survey results to come in. Since the content of our presentation and report rely heavily on the survey results, we could only work on the structure of our pitch. I took the initiative to do up the general organisation of the report and slides. When structuring the pitch report, I assumed myself as a designer who is trying to convince the Health Promotion Board to adopt my team’s new app design. By putting myself in the shoe of a designer, I found myself easier to prepare the layout of the report since I need to convince myself that the proposed design is a better one.
Together with Hui Ting, we came up with a rough wireframe of the new app design and a sample Navigation Flow comparison between an old and proposed user journey. Though these were only the first iteration of the wireframe and design flow, it served as a basis for my team to work on after collating the survey results. For the wireframe design, we also lookup several applications of similar functionalities to consider how we can incorporate those designs into ours. Though we looked for alternatives, we did not include those designs into the finalised design proposal yet. We want to redesign Healthy 365 to solve actual problems faced by the users instead of the perceived problems we think the users faced.
Results are in!!!
Due to the tight timeline we faced, we collated our findings on Friday. On Saturday, we narrowed down our targeted user profile from the survey results and identified the common pain point we aimed to solve. With my proposed pitch flow, my team only had to rearrange certain content to improve our argument. Also, we agreed to include proposed solution evaluations to show our understanding of our design decisions.
The Saturday meeting ended with us splitting the remaining work among ourselves and deciding to meet on Monday to go through the presentation flow. I am glad that my teammates are on the ball and do their parts well so that we are confident to complete the assignment on time with surplus time to spare for last-minute refinement.
