#iterativedesign

So this would be my take on a 40 min long video presentation about Iterative Design by two members of Apple’s UX/UI Design team.

The very first thing that was clear to me was in regard to the roles each of the speakers had within the Design team due to the specifics of the content they were communicating, the main speaker being clearly more oriented towards UX and the secondary more visually inclined (UI).

I was very interested on the key differentiations the UX guy made about users and product owners’ goals, and business and app goals, making it easier to dissect the project’s scope to assertively answer key questions about the product and it’s contextual variables in order to impact users’ lives through quality design.

Another key insights that the UX guy highlighted during the presentation was in regard to assimilating that even though we use apps, our perspective can not be the solely considered point of view as it is obviously limited and biased because we perceive according to our wiring... but then again, the hidden treasure for me was in the very distinctive emphasis he made when mentioning that everyone can’t be your user either -Which was basically one important feedback from my first solo project-.

Sincerely writing, when the UI guy cloned the app’s screen in 3 minutes using Keynote I felt so low that I only got better when I stopped and looked at all the work I've done these past three weeks and started writing the post about my experience so far, I guess experience is obviously key, but seriously... 3 minutes?!

Progressively, they started adding variations of the original design in order to have a wider range of options to decide from, and even though this implies extra work... it was pretty clear the importance of having different iterations in order to create good and quality designs, which according to the speakers at the very beginning of the video... It’s no easy task.

Evaluation!

Throughout the seven stages of the creative problem-solving process, Team Aquamarine worked collaboratively to identify weekly objectives, delegate accomplishable tasks, and regularly communicate our design progress noting points of constructive criticism and successful accomplishments. After presenting our Implementation phase of Kideo, showcasing the user experience, product design, and business model, we regrouped to analyze our classmates’ feedback to compare their responses with our intentions. Noting the high interest in Kideo’s playground, we sought out to further develop the feature to emphasize the educational, social, and emotional benefits within our final presentation. Additionally, we determined the need for our presentation deck to be initiated. Breaking down our weekly tasks, we split off to complete the UX/UI design iterations and presentation deck.

Of the methods and techniques reviewed, I find that team Aquamarine has consistently optimized feedback from our classmates, or Jury of Peers, as we remain conscious of our diversity in careers and backgrounds. Consequently, I find that the consistent exchange of feedback has fostered my personal ability to provide constructive criticism to other teams, my team, and myself in my personal work. In reflecting on the tools we used in class to communicate criticism, I found that the Google Sheets format worked best to efficiently and effectively provide and collect feedback. As opposed to the chat offered in Zoom, I could write, reflect, iterate, and repeat without dividing or incorrectly addressing my thoughts. Additionally, the spreadsheet format encouraged me to write more, diversified feedback, and saved time by pre-collecting team notes.