Do you speak your stakeholder’s language?
07/05/13 07:45
It’s the most normal thing in the world – project managers hand the charter, the requirements specifications and many other documents to other stakeholders for review and for approval. And it’s also quite normal that this document handover results in rather unpleasant feedbacks like: “I don’t have time for this”, “I don’t understand what is written in there” or a more general: “If you have to write these documents, then do it, but don’t bother me with it…”
The cause for this reaction is most of the time the language in which the document is written. And language does not mean English or French.Read more….
The cause for this reaction is most of the time the language in which the document is written. And language does not mean English or French.Read more….
Comments
The "What's in it for me" principle
08/04/13 23:45
Time and time again the question stands in the room what makes a project successful. And while most people agree today, that a simple "On schedule, in scope, in budget" is not good enough anymore, the term "customer satisfaction" still sounds very tempting. If the customer is happy, what else than success could it be?
But one thing gets easily forgotten - in most cases the customer and the user is not the same entity. The customer is usually a manager, a committee or an overseeing group. But the users, who are most impacted by the change, can be found some levels below. So what if they are not happy - is the project still a success?Read more….
But one thing gets easily forgotten - in most cases the customer and the user is not the same entity. The customer is usually a manager, a committee or an overseeing group. But the users, who are most impacted by the change, can be found some levels below. So what if they are not happy - is the project still a success?Read more….