Reflective Journal Week 2 (13/03/2017)
Monday 13th March: What did I do? Today, I was introduced to Adobe Spark by David Walters. Adobe Spark seems like a much more appealing option for a journal than a written book. I spent all day converting work from my written journal into this online one, which took a while, but it will definitely be worth it in the long run as it's both quicker and more aesthetically pleasing!
So what? Using Adobe Spark will allow me to create detailed reflection on my work in a fast and efficient manner. The software allows me to structure my work with images, videos and text so I can expand on what I did much easily. The Videos will help the reader understand the steps I went through to create a certain design, and the images help with reference, inspiration and tools used, as well as being much more visibly appealing for any viewer in comparison to a written textbook.
Now what? I will continue to use Adobe Spark to do a weekly journal which shows progress from every day in that week. The journal is based on a simple principle, what?, so what?, now what? and this principle will be maintained throughout. As I continue to keep up this journal I can relate back to it at anytime if I need to recall any information or any process I forgot about. The journal will also be a key part of my final project as it is a way in which I can evaluate how I did from week to week. If I feel the need to delve into any of these sub-headings in more detail, I may explain it in a different section. These points are just for guidance. (what?, so what?, now what?)
Tuesday 14th March: What? Today I presented my idea to the class and tutor Jason Barlow using a PowerPoint presentation with my team mate Ryan Hodder. Going into the presentation, we had a pretty clear understanding of each other's role, and intended to take it in turns with each slide, explaining each bullet point in more depth. I felt very nervous going into the presentation as I was afraid of messing up due to the grading of the whole thing.
Our PowerPoint was simple with few bullet points that were intended to be a start point for us to expand on answering key questions regarding our concept, such as target audience, base concept, inspiration and our individual roles on the project. Looking at past presentations I realised it's much better to have less text on the slide so the viewers don't get too bored.This also allows you to relay much more information through speech. As a whole, I believe this was a pretty solid game plan for us to follow for a successful presentation.
Leading up to the presentation, we hadn't really done a run-through of the entire thing as we thought it would be enough for us to revise our own slides and know what we were going to say.
Our presentation also featured a clip that we were supposed to have time stamped from 3:00 to the end of the video. The video was to explain some of the inspiration we used when thinking of our concept, which was an oriental village based on Japanese culture.
The presentation didn't have the strongest of starts with my team mate Ryan Hodder not being able to remember what he had revised to say. I noticed him struggling and reading the slides so I quickly decided to take over and say a few points while he recouped. He quickly took back over and gained confidence and was able to successfully finish his part. I was a bit shook up from the previous incident so I felt very pressured in my slide, leading me to repeat some things twice. However, I would say it went quite well. Midway through our presentation, Ryan was supposed to have explained a short clip which we time stamped around 3 minutes but he didn't get across everything that I was hoping for, so I tried to improvise and add onto his statement, but at this point he had already gone off the video so it was hard to relate what I was saying when the video wasn't there for the audience to see. The presentation finished fairly strong with me and Ryan feeling a bit more comfortable, I was also able to show off some of the work I had done previously on Japanese culture before even starting this project.