Close this search box.

When is the Project Done vs. Done-Done


What’s interesting, humorous or even sad, is an integrator’s ability to say when a project is done and when it is done-done.

The project closure process can happen many ways. Some project closures are positive, but many are negative. Last week, we discussed the processes integrators can put in place to prevent sloppy closures from happening.

A disciplined application of these processes is required for success, which seems straightforward enough. However, over half the time we still see project closures rife with incomplete deliverables, dropped hand-offs, and damaged client relationships.

What does a negative project closure cost an AV integrator?

That is the topic of this week’s video with Brad Malone.

“I’ve taught project management around the world and typically you work until the project is done, completed and correct,” says Malone. “What I find in the AV industry is that there’s done and then there’s done-done.”

“When I ask integrators what that means, they say, ‘Well, done is when we’re done enough to leave the job site without totally irritating the client. Done-done is the time, the effort that it takes to go back and fix it.’”

“Then I ask, ‘What do you lose in that?’”

“They usually say, ‘Well, we lose profit; we lose our reputation, and we kind of lose our morale.’”

“Then I ask, ‘Why do you do that?’”

“More often than not, they reply, ‘That’s just the way we do it in this industry.’”

I’d just like each of you to begin thinking about what does that cost your company in terms of all those factors, morale, quality, reputation, drama and chaos? Because going back and fixing the one project now causes that cycle to hit the next project.

Doing it correctly the first time would tremendously solve this dilemma or problem of done and done-done.

Watch the video below:

Related article: Creating Project Managers the Right Way

Featured Content

Handpicked Related Content

No data was found