Project Initiation Monthly Initiation Weekly Management Daily Management Monthly Closure Project Closure Post-Project Management Appoint the sponsor A01 Appoint the project manager A02 Appoint the key team members A03 Describe the project A04 Identify and plan the deliverables A05 Identify risks and plan responses A06 Have project initiation peer-reviewed A07 Make a go/no-go decision A08 Kick off the project A09 Conduct a focused communication A10 Revise and refine the plans B01 Have the monthly cycle peer-reviewed B02 Make a go/no-go decision B03 Kick off the monthly cycle B04 Conduct a focused communication B05 Measure and report performance C01 Plan responses for deviations C02 Kick off the weekly cycle C03 Conduct a focused communication C04 Manage risks, issues, and change requests D01 Accept completed deliverables D02 Evaluate stakeholder satisfaction E01 Capture lessons and plan for improvements E02 Conduct a focused communication E03 Hand over the product F01 Evaluate stakeholder satisfaction F02 Have the closing activity group peer-reviewed F03 Archive the project documents F04 Celebrate! F05 Conduct a focused communication F06 Evaluate the benefits G01 Generate new ideas G02 Conduct a focused communication G03

E01 - Evaluate stakeholder satisfaction

This management activity belongs to the Monthly Closure group. This group of activities are done at the end of each month to close the cycle and prepare us for the next one.

Send questionnaires to the team members and to the customer, suppliers, or other external stakeholders, to evaluate their satisfaction with the project during the month. Record the results in the Health Register. Make sure the evaluation is anonymous.

Health Register template

Purpose

It’s crucial to have frequent satisfaction evaluations so as to find out about problems and solve them as soon as possible, rather than waiting for undesirable results in the future. This evaluation is not limited to the customer – you should also pay enough attention to the team members, as their satisfaction has a significant impact on the project.

It’s important to keep the evaluation anonymous, as otherwise, some people may not be comfortable expressing their true feelings about the project.

Common pitfalls

Don’t limit your evaluation of customer satisfaction to a few representatives – evaluate all influential people.

Don’t add too many questions to the questionnaire, so as to keep it easy for the stakeholders to respond.

Even when you do your best to keep the questionnaire anonymous, if there are only a few participants, some of their responses may be identifiable. If this occures, try to ignore those personally identifiable items, and never use them in the future. Otherwise, some stakeholders may not trust the anonymity of the evaluation.

To ensure that you won’t see personally identifiable information in the event that it does exist, focus on aggregate data and do not review the answers individually.

Principles

The following principles play a significant role in this management activity:



⊚ Download the manual in PDF

⊚ Download the diagram

⊚ Subscribe to the announcement emails

Thanks for sharing your opinion with us. Please note the following:

  • Please write it briefly and clearly.
  • Feel free to write in any language you prefer.
  • If you have multiple suggestions, please submit them separately.

If your suggestions inspire a positive improvement, we’d be happy to credit you as a contributor (if you provide us with your name and email address in this form).



To distinguish you from random bots on the Web, please enter the number of P3.express activity groups below.


If you like, you can share your name and email address with us, in case we need to talk to you about your comment, or give you credit as a contributor:




It's best to use micro.P3.express instead of the regular P3.express if you have micro-projects with 1 to 7 team members.