Minor Project - HealthCamp
Ahmed Yaman Ibrahim (0341119)
Minor Project
MINOR PROJECT
Week 1
In the first week, we sorted ourselves into our respective groups for our projects. In my case, my project was a fitness app named Healthify, and our group's task was to work with the business and computing teams to develop a prototype for the app based on they specifications given to us in the brief. During week 1, we met the members from business and computing, and had an ice breaking session to share our contact details and plan ahead for the project.
Reflections: When the groups were finalized I was a bit unsure if it would be efficient to have just one UX student for a project where the final brief is an app prototype, but we had to balance out members for all the groups so we had to make do with what we could. Afterwards, we met the other groups involved in the project and introduced ourselves. We learned what each group would be in charge of and agreed to set up a group chat to discuss what we would be doing next.
Week 2
In the second week, the business team (EAP) provided us with their outline of how they wanted the app prototype to look. We had not yet started the production process as we were still in the ideation phase, but we agreed we would use it as a reference when we start production of the prototype.
We agreed with EAP to use the group chat as our main method of discussion as it would be easier to respond there. We told them that it would be a while before we started our production process, but we would consult with them if we ever have questions regarding the project or the ideation stage.
Meanwhile in our class sessions, we had a lesson on Design Thinking and how we would be using it during our own project.
Reflections: There was some confusion as to whether Computing was still involved at this stage as they mentioned during the first meeting that they were having some issues with how the project was set up and that they would sort it out soon. We had no response from them since then for the next few weeks. At this stage we did not really have much to discuss with EAP either so there wasn’t much communication between us.
Week 3
We continued with the ideation stage and after some preliminary research we developed user personas for our project. We went through some extensive correction at this point as we eventually realized there were 3 different target audiences for the project and that we would need to figure out a way to cater the app to all 3 of them.
User personas:
Based on the feedback given, we continued working on the user personas to figure out how to address all 3 target audiences.
Reflections: Figuring out how to target the app to 3 different audiences was possible in theory but I realized that once we get to the production phase it would make things quite difficult as we would have to design the app to essentially work in 3 different ways. Moreover this was not part of what EAP presented us with but our own conclusions from research and consultation, so we had to figure out how we would prioritize it as well.
Week 4
After finalizing the user personas, we created a questionnaire to gather feedback on the different kinds of potential users for the fitness app and what they would ideally want out of such a service. The questions in the survey were adjusted based on how each group would make use of the app.
Link to survey: https://docs.google.com/forms/d/1xYIhqQ57OhfS2s1zKZDn544zlwX6l0GYRRNzi2G_MBA/edit?usp=sharing
The 3 target audiences for the app were split into:
1. Personal users (teenagers - adolescents, either students or employed)
2. Business owners, looking to incorporate fitness into their work culture
3. Content creators for a platform to create fitness content and earn from it
Based on the responses for the survey, 3 conclusions were made:
1. Personal users: The majority of personal users are teenagers and young adults who are either students or employed, with busy schedules. They believe they do not take care of their health as much as they should, and would prefer that the app provides features tailored to their needs. They are also open to the idea of a paid service if it provides greater benefits, and many have requested a personal coaching service.
2. Business owners: Business owners would like to introduce a fitness service to their company in order to motivate employees to take better care of their health, as it would benefit both them and the company by making employees more productive and reducing the risk of workers falling ill. They are open to the idea of providing employees with rewards based on how well they perform in their fitness tasks.
3. Content creators: Content creators are looking for a platform to post fitness content, and they request features that would allow them to better interact with their community. They are also willing to offer personal coaching as a service, which has been requested by personal users as well.
Based on this information, we then created a user journey map for the 3 personas. We went through some extensive feedback sessions where we had to redesign the journey map a few times over to make sure we covered all our bases.
Reflections: This stage was quite difficult for us as we were essentially designing a journey map for 3 different kinds of users and we had to make sure all their needs were met. It took some effort but I think we managed to make it extensive enough to cover all our bases.
Week 5
During this week, we discussed with Mr Mike about our lack of communication with the computing team and after some discussion, we set up a meeting with the other groups to put forward our initial presentation to the client, Ms Jessie. We also went through our user journey map one more time to ensure everything was the way it should be.
Full user journey map:
Reflections: After discussing with EAP and Computing during the meeting, we had one more meeting by ourselves to figure out any issues we might have from our previous lack of communication and to make sure we knew what content we would be making for the presentation. We were able to stay on the same page but we did have to make some adjustments to what our final product would be based on what we are able to do with the time that we have.
Week 6
We had our initial presentation with Ms Jessie and resolved to maintain communication with the other groups for the duration of the project based on the feedback we got. We also had another meeting with Computing and EAP to finalize all the features that would go into the app and agreed to start developing the lo-fi prototype for the app.
Design team content for our initial presentation:
Reflections: The meeting we had after our briefing with Ms Jessie gave us a much clearer outlook at what would go into the actual app prototype, so we resolved to make sure everything we add to it is content that all groups agreed on. In the meantime, our other group members began working on designs for the social media side of the project, based on the touchpoints from the user journey map.
Week 7
While I worked on the lo-fi prototype, feedback sessions with Mr Mike gave us some ideas on what kind of content we should be making in terms of social media posts. We continued to work on both.
Reflections: While the progress for the lo-fi prototype was going smoothly, we were a bit stuck on what kind of content we would be making in terms of social media, as when we discussed with EAP they mentioned that they did not have a clear social media marketing plan, which meant that we only had our touchpoints to work with.
Week 8
After some deliberation, we created an art direction board and project timeline to ensure our designs are consistent and to keep track of what work each member was doing. I continued to work on and finish up the lo-fi prototype.
Reflections: As the app prototypes were a lot of work on their own, I was unable to spend as much time as I would have liked to review the work the other members were doing for the social media side of the project, so I resolved to finish up the prototypes sooner and to help the others manage the social media content. (This did not go as planned as the hi-fidelity prototype ended up taking a lot longer than expected to finish).
Week 9
Finished up the lo-fi prototype and discussed it with EAP and Computing; as they had no issues with it, I went ahead with developing the hi-fidelity prototype. We also had extensive feedback sessions with Mr Mike with regards to the social media content, in order to make sure it was consistent.
Lo-fi prototype:
Link to lo-fi prototype: https://www.figma.com/file/Ik3xlwLGOF99pTDGpwwZ5W/Healthify-lofi?node-id=0%3A1
Social media content in progress:
Reflections: Prototype production was going smoothly but we were still facing issues with social media content as there was quite a lot to do and we had to make sure all the work was consistent. In terms of workload the app prototypes were quite heavy and it became a challenge to make sure I was keeping up with my other modules as well.
Week 10
We continued working on prototype and social media content, and made adjustments based on previous feedback.
Reflections: Our work kind of slowed down during this week as we all got quite busy with our other modules as well, but we made sure to at least make some progress each week. The hi-fidelity prototype was taking longer than initially expected but there were no further adjustments to make in terms of the content so we could just continue working on it.
Week 11
Finished up the first iteration of the hi-fidelity prototype and made further adjustments to social media content to make sure it was consistent.
Hi-fidelity prototype 1:
Link to first prototype: https://www.figma.com/file/WdOQW1SYS2dhqNTVCjY660/Healthify-hifi?node-id=0%3A1
Reflections: More or less the same as last week, a lot of us faced setbacks because of our other modules, but we were able to make some progress regardless.
Week 12
Although EAP and Computing were happy with the prototype, we had to adjust the visual design of the prototype to match the art direction seen in the social media content.
Reflections: As I was nearing the end of designing the hi-fidelity prototype, I went over everything again to make sure there wasn’t anything I missed, and I realized I was a lot more proficient at working on prototyping software than I was before. On the other hand, it had still taken quite a chunk out of my time and I had to make sure I was still keeping up with my other modules and making sure the design team had made progress for the coming week.
Week 13
We had to finalize a new name for the app due to copyright issues, and we also began preparing for the final presentation to Ms Jessie. At this point we were also slowly working on the Spatial environment for the brand. I also finalized the design for the hi-fidelity prototype.
Hi-fidelity prototype 2:
Link to final prototype: https://www.figma.com/file/GJDtE7jemM4hTAlFn3D4Uq/Healthify-hifi2?node-id=0%3A1
Reflections: All of my modules are at their busiest stages at this point so dividing up my time has become quite difficult, especially because for this project we have to keep making sure all our schedules align if we want to have a meeting. Issues like that have caused delays from time to time but hopefully we should be able to complete everything soon enough.
Week 14-16
We changed the name of the brand from Healthify to HealthCamp, and finished up our final presentations for both this module and for the final meeting with Ms Jessie. We also went through all the content we made one last time to ensure everything was as consistent as it could be.
Finalizing social media content:
Final presentation for Minor Project module:
Final presentation with client:
Link to all design content: https://drive.google.com/drive/folders/1ZAY2a4lvroYGd0C_4pvrTQb5kKtU2UGS?usp=sharing
Reflections: We ran into a lot of trouble trying to finalize the new name for the brand due to conflicts brought up by the Computing team, but we were eventually able to decide on a new name (HealthCamp) and immediately got to replacing the old logo on our design work with the new one.
All in all, this project was a learning experience in terms of figuring out how to work with teams from different backgrounds and understanding teamwork in general, especially in situations like aligning project timelines and constant communication. It was hectic and frustrating at times but overall an interesting experience and I can say I learned quite a bit, both in terms of team experience as well as in a technical sense.