Types of Influences
To move projects forward (aka–gain buy-in from stakeholders) you must clearly explain how your solution addresses project goals. Furthermore, it’s as crucial to convey this information to your other team members involved (i.e. Development, Product, Marketing…) so they know how their contribution best serves the overall picture.
- It provides an opportunity for other members to connect with and understand your customers
- It explains the why behind design decisions and future product features (so everyone is on the same page)
- It validate the importance of all feedback, early in the process
Tailor Your Documentation
Part of being a good UX researcher & designer is articulating and sharing your research findings to various team members, whether on your direct team, to those that oversee the project, and to people completely outside your team.
Consider your audience
The best approach is to develop an understanding of other people’s perspectives, and then tailor your findings, that is specific to what that team member cares about.
Ask useful questions
The purpose of asking questions is to encourage the other person to share what is important to them. This is how you develop an understanding of the other person’s perspective.
Questions you could ask:
- What is the main priority of this project from your perspective?
- How does this project affect your teams goals, the business goals, your personal development?
- What is the most important information you need right now, to move this project forward?
Consider cognitive load
The more clutter, noise, or choices we present people with, it increasingly becomes harder for them to concentrate on the task at hand.
Tailer your documentation
Knowing who you’re sharing your findings too, and what they care about most is the key to keeping their interest.
In essence, It’s your responsibility to figure out what motivates them, what matters most to them, and how you can best share your proposal with them.
Finding the best approach to deliver your information requires experimentation, so take the time to find what serves each team member best.
If all else fails. Name your file README.TXT and team members will read! ⚡️