Post-Launch Tasks = Project Overhang

by Joanna Pineda Posted on August 20, 2009

Man climbing rock overhang After each Web site launch, I ask the Project Manager in charge what’s left to do. Why?  Because inevitably, there are items that didn’t make the launch. I call this Project Overhang and it can be deadly to a firm’s profitability and productivity.

Project Overhang is what we call tasks that are left over from a project. The project, site or application can be up, tested and launched, but there are tweaks we didn’t complete, post-launch fixes or small change orders.  Often, Project Overhang does not generate additional revenue and the items are so small that they can slip off our radar if we’re not careful.  Project Overhang is much less likely to happen on a client account because those projects are external, revenue-generating and discussed during post launch check-ins.  But Project Overhang on internal projects can linger for years!  I once had a to do item to update a new staff orientation guide that didn’t get done for two years!

Which is why I’m trying hard to make sure we have no overhang from our recent office move.  We moved 2 1/2 weeks ago, we’re up, we’re running and nearly every box is unpacked.  Notice I said “nearly” every box.  It’s the last few boxes that take forever to unpack.  I have two boxes at home from a move back in 2001 that are still waiting to be unpacked.  So back at the office, we are continuing our SCRUM process to get all move-related items done by the end of the month.  In fact, by Friday, I plan to have my office “done,” all prints hung on the walls, and all boxes in the kitchen and supply room put away.  The remaining Project Overhang will be to unpack the CTO’s office, but that will be the topic of another blog post. 🙂

My tips for dealing with Project Overhang are:

How about you?  Do you have overhang at work or at home?  What’s your most ridiculous overhang item?  What are you doing to clear out the overhang?

Related Articles