Project Killers: Lions and Tigers and Bears Oh my!

OZYou’ve just discovered yourself surrounded by Witches and Munchkins in Munchkin land and you desperately want to get back to Kansas.  You’ve heard that the Wizard of Oz in Emerald City can help you get back, but how do you find the Wizard?  Just follow the Yellow Brick Road!

Do you see the similarities to your CRM project?   In Munchkin land Dorothy had a clear goal, return to Kansas with the help of the Wizard of Oz.  Your CRM project has a clear goal; help grow your profits by delighting your customers.  The path from Munchkin land to the Wizard is the Yellow Brick Road.  Your path to delighting your customers is your project statement of work.  Just as Dorothy gathered helpers on her journey to Oz, you will assemble a project team to assist you in getting to Deployment.   Finally, just like Dorothy you start off confidently down the road.

If you have watched the 1939 classic movie the Wizard of Oz, you should remember that the Yellow Brick Road was a path filled with risks to the journey – or as the Strawman and Tin Woodman stated – Lions, and Tigers and Bears.  There were also belligerent fruit trees, wicked witches, and deadly poppies along the way.  Dorothy hadn’t planned for any of these risks and would have been stopped ‘dead’ in her tracks if not for the help of her companions and finally the intervention of Glinda the good witch.

Your project path is a lot like the Yellow Brick Road.  yellow brick roadWhat are the lions, and tigers, and bears you will face?  Where are the belligerent fruit trees and deadly poppies?  Who are the ‘bad witches’ and what risks do they introduce?  Every project faces at least one risk to successful completion.  Most of the time, there are myriad risks to successful completion.  If these risks are not identified and/or not mitigated, they become impacts.  Impacts cost the project time, money, and scope.  In the most severe form, they kill the project before any benefit can be realized!

Dorothy ran head long into her risks and impacts, and unless you have a ‘Glinda’ protecting you, we don’t recommend that approach.  Instead create a detailed project plan using a tool such as MS Project that can point out some of the most common risks faced by a CRM project.  Here are the top 10 risks as identified by online-crm.com:

  1. Invalid project assumptions (different expectations among stakeholders)
  2. Project planning omissions. Significant delays incurred not because project planning tasks were underestimated but because project tasks were completely omitted (forgotten)
  3. Data conversion delay. Unanticipated data scrubbing due to poor data quality
  4. Lack of continuity or consistency of business processes among multiple locations (as well as the introduction of sub-optimization by some locations)
  5. Failure to proactively anticipate and mitigate user adoption challenges – fear of change, sub-optimization and/or sacred cows. Closely aligned with failure to recognize the change in cultural due to a CRM implementation
  6. Missing or infrequent active and visible executive sponsorship
  7. Project is perceived by users as optional; CRM software failure is an option
  8. Failure to backfill project team schedules/workloads
  9. Failure to recognize weak (basic PC operation) user skills assessment prior to training
  10. Failure of Risk Management and proactive risk mitigation

Interesting to note that one of the top 10 risks to any CRM project is the lack of proactive risk mitigation!  Your job as a project manager is to identify these above risks (and all others) well in advance of running into them, determine the potential each has for becoming an ‘impact’ to the project, determine whether or not to accept or mitigate the risk, and establish a risk mitigation plan for each risk that you have identified should be mitigated.  Those mitigation plans should have tasks, resources, and due dates that are tracked on your project plan with strict adherence.  Each risk that is not mitigated becomes an ‘impact’, you will have to deal with impacts to the project, but by the time you are dealing with them the project has been delayed, made more costly, reduced in scope, or all 3.  If you don’t have more time or don’t have more money, and Glinda doesn’t come to your rescue, your project has just come to the end of the Yellow Brick Road with the gleaming Emerald City far in the distance.

Jim Lindenfeld, Principal Consultant

Jim Lindenfeld, Principal Consultant

This blog was written by Jim Lindenfeld, who has been actively involved in customer relationship management during his entire professional career.  He is a certified sales and sales management trainer.  He has been involved in the implementation of CRM systems since 1987 and is currently a principal consultant in our CRM practice.

Project Killers: Does X Mark the Spot?

