You have to break it in order to make it!
The sixth week of my internship was very busy. There were meetings scheduled that needed my presence and there were work and deadlines that were to be met. It was a week that flew by surprisingly fast. Overall I had a lot of meetings to go to and designs that needed approvals and revisions. The meetings that are the highlights are the high-level team meeting where the website's personas were discussed and finalized. Our digital tools team had each prepared three personas and we went through each and every persona. We wrote down the key points, needs, personalities and barriers for each of the personas and then narrowed it down to 3 ideal personas for the new website. The exercise was fun and very interesting. The vice president liked one my personas and it felt good to know that I was thinking in sync with the company's requirements and goals.
User Journey Map - created for an interactive
Another meeting that was very (knowledgeable) was our weekly interactive tools team meeting. We discuss a design/dev trend every week ad it was my turn this week. We updated each other on what we achieved, what changes are to be made and what are the next week's goals. I talked about failure mapping in that meeting. Failure mapping is like making user journeys, the only difference being that instead of going in the direction to building an experience; we break the user experience apart in order to find flaws and bugs that we won't normally see in user journeys or experience maps. As it was a week where we were developing personas, the development intern raised a question that what about the users that are not visualized or dismissed while developing the ideal persona for a project. The question was interesting and failure mapping is an answer to it. We consider the options that are discarded as well as the ideal option in order to make a discuss that is as user-friendly as it can get. I'm finding these weekly discussions helpful as not only it helps me stay updated I can understand a topic from a developer's or a project manager's perspective. Lastly, we had a meeting with the content team i.e. Megan and her supervisor to touch base on the content making and strategy of an interactive I designed and got approval last week. I walked them through the prototype and explained how my design will work and what the content has to achieve in order for my design to work and convey proper message. Deadlines were set and my design was praised by the content manager. All in all, my week was both fruitful as well as busy. Even though I did not realise where the week went, it left me with a satisfied feeling of having worked to the best of my abilities.
