Client expectations are expressed in chartering documents such as the scope of work, the project purpose statement, and the list of project deliverables. Other expectations exist that are more difficult to express in written documents.
Managing Expectations
One project client had such a difficult time with the billing processes on her previous project that significant project management time and resources were expended on reconciling billing issues. This client has an expectation in the next project that project accounting and billing processes operate effectively and efficiently. Another client had been constantly surprised by changes and non-planned events happening on the project. This client wanted to participate early in the discussion of problems that arise during the life of the problem and contribute to finding solutions and minimizing the negative impact on project performance.
Understanding and capturing these expectations in a written document is an important step in effectively meeting client expectations. Often it is the next question that enables a project manager to discover the less obvious expectations. The next question is the one the project manager asks after the initial response to inquiries about expectations. In our example, the client may express that he or she wants project billings to be accurate and timely. This is an easily understandable expectation, but when the project manager asked the next question—“Can you tell me more about what you mean?”—the client revealed the problems on her previous project, and the project team developed a better understanding of the client’s concern. The project team developed measures for tracking project billings that measured both timeliness and accuracy. This process enabled the project team to understand the client’s concern, develop work processes that demonstrated a response, and provide data to the client on the timeliness and the accuracy of the billing processes.
For the client that expected to hear about problems early and participate in the problem-solving discussions, the project team shared the project action item register and highlighted issues the team felt may be important to the client. The project manager also discussed potential concerns with the client during their weekly project update.
After the project team captures the client expectations, the team then develops a method for tracking performance against expectations. In our example, the project team defined accuracy and timeliness in measurable terms and tracked the team performance. The project team developed a survey to track the client’s perception of inclusion in the problem-solving process and tracked the client’s response. These measures were then presented in the project review meetings with other measures of project performance such as cost and schedule.
As the project team meets and exceeds the client expectations, these expectations tend to change. If the goal is 85 percent accuracy on all project billings, and the project team begins to perform with an average of 95 percent accuracy or higher and never falls below 90 percent, then the client begins to expect 95 percent accuracy. This is a realistic expectation of the client; it also changes the expectation so that meeting the client’s expectation becomes harder. Even if expectations change, it is important to maintain the original goal. This reminds the client at the end of the project that the project team not only met expectations but also raised them during the life of the project.
- 1673 reads