When we discuss getting close to the user, we often think about the user and customer as interchangeable parts. However, for many projects, you’re customer might not be the user.
Your customer might actually be the client.
In most cases, it will have zero impact on how you do your job, but it is always something to consider — especially when it comes to the stakeholder interviews. When you are working for a client, you want them to feel like they can trust you and that you will listen to their concerns.
You’re still tasked with building better resources with the users in mind, but now you’re talking with the person who could shut it all down if desired. In many ways, this project’s success will hang in the balance of the working relationship with the client — and that relationship begins now.
Resources for review
Please use the following items to guide your exercise attempt:
| Article/Video | Source/Author |
|---|---|
| Voices from the ladder | New Pragmatic |
| The Delicate Art of Interviewing Stakeholders | eightshapes |
Exercise
Length: One-to-two hours to complete.
As stated in the resources above, every project starts with a problem or opportunity to tackle. Most (but not all) clients will then produce an initial set of requirements to kick off the design process.
Using the research you gathered during the previous exercise, study the provided requirements doc and compose a list of ten questions you would like to ask the project stakeholder.
Upon completion, update your Program Journal with links to any assets produced in this exercise. Post your journal in the Feedback-Loop channel for review.
///