Client focus

Share to0

ArticleQuality Management, Stakeholder EngagementJune 1997

PM Network

Darnall, Russell W.

How to cite this article:

Darnall, R. W. (1997). Client focus. PM Network, 11(6), 42–44.
Reprints and Permissions – opens in a new tab

This article contains an excerpt from Russell W. Darnall's 1996 book, The World's Greatest Project, in which these ten suggestions are offered for increasing client satisfaction: 1) educate your clients; 2) clarify your clients' expectations; 3) establish standards and procedures for making decisions; 4) tackle tough issues early; 5) provide mechanisms for revisiting key decisions/issues; 6) manage around milestones; 7) celebrate milestones with clients; 8) include clients on the team or in the solution; 9) clarify your clients' important values; and 10) deal evenly with your clients.

Presenting project and quality management concepts in a unique, engaging narrative style, Darnall's book, published in 1996 by PMI, covers the ABCs of TQM on projects.

By Russell W. Darnall

From Chapter Five: Managing Client Expectations

EARLY ONE EVENING, as the last few cars left the office parking lot for home and families, Ken sat in John's office discussing the integration team meeting. The meeting had gone well. Although the project was still in an early phase, everything was happening on schedule. But something was bothering John.

“Do you think the client is pleased with our approach to the project?” asked John.

“He's been a part of developing the approach with us” said Ken. “If he wasn't happy with our approach, I would think we'd know it by now.”

“Clients aren't always that open about what they think. You know about my last project. We did a good job. One of the best projects I've managed, but the client was not happy in the end. He admitted that we'd met all the criteria in the project scope but said the project should have gone better. I don't know why it ended so poorly because we started out great and maintained a good relationship until the last stages of the project. It wasn't the project's performance—the client's expectations were a moving target, and that caused the project to look poor. I don't want that to happen again.”

“A client always feels frustration during the life of a project,” said Ken. “How well we manage that frustration probably determines how the client views the success at the end of the project. We may want to develop a plan to manage that frustration.”

“Speaking from experience, clients aren't always open about what they're feeling. How do we know when the client is frustrated?” said John.

“There are usually symptoms,” responded Ken. “When the client is late for meetings, doesn't attend meetings, is slow to return phone calls, these are all signs of discontent. When a client feels uncomfortable with the team, he won't tell you that. He'll give you a credible excuse like pressures from the boss, but…”

They exchanged a silent, knowing expression. Then Ken and John spent the next hour planning how the project team could better understand the client's expectations, measure how well the project was meeting those expectations and increase the client's comfort level with the project. Together, they outlined for the project team a Plan to Meet Client Expectations:

img

1. Educate the client from the beginning on what it takes to get the job done. “After years of experience executing projects” Ken said, “the project team understands the phases and frustrations of projects. Because of this experience, periods of frustration are taken in stride. The team understands the events that lead to the frustrations and knows how to deal with them.

“These same experiences can be much more disconcerting for clients. By explaining what to expect and planning with the client a process for minimizing the impact of these concerns, the team prepares the client for these events and reduces his frustrations.”

2. Clarify expectations. “There are three important points under this heading” said Ken.

img Ask specifically what the client expects and develop a written statement of expectations. This goes beyond the scope of services and addresses how we deal with each other and work together.

img Develop measurements for meeting the key expectations. Using these measurements, provide feedback on performance to the project staff throughout the life of the project.

img Don't let the expectations or measurements change arbitrarily.

3. Establish standards and procedures for decisions. “Making decisions is one of the project team's most important tasks” Ken noted. “Make sure every team member understands how and when to bring up issues, concerns, and problems. Also:

img Develop procedures that encourage both the client and the project team to bring issues and concerns to the table early.

img Develop a process for dealing with each of these issues and concerns effectively. Define how and when decisions are made.

img Use weekly staff meetings, action item lists, decision lists, responsibility matrices, and other tools to clarify issues and foster decision-making on a timely basis.”

4. Deal early with the tough issues. “We often believe we can solve problems, improve performance, or make up for mistakes in such a way that our client doesn't become aware of the full implications of events that might have a negative impact on the project,” Ken said. “But the greater the distance between the time of the event and the time the client knows about the event, the greater the client's frustration and mistrust.

