Ideally we glide through our projects with happy customers and arrive at deployment ready to shake hands and say goodbye…all on good terms. Reality, though, is often something altogether different. I'd like to say I never experience customer frustrations on any of my projects, but the truth is I've experienced some degree of customer frustration on nearly every project at some point during the process. It may be a big issue or it may be something miniscule, but at some point it usually happens.
Customer frustrations can arise from any one of a number of things. From unanticipated change orders, to error-filled deliverables, to rude project team members, to project budget issues, to just conflicting personalities.
Anything – literally – can set it off and it may not be a showstopper, but it should be addressed. The potential issues can be endless – so I definitely can't address all the possibilities here. But we can discuss a few possible proactive or responsive measures we can take to try to alleviate customer frustrations if we sense that things aren't going as well as hoped…at least from the customer's point of view….
Step up communication practices
Effective, efficient, and timely communication remains, in my mind, the number one responsibility of the project manager. All task assignments, all feedback, all customer interaction, all issues resolution, and all collaboration in general, begins and ends with good communication.
In fact, with more than 50% of all projects failing, one survey showed that project managers cite 'poor communication' as the second biggest contributor to project failure – right behind 'bad or incomplete requirements.'
If a failure point at the beginning of the project was to skip the creation of a project communications plan and now you're seeing communication breakdown, it may be the right time to go back and create the plan so everyone has the same communication expectations going forward for the rest of the project.
Revisit weak areas
There may be weak areas of the project that are causing the customer concern like how risk is being handled or possibly the delivery of error-prone deliverables. Revisit those weak areas and add more effort where needed.
For example, begin reviewing risk topics and issues regularly on a weekly basis as part of the weekly status call or meeting with the customer. If deliverables have been a problem area, incorporate peer reviews on every future deliverable. Having the entire team review every deliverable will greatly reduce the likelihood of presenting the customer with a document or deliverable with issues or errors.
React to team member concerns
If the customer is frustrated with someone on the team, meet with the customer to find out why, meet with the team member to work out some corrective action, and then jointly meet with the customer to discuss.
Personnel issues rarely work themselves out on their own and if there is friction between the customer and one of your team members it may not even be obvious to your team member. Bring it to the forefront and take the necessary corrective action BEFORE your customer has to request a replacement. If you let it get to that point, then your leadership will definitely be called into question as well.
Circle back
If necessary, go back to the kickoff presentation and notes to analyze where you are vs. where you should be in terms of process and promises and assumptions. It's never too late to try to get the project back on track and make the customer feel comfortable again.
It's possible that you discussed processes, actions and policies that would be implemented or followed and they never happened or were never implemented. If that is the case, it may be frustration point for the customer to see that it was an expectation that was never fulfilled. Often the customer sees it as something they paid for but never received.
Call for input
Customer satisfaction is one of the three key indicators of project success, so responding to and resolving customer frustration should always be a top priority. When you've experienced customer frustration, how have you responded? What actions have you taken to resolve these issues? What general approaches have worked the best for you? Thanks – we'd love to see your feedback!
Brad Egeland has 25 years of high-level, professional IT and Business Management experience, including 19+ years of enterprise Project Management experience. He has developed and implemented systems for start-ups and their customers as well as $100 million long-term contracts. His experience is in the industries of Manufacturing, Aviation/Airlines, Gaming, Government Contracting, Retail Operations, Pharmaceutical, Start-ups, Healthcare, Higher Education, Non-profit, High-Tech, Engineering and general IT. Brad is a father of nine and lives in Las Vegas, Nevada. You can visit Brad's professional website at www.bradegeland.com.
Gone are the days of the once-stuffy office space with stacks of files filling up your in and outboxes. Technology has brought an entirely new look to today’s modern office. Below, I’ve outlined three trends that I think greatly innovate our workplaces and define what they look like in the sleek modern era.
Keeping the project budget in line is one of the most difficult things that a project manager does – and yet it is a huge factor in determining the overall success of the project when the engagement winds down.
Dave Anderson, Director of Sales & Marketing in UK2 Group, a
In our new podcast, we discuss this issue with Matt Bullock, a COO at
Also, as we promised, we did a drawing of 10 funny, yet useful, prizes (including the awesome grassy lawn charging station that we basically fell in love with ourselves!) among everyone who took part in the survey.

So what’s the bottom line? Terri Griffith from GigaOm has perfectly
"Complexity can be managed, work can be shared, and transparency supported — all at blazing speed." [in Wrike]
No matter if the person mentioned after @ follows the task or not, she or he will immediately receive an email notification with the text of your comment. Imagine how handy the feature is when you need a piece of advice from a teammate who is not directly involved in the task! For example, if you work on your company's branded YouTube channel, you may need to know if the design mock-up you created is technically viable, so you mention your DHTML developer in the comment. Or when you need to ensure the sales proposal you created aligns with your team's goals, you mention the appropriate executive. There are so many cases when the feature is very handy, including the ones when you need to involve overly busy teammates into the discussion.


