Personal Reflection

On reflection, I developed a lot as a designer and identified many areas to work on. I applied myself in all aspects of the project. I took the lead on visual research, the onboarding design and our final presentation. My role evolved through the project as I adapted to fit the needs of the group. The result was a varied body of work to reflect upon.

Ultimately my design work needs refining. This is best evidenced in my initial iterations (see Appendix AA). At this point, I was adjusting to a new design tool which took significantly longer than expected. I would like to speed this up with some further self-guided lessons. I don’t have the visual communication experience that my teammates have, so I operated quite well when considered.

I undertook a self-directed part of the design process with guidance on information hierarchy and design systems by Sorcha and Iwona. The team decided my tone of voice reflected what the app should convey during our initial iterations. So, therefore, I designed the onboarding process whilst obtaining feedback along the way. This developed my skills in an area I want to improve. In future, I will volunteer to take on more UI work as the only way to learn is by doing.

Considering we have never met, we communicated and collaborated well throughout the project. We overcame challenges by putting the group’s needs over personal opinions allowing us to create an unbiased environment with our user’s experience at the forefront of our process.

In future, quick feedback from testing is essential for evaluating our designs. This should be implemented early and often throughout the process. However, our team did not have experience in prototyping bar one member; therefore, we will improve this by upskilling through various projects on this course.

Our team charter was instrumental in reminding us we all have different perspectives. In future, it would be nice to conduct A/B testing when our ideas on how to proceed were not aligning. This would underpin our decision making with factual data rather than opinion. This would be a great way of preventing lengthy conversations and ensure all voices are heard with the best outcome for the project prevailing.

Fundamentally, we must remember that the bus service is for all users, not just one; therefore, all opinions matter (See Appendix BB).