X Marks the SpotProject Killers are waiting to pounce on every project – from inception to transition.  In this series we are looking at the most common assassins and exploring the ways to preserve the health and well-being of your projects.  The most heinous killers are:

 

  1. Dead on Arrival (a.k.a. DOA) – A project without the proper estimations for time and resources somehow is initiated. (The Path to On Time, On Budget and In Scope : http://blog.evergegroup.com/?p=1385)
  2. Death by Documentation (a.k.a. Strangled in Red Tape) – A great deal of time and effort goes into plans, requirement documents, and design documents with no real benefit to the project. (Project Killers: An Ode to Death by Documentation: http://blog.evergegroup.com/?p=1389)
  3. Death by Indecision (a.k.a. Analysis Paralysis in its milder forms) – Key project decisions are delayed or avoided altogether. (Project Killers – PSI – Project Scene Investigation “A Case of Slow Death” http://blog.evergegroup.com/?p=1400)
  4. Death in Unchartered Lands (a.k.a. Scope Creep) – The participants, stakeholders, scope, and methods, are never agreed to formally when the project starts. If you don’t know where you’re going, most any road will take you there – but it may take a lot longer and cost a lot more!
  5. Sudden Unplanned Death (a.k.a. Running into a dead end) – risks are not properly identified and mitigated
  6. Death by Starvation (a.k.a. Bottlenecks) – resources are not properly identified and allocated.

We have already dealt with DOA, Strangulation by Red Tape, and Analysis Paralysis in previous blogs.  This blog deals with Scope Creep, enemy number One and the most hated project killer of all time.

Imagine that you make your living by looking for and recovering treasure.  It shouldn’t take much imagination, because that is exactly what you are doing as a project manager, but let’s carry out the analogy to show the congruence.  First, as a professional you wouldn’t chase a treasure that was known to be too small or too costly to obtain.  Second, you would have a ‘map’, literal or figurative, that has a definitive ‘X’ that marks the spot where the treasure can be found.  Third, you would obtain the permissions and licenses needed to hunt for the treasure.  Fourth you gather your investors to fund the trip.  Fifth, you would assemble your treasure hunting team.  Sixth, you would plan your treasure hunting trip.  Finally, you would hunt for and recover the treasure.

It is easy to see the analogy, an IT project is a lot like a treasure hunt.  You initiate the project to benefit (the treasure) your organization.  You have an estimate and a statement of work (the map).  You license the software.  You identify the business stakeholders and obtain the funding.  You put together the project team.  You write up a plan to obtain your objectives.  Finally, you carry out the project and obtain the desired result.  Or do you??

Do you instead ‘get greedy’?  A new map has been found, lying close to your original treasure is another one.  It is temptingly close by and by extending your trip, and pushing your resources to the limit, that treasure can be had!  X no longer marks the spot.  Your careful plans and preparation are no longer going to assure you of finding the treasure you seek, because you now seek more than you had originally planned to.  You have literally released the ‘bird in your hand’ to seek ‘two in the bush’.

When this happens to your IT project, when you reach out for that nearby benefit, you have exposed the heart of your project to the most deadly and feared project killer, Scope Creep.  Yes, there may be more benefit to be had, and yes, it may be reachable by running the project longer and pushing the team to the limits.  However, you must realize your carefully created plans and preparation are no longer going to assure you of a successful project.  Prior to giving up on your original ‘treasure’ in favor of a new, expanded one, you should think of the professional treasure hunters.  What would they do?

The truly successful, professional treasure hunters stay focused on the prize to the exclusion of all potential distractions, they also draw up a charter and make every member of the team commit to that charter, and finally they set up the reward system for the team members in such a way that they are only rewarded for the treasure they are chartered to find.  Do the same for your projects and you will find that X indeed marks the spot much more often than not!

Jim Lindenfeld, Principal Consultant

Jim Lindenfeld, Principal Consultant

This blog was written by Jim Lindenfeld, who has been actively involved in customer relationship management during his entire professional career.  He is a certified sales and sales management trainer.  He has been involved in the implementation of CRM systems since 1987 and is currently a principal consultant in our CRM practice.

Illustration created and provided by Jonathan Pike, eVerge Group IT Specialist.