|
Member
Feature Article
Client Expectations
Part II - Meet them by managing them
by Rob Cimini
Part I on this subject presented the concept that a successful client engagement is achieved by meeting client expectations, with the consultant accepting ultimate accountability for attaining that outcome. But achieving the desired outcome demands that both explicit and implicit client / stakeholder expectations be proactively managed throughout the life of the engagement.
As detailed in Part I, an effective management process is grounded in solid general management skills which support the application of a structure for managing the engagement or project. The degree to which accountability is accepted by the consultant for meeting stakeholder expectations will determine the degree to which he/she actively manages their expectations and therefore relies on general management and project management skills. Part II of this article will present the essential elements for managing stakeholder expectations delivered from the perspective of project management for the non-project management professional.
The key attribute of Project Management, when practiced in its intended structure, is the systemic approach of assigning, managing and enforcing accountability. That is, stakeholders and team members must undertake and be accountable for their contributions to meeting the project objectives if the consultant is to deliver a successful project. So how do stakeholders get assigned and accept accountability? The answer is through their active participation in the development of the project plan. The plan then becomes the tool for managing and enforcing the accountability of all project participants.
In order for the project plan to be an effective tool in managing and enforcing accountability, it must meet four criteria:
- It must be a formal, written document. This does not imply creation of a major literary work but it must contain essential content in order to be a tool for guiding the project.
- It must be realistic, reflecting what the team and consultant feel is achievable and not based on hope driven by management objectives.
- It must be approved to assure awareness of project content by all stakeholders and particularly senior management.
- It must be bought into or else the project becomes the sole property of the consultant and the assigned accountability cannot be effectively enforced.
The project plan forms the foundation for project success. It is a dynamic document that must be flexible to respond to changes in the project environment as well as adjustments in stakeholder expectations. The ensuing discussion will examine the essential content of an effective project plan, identifying project management processes and knowledge areas that are specifically associated with managing stakeholder expectations.
Project Management Processes and Knowledge Areas
Start the Project – The Initiating Process
Resist the inclination to jump into the work of the project in the interest of showing quick results to the client. Conduct a formalized initiation process that:
- Confirms that the business elements such as financial justification and business plan support are solid and verifiable. In one memorable instance, personal experience in challenging project justification saved a client from pursuing an inadvisable project.
- Identifies the stakeholders, their capabilities and potential role in the project.
The output of the Initiating Process is a formalized document called a Charter, in Project Management jargon. The Charter provides a high level overview of the project, deliverables, objectives, why it is being undertaken and identifies the consultant and his/her authority to manage the project. It is the basis for developing the project plan.
Develop the Plan – The Planning Process
Citing the Gantthead Survey first referenced in Part I, the #4 reason for project failures is poor project plans and planning process. Prevent that deficiency by including the following in plan development:
- Scope Definition: Avoid subjective or qualitative descriptions of project objectives – make them quantitative . Identify all major deliverables. Any work not included in this document is excluded from the project!
- Quality Management: Access measures for controlling and assuring the quality of the final project product.
- Schedule: Individual tasks should be tied to achieving a specific deliverable as defined in the Scope Definition. Tasks should not appear as a random list or resemble a “To Do List”. They should designate responsibility and have realistic time frames for completion.
- Cost: Cost estimates are always subject to refinement. The need for scrupulous cost tracking depends on the project. Be sure to quantify the projected accuracy of cost estimates and manage the costs to meet the key stakeholder expectations.
- Risk Management: Risk is not a popular topic for discussion with stakeholders. But managing risk holds greater potential impact on project success than any other aspect of project management. Experience has demonstrated that clients unwilling to embrace this process leave themselves vulnerable and in a defensive posture when a risk event occurs. Risks can be managed. But the consultant in concert with the stakeholders must be willing to search them out and be proactive in confronting them.
- Communications Management: As the stakeholder roster increases, so does the need for effective communications. The project plan should include a formal communications plan that addresses Who needs to know what, When they need to know it, and How will they get the information.
It is crucial to have periodic performance review meetings involving the stakeholders and project team. The objective of these meetings is to highlight progress and discuss only by exception those tasks and deliverables that are deviating from the plan. The protocol for good meeting management must be applied to make these sessions productive.
- Human Resources Management: Stakeholders that will actively participate in the project should be identified on a Responsibilities Assignment Matrix (RAM) along with the project deliverables in which they will contribute.
Several revisions may be required for the plan to evolve and meet the four criteria identified above. Once achieved, a kickoff meeting should be held regardless of the size of the project to formalize plan acceptance and to signal the commencement of plan execution.
Making It Happen – The Executing & Controlling Processes
The Executing process is about working the plan while the Controlling process is concerned with controlling changes to the plan. They proceed concurrently. Controlling the project is a notorious area of weakness in most projects. In fact the #1 reason for project failures according to the Gantthead survey is poor project management skills. It is at this point in a project where these deficiencies become most obvious. Taking the position that no news is good news, is ill-advised and not consistent with good project management. Make the effort to stay abreast of all deliverables.
An essential procedure that must be in place during the Controlling process is change control. The combination of Scope / Quality, Cost and Schedule represent a triple constraint on the project. A change in any one of these plan elements will impact the others. Pressure from stakeholders to improve schedule, add functionality (increase scope) or cut cost are typically encountered. In managing the expectations of the stakeholders, the implications of accommodating these requests must be documented, communicated and approved before the plan is modified for their inclusion.
The Executing and Controlling processes are critical in managing both the explicit and implicit stakeholder expectations and rely heavily on the communication plan and performance review meetings. The consistent application of the communication plan helps ensure that all stakeholders are informed on project status, supports controlling project changes, and aids in resolving the myriad of inevitable obstacles that pose a threat to project success, i.e. meeting the stakeholders’ expectations.
An essential output of the Executing and Controlling Processes is verification that project objectives contained in the Scope Definition have been met. Once confirmed, then project closure can proceed.
Finish the Engagement – The Closing Process
This is a formal process of gaining stakeholder agreement that the project objectives have been met and concluding any administrative project activities. A discussion of lessons learned is strongly encouraged both to promote future improvements and to demonstrate to the stakeholders the consultant’s commitment to excellence.
Focusing on meeting stakeholder expectations puts the consultant on the path to a successful project. But achieving this end requires an approach based on accountability, strong management skills and a process to manage the contributions and accountability of the project participants. The key attribute of Project Management – assigning, managing and enforcing accountability, provides that process. Experience has shown that this holistic approach will yield an acknowledgement from the client for the quality of service instead of having to justify one’s value at the end of the engagement.
Rob Cimini, PMP is Director of Project Management for Pragmatic Consulting, Inc., a consulting firm that provides continuous improvement solutions.
You
could be sharing your wisdom and observations with your fellow IMCNE
members. Submit your article of 250-300 words for consideration
to News & Views Editor Mike Kayat at
, Subject: IMCNE article.
 |