Nothing sets a person up more than having something turn out just the way it's supposed to be, like falling into a Swiss snowdrift and seeing a big dog come up with a little cask of brandy round its neck.

Claud Cockburn in Printing House Square.

“Including the client in problem analysis and recovery planning provides him with confidence that problems are being addressed, that he can positively impact problems on the project, and that the team is not hiding problems from him.”

5. Provide mechanisms for revisiting key decisions/issues. Ken elaborated, “The project environment often moves fast, with decisions made and implemented to keep pace. But once a decision is made, is the project committed forever to that decision? The obvious answer is 'No.' But how does the project team address issues or decisions that have been settled? It may take significantly longer to make decisions if they're viewed as final—and a slow decision-making process can have a significant impact on the project schedule.”

6. Manage the project around milestones. John remarked, “During the life of a project, a small problem often creates a small delay. Enough small problems delay the end date or slip the schedule to the degree that the project team has to work overtime, make rushed decisions, and add resources to finish the project by the end date. This frantic atmosphere isn't the impression you want the client to remember, but since it's their last impression, it's usually a strong one.”

John's Journal    November 3

I'm developing an understanding of what it means to be “client-focused.” It's NOT a buzzword— but it's also not an easy concept to explain. There are no activities, no work processes _ being client-focused is more like an attitude that is reflected in everything I do on the project. I believe I'm getting better at putting myself in the client's shoes, understanding what the project means to the client's success beyond the project, and how we can help him get there.

The plan we developed for managing client expectations this week is only common sense. It's the way I want to deal with Hal and his team all the time. It means including Hal in the planning of the project and being painfully honest with him when we run into problems.

My job is to make Hal, as well as all clients, a Hero—someone who was wildly successful at managing the project.

“To combat that tendency,” Ken responded, “create a small number of milestones that reflect significant progress toward completing the project. Manage each of these milestones as if it represented the end of the project. Add resources, work overtime, and make all reasonable attempts to meet these project milestones. This spreads the pressure over the life of the project instead of building toward a frenzied finale.”

7. Celebrate milestones with your client. “This I can't stress enough” Ken stated. “Build on your success. Celebrate your progress and include the client in your celebration. This helps the client understand his contribution to that success and provides a balance for the tense times on the project.”

8. Include the client on teams, give him responsibility, and make him a part of the solution. “On too many projects, the client acts merely as overseer, making sure all the rules are followed. But project success depends on the active involvement and contributions of the client” Ken explained. “One way to achieve this involvement is through the client's participation on the team, not just as another person who attends team meetings, but as an active contributor who develops solutions to problems and actively helps implement those solutions. Because project problems are client problems, project success becomes the client's success.”

9. Clarify values. “Understanding the values that are important to the client communicating…your own values…resolving discrepancies between value sets ahead of time. This is the most significant contribution you can make to improving communication on the project” Ken said. “Disagreements based on differences in values are extremely difficult to mediate, because compromise means compromising your values—and that kind of compromise comes at a high price. Understanding differing values and planning up-front how to deal with conflict significantly reduces the potential for insoluble conflicts on the project.”

10. Deal evenly with the client. “The client must know he can trust the information he receives, trust that decisions are made with his best interest in mind, and personally trust the members of the project team” Ken said.

“I couldn't agree more,” John nodded. “Opportunities to take advantage of the client always present themselves, but although these may realize a short-term benefit, a breach of trust, more than any other single act, gives the client a negative view of the project.”

BY THE TIME THEY WENT HOME that evening, John had more fully developed his list of 10 principles for dealing with the client. He planned to pull the staff together for an informal work session so they could discuss and improve on these principles. He knew that it would be tough to engage the staff in this type of discussion, but by the time the meeting was over, the team members would know how they contributed to the client's expectations of project success. ∎

 

Russell W. Darnall is employed by Fluor Daniel as part of their South Latin America Region Management Team. His foundation in quality developed during a two-year assignment at Fluor Daniel's Continuous Performance Improvement Resource Center, a global research and support center for Total Quality Management.

PM Network • June 1997

Like what you just read?

Log in or register for a free PMI account to get access 
to even more articles like this one.

Offer from our training partner

Advertisement

Offer from our training partner

Advertisement

Offer from our training partner

Advertisement