Post-Project Customer Evaluations and Implementation Reviews

UPI Study › Courses › Project Management › Free lessons › Lesson 10.4 Free with a free account

Post-Project Customer Evaluations and Implementation Reviews

Project Management · Chapter 10: Project Closure and Post-Completion ReviewSection 10.4 · lesson 66 of 7312 min · free with a free account

← Cost Variance: Definition, Calculation, and InterpretationNext lesson: Defining Goals and Objectives for Project Teams →

Earn 3 college credits for Project ManagementRecommended for credit by NCCRS · Business 230 · self-paced · one payment, lifetime access

In this lesson

Gather customer feedback and test realized benefits against the business case.

  • Compare surveys, interviews, feedback forms and structured debriefs for customer evaluation
  • Write specific, neutral, single-issue evaluation questions and name response problems
  • Rate each business case benefit as met, partly met or not yet visible from evidence
  • Report shortfalls by cause rather than blame and route findings to those who can act

Free study notes

Get this lesson's notes by email

The key points and 4 practice questions with answers, in your inbox. One email, free.

One email. Unsubscribe in one click.

Transcript

Everything said in the video, section by section (1,581 words). Read along, or search it.

Opening Question

Satisfied Customer, Unproven Benefits

Four months after the Riverside clinic opened, Priya is back in its lobby. Helen has asked her to run the post-implementation review. The figures are made up. Grace, the clinic manager, says the new scheduling system is satisfactory. In a short evaluation, her front-desk staff rated it four out of five for ease of use. So, did Riverside deliver what its business case promised? A happy customer and a delivered benefit are different questions.

Why Look Later

Feedback and Benefits Arrive After Closure

Closure ends the work, but not what can be known about it. Two kinds of information arrive only later. The customer's view, once they've lived with the result. And the realized benefits, the improvements the business case promised, which show up only after the result has been in use long enough to change the work. A project can pass acceptance, meet its cost result, and produce an excellent closure report, and still not deliver what the organization wanted. Two activities look for that gap: the customer evaluation, which collects the customer's judgment, and the post-implementation review, which compares realized results with the business case.

Evaluation Methods

Surveys, Interviews, Forms and Debriefs

A customer evaluation is a structured collection of the customer's judgment of the delivery, and of working with the team. Four methods are common. A survey: the same questions sent to many people. It's cheap and comparable, but can't follow up an unexpected answer. An interview: one person, prepared questions. It's deep, but slow, and the few views heard may not be typical. A feedback form, filled in at a natural moment like handover, catches views while fresh, but answers are short. A structured debrief, a facilitated meeting, lets disagreements surface, but confident voices can dominate. Each misses something the others find, so a short survey plus a few interviews usually reveals more than either alone.

Question Design

Specific, Neutral, Single-Issue Questions

Answers are only as good as the questions. Be specific: were the appointment reports easy to read, not did the project go well. Be neutral: how helpful was our excellent support team invites praise. How would you describe the support you received doesn't. Ask one thing per question: the speed and quality of training can't be answered if training was fast, but poor. And mix rated items, for comparison, with open items, for reasons nobody thought to ask about. Priya's form has five items: rated questions on communication, on whether the result matches what was agreed, and on training; then two open questions, on what to do differently, and what's still missing.

Quick Check

Spotting a Leading Question

Quick check. A draft question reads: how much did the wonderful new reminder-text service help you? What's wrong with it? Pause, and decide. It leads the respondent. Wonderful tells people the answer you want. It asks only one thing, so it isn't double-barreled. And an open question can be added to the form, but it wouldn't fix the leading word.

Response Problems

Return Rate, Courtesy Bias and Small Samples

Even good questions can mislead, so name four response problems in any report that uses the results. First, a low return rate: responses divided by forms sent. Send a hundred twenty forms, get thirty back, and the return rate is twenty-five percent. The three quarters who stayed silent may think differently. Second, courtesy bias: favorable answers given to be polite, especially face to face. Third, unrepresentative respondents: only the enthusiastic, or only the angry, or managers answering for users they rarely see. Fourth, small numbers. Three satisfied answers out of four is seventy-five percent, but one more answer moves it to eighty, or to sixty. So report the count, not just the percentage. Remedies: keep it short, send a reminder, promise the answers are used to improve and not to blame, and ask the people who actually use the result.

Post-Implementation Review

Testing Results Against the Business Case

The post-implementation review Helen asked for is different. It's a structured examination, some time after handover, of whether the result works in use, and whether the business case's benefits were realized. The evaluation records how the customer feels about the delivery. The review tests results against evidence. Timing: long enough for staff to learn the result and for effects to show up in records, but not so long that the people and papers have dispersed. A few months is typical, or a full cycle when effects are seasonal. Scope: use, support and benefits, without reopening settled matters like contract terms. Participants: users, support staff, the benefit owner, and someone independent of the project team, since people reviewing their own work tend to find it good. The sponsor and the project management office receive the findings.

Review Questions

Use, Support and Realized Benefits

Three groups of review questions recur. Is the result used as intended? Who uses it, how often, and have users found workarounds? A workaround is valuable evidence that something doesn't fit how people work. Are support needs met? How many help requests, about what, whether the support agreed at handover is enough, and whether training covered what users needed. And were the benefits realized? For each one, what changed in the records, and by how much. Each question should be answerable with evidence, like logs, records and observation, not just opinion.

Benefit Status

Comparing Each Benefit With Evidence

