Day 8 - Stakeholder Map
Stakeholder maps are create in various forms to determine what parties are involved or even affected by the design process. They can be an endless list of even the most minute parties involved or they can be descriptively specific as to who each person is. Stakeholder maps allow the team to visualize how each party will be affected.
Side note: This is the final method of phase 1 of the challenges. Next post, I will be moving into exploration and immersive research methods!
What I Learned:
Sometimes we can focus in too much on the "user" and their experience. We can focus on the experience of the customer and the CEO. With the stakeholder map, it broadens those views and helps designers visualize not just the main people but also those who surround them. It helps to visualize how design development can effect other stakeholders, other than the user.
I did learn and find interesting that stakeholder maps can be long lists or diagrams of who is involved or they can be the complete opposite. Its also important to note that they can be reiterated on as the project moves forward. People may be removed, others added. What matters is the team can see who they are working with and even times who could be working against the team.
To try this method out, I made a stakeholder map for a project idea that I'll work on at some point. The idea is to do with a person applying for jobs and their experience with it, so I built my stakeholder map around an applicant and the stakeholders in their experience. It is a very rough map that I created in an hour. I first made a list of all the stakeholders involved in this experience and then quickly sketched out a visual version to see how they connected and interacted. I used the example in the book (universal principles of design) to also help guide my thinking.