View profile

Issue #14: Thinking about the stakeholder experience

It doesn't matter if you work for an agency or in-house. Or whether you're a designer, researcher, de
Issue #14: Thinking about the stakeholder experience
By Jonathan Kochis • Issue #14 • View online
It doesn’t matter if you work for an agency or in-house. Or whether you’re a designer, researcher, developer, or PM – every project you touch has stakeholders.  In short, a stakeholder is someone with an interest or concern in the project you’re working on. We spend a lot of time thinking about the customer experience and less on how it feels for stakeholders to be involved in our work. In this issue I’ve assembled content on the stakeholder experience, why it’s important, and how to improve it. Enjoy!

The Stakeholder Experience
Stakeholder Experience Design
Improving Discovery
Discovery is where it all begins with stakeholders. As mentioned in the post above, failing to engage stakeholders in the discovery phase puts you at risk of losing them for good.
Signalling a Process Change with a Discovery Phase
Discovery Kanban at Optimizely
3 ways to strengthen your discovery phase
Shot from a stakeholder engagement session I conducted as part of a large website overhaul. Projects move much smoother when stakeholders are heard, involved, and respected.
Shot from a stakeholder engagement session I conducted as part of a large website overhaul. Projects move much smoother when stakeholders are heard, involved, and respected.
Did you enjoy this issue?
Jonathan Kochis

A weekly collection of original and curated UX content, ideas, and tips.

If you don't want these updates anymore, please unsubscribe here
If you were forwarded this newsletter and you like it, you can subscribe here
Powered by Revue