The business case listed the benefits that justified Riverside, each with an expected result. The review compares each with evidence, one row per benefit: expected, evidence source, observed, and status. Three statuses are enough. Met: the expected result was reached. Partly met: it improved, but fell short. Not yet visible: the evidence is too limited, or too early, for a fair judgment. Missed appointments were to fall from eight in a hundred to four. The appointment records show four: met. Front-desk time on manual scheduling was to fall from ten hours a week to two. A time sample shows two: met. Staff overtime was to fall from four hundred hours a month to three hundred. But there are only three months of payroll data, taken before flu season. That's not yet visible. The average patient wait was to fall from forty-five minutes to thirty. The check-in log shows thirty-four. The share of planned improvement is forty-five minus thirty-four, over forty-five minus thirty: eleven over fifteen, about seventy-three percent. Partly met.

Quick Check

Measuring a Phone-Queue Improvement

Quick check. Willowbrook's phone-queue time was to fall from twelve minutes to four. The call log now shows six. What share of the planned improvement was achieved, and what's the status? Pause, and decide. Partly met, seventy-five percent. Twelve minus six is six minutes gained. Twelve minus four is eight planned. Six over eight is seventy-five. Fifty percent divides the gain by the starting twelve, not the planned eight. And met would round a shortfall up to success.

Intangible Benefits

Evidence for Benefits Hard to Count

Tangible benefits, like waiting times, error counts or overtime hours, are measured in records, against the starting value. Intangible ones, like confidence, cooperation or reputation, can't be counted directly. Their evidence is indirect: structured interviews, repeated ratings on the same questions, or behavior you can observe. Riverside's business case promised staff would trust the daily schedule. Interviews show most do, but two front-desk staff still keep a private paper backup. Partly met. Intangible evidence is weaker, and the review should say so. But leaving these benefits out because they're hard to measure would misrepresent the project's value.

Reporting Findings

Causes Rather Than Culprits

Report the findings as they are, including benefits not yet visible, and benefits not reached. Three habits help. Tie each statement to its evidence, so readers can check it. Report a benefit that can't yet be judged as exactly that, with the date it will be rechecked, rather than stretching it into a success, or dropping it. And explain a shortfall by what in the process, plan or design allowed it, not by who is at fault. A review that finds a culprit teaches people to hide problems. One that finds a cause teaches the organization something. Wording matters. The training didn't cover urgent walk-ins is a cause that can be fixed. The front desk ignored the system is a judgment that ends the conversation.

Feeding Back

Turning Findings Into Future Changes

Findings matter only if they change something. First, they go to the sponsor and the benefit owners, who can act on shortfalls, with extra training or adjustments. Second, to the project management office, which can spot patterns. If several projects miss the same kind of benefit, the cause may lie in how business cases are written, or benefits measured. Third, into future estimates. If training took twice as long as planned, the next training estimate changes. If a benefit was over-promised, the next one is justified differently.

Case Resolved

Why Waits Stayed at Thirty-Four Minutes

Back to Grace's satisfactory. Priya asks why the wait is thirty-four minutes, not thirty. Interviews show the front desk overrides the system's slots for urgent walk-ins, because training never covered how to enter them. Grace was pleased, and expected a thank-you note. Instead, Priya reports the wait as partly met, overtime as not yet visible, with a recheck after flu season, and the cause as a training gap, not the staff. Helen approves a short refresher course, and the project office adds urgent walk-ins to its training checklist for later projects. So the answer to the opening question: Riverside delivered most, not all, of its promise. A customer can honestly call a result satisfactory, while a benefit stays partly unrealized.

Key Takeaways

Evaluations and Reviews in Brief

To recap: customer satisfaction and realized benefits are different questions, asked at different times. Combine evaluation methods, and write specific, neutral, single-issue questions, rated and open. Name the response problems: return rate, courtesy bias, who answered, and small numbers. Months later, check each benefit against the business case: met, partly met, or not yet visible. And report causes, not culprits, so the findings feed the sponsor, the project office, and future estimates.

About Project Management at UPI Study

Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Why take it here

Why students take Project Management with UPI Study

How projects are planned, run and closedProject Management teaches how to deliver work on time and on budget: scope, schedules, the critical path, budgets and earned value, risk, contracts, monitoring and closing a project, and leading the team. It is a common course in business, management and engineering degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Post-Project Customer Evaluations and Implementation Reviews

What is a post-implementation review in project management?
A post-implementation review is a structured examination, some time after handover, of whether a result works in use and whether the business case benefits were realized. A few months is typical, or a full cycle when effects are seasonal. It includes users, support staff, the benefit owner and someone independent of the project team, and its findings go to the sponsor and project management office.
How do you write good questions for a customer evaluation after a project?
Make each question specific, neutral and about one thing. Ask whether appointment reports were easy to read rather than whether the project went well, avoid praising words that invite agreement, and split double-barreled items such as the speed and quality of training. Mix rated items for comparison with open items that capture reasons nobody thought to ask about.
How do you measure the share of a planned benefit that was achieved?
Divide the improvement achieved by the improvement planned, both measured from the starting value. If patient wait was to fall from 45 minutes to 30 and fell to 34, the share is 11 over 15, about 73%, so the benefit is partly met. Dividing the gain by the starting value instead of the planned improvement is a common error.
What is courtesy bias in project feedback?
Courtesy bias is the tendency to give favorable answers to be polite, especially face to face. It is one of four response problems to name when reporting evaluation results, along with a low return rate, unrepresentative respondents and small numbers. Remedies include short forms, reminders, assurance that answers are used to improve rather than to blame, and asking the people who actually use the result.

About the Project Management course

How many college credits is Project Management?
Project Management (Business 230) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Project Management cost and what is included?
$250, paid once, with lifetime access: all 73 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Project Management take?
It is self-paced with no deadlines. The 73 lessons total about 15 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Project Management.

73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Project Management
3 credits · NCCRS
Enroll →