PPM Implementation Key Success Factors
by Jackie Golden

VP of Global Solutions - Solution Implementations have been my passion for the last 15 years. I will be sharing some of my recommendations on practical ways for getting work done and projects completed on time and on budget. No matter the industry or functional group, everyone needs to deliver on goals and objectives on an on-going basis that contribute to their success.

Top 10 User Adoption Techniques for Work Management Solutions

In working with customers over the last few quarters around this transitional idea of going from traditional Project Management to Work Management, the main questions they ask me are, "How will this help improve my user adoption and involvement in delivering successful projects?" and "How is the idea of Work Management different?"
college
It reminded me of the questions my kids asked me when they were going from high school to college. They were anxious about how hard the courses were going to be and would they be able to perform at the same level as high school. We had a rule in my house, that they brought home As and Bs in exchange for their freedom, some money in their pocket, and keys to a car; otherwise, they were subjected to the Golden Prison House. So needless to say, the same rule applied for college. So I explained to them the difference was as simple as this: In high school the teacher’s organize your work for you, give you a list of tasks to do, check up on you, ask you for a status, and expect you to deliver on the curriculum they give you. In college, the professor will give you a course outline and curriculum with expected assignments and grading measurements. After that, they generally don’t help you, organize you, or monitor you; they just expect you to deliver on the curriculum any way you feel is best for you to deliver the highest quality work. They might give you some structure to work within, but don’t limit you to how, who, or what you use to deliver the results.

This is the difference between Project Management and Work Management in how you involve your people and get them to share in the responsibility of delivering the work required on a project, program, or initiative in any organization. You give them the structure, the framework to work within, and then provide them the freedom and ability to get the work done in the best way possible. It can lead to great strides in innovations at the ground level. It encourages the team members to get the work done more efficiently by improving processes and doing it the way they think will be easier and more effective. You then will have a higher quality of information about what is going on in your organization and can gather better intelligence from your teams and really understand what changes need to be made to deliver better, quicker, and more innovatively.

With that introduction, here are my top 10 techniques for getting high User Adoption within a Work Management Solution:
10.  Evangelize the message of allowing people to get the work done in the best way. You need to market to the teams involved why a Work Management solution will make it easy to manage processes, work, and projects.
9.  Show them how easy it will be to provide you with the updates on the tasks, time lines, and amounts of work involved. Let them know that this will allow them to tell you how, when, and who will be best in getting this done.
8.  Take time to understand a day in their life and provide them with an easy to use solution for collaborating with their peers/teams/cross departments. Show them how they will do what they do today easily using a Work Management solution.
7.  Make sure the solution makes it easy for them to see all of their requests and prioritize them.
6.  Show them how easy it is for them to add their own task lists outside of tasks assigned or requested of them. This way they can review all the work, structured and unstructured in one place.
5.  Make sure the solution allows for a calendar view of all their work commitments, so they can quickly glance at their calendar and see how they are going to tackle their day.
4.  Allow for them to see what their team members are working on and provide information and content to help them work more effectively as a team.
3.  Allow team leads/managers to announce (on-line in the Work Management solution) an incentive associated for the team to hit an aggressive deadline and provide progress updates that the entire team can view in real time.
2.  Create an easy feedback loop for everyone to provide suggestions on improvements in the processes and projects they are involved in that can be incorporated in real time.
1.  Give everyone at your company an "Easy Button".  An easy to use, robust, collaborative Work Management solution (SaaS version is best). Give them a link and watch them get it done.

I run my entire Services Organization (Education, Consulting, and Customer Support) on a Work Management solution and have been for the last year.  With every employee on the system, we were able to deliver an amazing amount of progress in the last year including development in the maturity of the organization, services we provide, and quality of delivery. The organization grew revenue by over 78% and margins by 300%.

I’m telling you, it’s the next technology solution to creating a competitive edge.

As always, I welcome your comments and encourage you to share your experiences.

0 Comments »

Is there ROI in using a Services Program to support a Software Implementation?

In any software selection process there is always the point in the sales cycle in which you evaluate the need to purchase a services program to support the implementation of the solution you are purchasing.  It is also the area that most companies negotiate the highest discounts or cutbacks in the overall cost of the solution.  Why? Is it worth it?  Should you do it on your own to save money?  Is there really value in spending 1:1 in dollars (Software $ to Services $) to bring the solution into production?

 

Let me share my first experience in implementing an Enterprise Financial reporting system for a publisher in which we wanted to save money so we decided to send a few of my team members to training and then do the design and implementation on our own.  They came back from training excited about the project ahead.  Then we sat in front our computers with the solution up, trying to figure out the best way to start.  We knew what we wanted for our end results but weren’t sure how to design and configure the solution to get us there.  So we started with the "Hunt and Peck" method to navigate our way through screens and started just setting up various areas that we thought made sense.  Then loaded some data and created our first reports and waited with excitement to see the results.  Up comes this report with all kinds of data, we were thrilled.  Then started looking at the data to verify the results and realized we had complete garbage.  We went at this for 3  months in our "Trial and Error" mode, before we finally asked for some consulting assistance, then signed up for a more comprehensive support package to help us long term as well.  Literally within 3 weeks of the consultant working with us, we redesigned and configured the solution to meet all of our success criteria.  Here’s the Cost Savings breakdown:

Started on Own Labor Costs Lost Time
Resources    
  3 FTE for 3 months $18,000 2 months
Consultant $20,800  
Total Costs $38,800  
     
If Used Consulting from Start    
Resources    
  3 FTE for 1 month $6,000 0
Consultant $20,800  
Total Costs $26,800  
     
Savings $12,000  

This was for only one small group and we were rolling this out world wide.  The larger the implementation and the more team members involved, the higher the savings in resource utilizations and company labor costs associated with putting solutions into production.

I have spent the first half of my career working for corporations implementing just about every solution in an architecture, from ERP systems to reporting including data warehousing and integration solutions.  I spent the second half of my career working for the software companies implemeting the solutions for all the corporations.  I have been on both sides of the table.
My conclusions are that the majority of the time the implementations go into production with a higher quality, closer to target and much faster when using a services program. A services program can include any or all of the following: 

  1. Consulting
  2. Education
  3. Customer Support

Some vendors offer packaged solutions with deeper discounts for prepaids and others are custom designed to meet your needs. The following table shows the differences in implementing "On Your Own" versus purchasing a "Services Program": (Based on the averages of several customer databases for various software solutions from 2002 to 2010)

  On Your Own Services Program
Costs Lower Higher
Knowledge Transfer 30% Average 60% average
Timeframe 2-3 times longer within 30 days of plan
Quality Design Fair Good
Meets Success Criteria 50% 85%
Delivery On Time 30% 75%
Delivery On Budget 60% 85%
Configuration Simple Complex
Customizations Low/Difficult Higher/Offer support
Simple Reporting 100% 100%
Complex Reporting 50% 95%
Methodology None Proven Methods/Approach
Reusability Med High

When thinking about whether "To Buy Services" or "Do it Own Your Own", I recommend that you purchase a services program.  If you define your key success criteria up front, you can design a services program that delivers what you need for a good budget price point and get you into production in much shorter time period.  To be able to tell your key sponsor or stakeholder that you were able to deliver the results within a planned timeframe and budget will be a great career booster.

0 Comments »

The Top 10 Success Factors to PPM Software Implementations

In sharing secrets to success, we always want to get to the bottom line quickly.  In other words, where is the BIG RED EASY BUTTON.  Truth is that there are no real short cuts.  It’s like my grandma used to always say "Life seems to be getting so complicated.  It seems so much harder to do things faster to end up with nothing of value."  Simple words of wisdom from a 90 year old, yet so true.

I wanted to find a way to simplify the key factors that are consistent across all the projects that are successful and provide real value to the organization.  I put this together at a User Conference recently and it was such a hit that I thought I would share it with all of you.  I call it my TOP 10 LIST

However, first we have to start with the following top 10 list:

The Top 10 Things NOT to do as a Project Manager:

    10.  Develop your project plan on a napkin while "Out on The Town".

     9.  Use the 12 step program from your local gym as your methodology.

     8.  Setup Project Structure as "Ready,  1..2..3..  GO TEAM".

     7.  Resolve project issues through nightly discussion with your spouse or friend.

     6.  Review Status Report by asking everyone:  "Soooooooo,  How’s it going?".

     5.  Test the system using the nightly janitorial staff as the only available resources.

     4.  Use the Customer Support team to educate your staff by logging 1000 "How to" calls.

     3.  Complete Knowledge Transfer with a voice message to the team:  "So Ya’ll got it now, huh?"

     2.  Setup Executive Monthly reviews as dinner at Ruth Chris Steakhouse.  Opening line will be "  Project Successes are like your steak tonight, very rare."

     1.  When ready to Go-Live:  Send out an email to all the end users:
"Get in, sit down, buckle up…. It’s going to be one hell of a ride."

Now that you are all hopefully laughing, or at least smiling, because you recognize something familiar on the list, I will share the real Top 10 Key Success Factors:
     


/* Style Definitions */ table.MsoNormalTable {mso-style-name:”Table Normal”; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:”"; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:”Times New Roman”; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin;}

1.     Develop a Success Plan

2.     Execute on Recommended Methodology of the PPM solution you are implementing.  Don’t skip steps.

3.     Utilize qualified and experience resources to get it done quicker, better, faster.

4.     Setup a solid Project Management Structure – Team meetings, Issue Management processes, change controls and documentation sharing.

5.     Develop an effective Communication plan.

6.     Execute thoroughly on the Test plan.  Allow for adequate test time and issue resolution.

7.     Follow recommended Education plan.

8.     Engage with Consulting in a mentorship program that ensures knowledge transfer to the core team.

9.     Develop a partnership relationship with team and PPM vendor services team.

10. Inform the Executive Sponsor of on-going status and successes.  Use them to break down barriers as well as excite them with the accomplishments.

I welcome your comments on this topic.  I enjoy hearing about the things that others find helpful in driving success during their implementations.

2 Comments »

Can I buy an insurance policy for my PPM Implementation?

Wouldn’t it be great if we could purchase an insurance policy that would give us back all the time, money and resources spent if we had a failed PPM implementation? or We could look at it in a different way.  Create your own insurance policy for your PPM project implementation. 

My Step-dad always believed in having the right insurance policies.  As a skunk-works test pilot for Lockheed Martin for 30 years, he believed you had to always be ready for the worst.  He was the original pilot on the SR-71, the first stealth plane. 

He shared a story with me  about the one and only time that he ejected from a plane during a test flight, which was not one of the SR-71s, but another type of plane.  He first explained that test pilots are very well trained to do everything they can to save the plane and land safely.  So they go into every test with a readiness for all the things that can go wrong.  He then shared that most of his flights have something that does goes wrong, but he has always managed to land the plane safely even in some of the most unusual circumstances and places.  So in this particular flight when things started to go wrong, he went through all the options for trying to keep the plane in flight.  He stuck it out as long as he could, doing all the right things to compensate for anything that might go wrong.  However, in this case, it wasn’t enough, and he ejected just in time to save his life. 

In retrospect, over a 30 year period with thousands of hours of flight time, he was able to complete all his test flights successfully with only the one failure.  I would say that’s a pretty good track record.  He believed his success was due to the insurance policy they created within Lockheed which was their preparation and readiness processes, along with the procedures and education that allowed them to do all they could do to make every flight a success.

It made me realize that this is what a Professional Services program offers to customers to support their implementations.  In utilizing the right services programs that include consulting, education and customer support that follows a proven methodology and approach; a customer has just purchased their PPM insurance policy. 

A PPM services program that offers a road-map following a proven methodology, delivers the following:

  1. A comprehensive education program to transfer product knowledge based on roles
  2. A consulting services program to ensure the right application design is deployed rapidly with accuracy while mentoring the customer to support the product knowledge transfer
  3. A Flexible customer support program to meet the growing needs of an organization that continues to ensure their success and utilization of the PPM solution

The above represents a full coverage PPM insurance policy.

Projects are setup to fail when customers try to reduce costs when purchasing PPM by cutting out the use of services that offer the proven programs and expertise which provide a rapid return on their investment.  I’m still a believer in "Pay me now or Pay me later", but one way or the other, every customer returns after a project failure looking for a miracle cure.  Although a professional services organization doesn’t offer a big red button to push to make it all instantly better, they do offer insurance programs that can get you back on track.

Invest in a services program, it will be well worth the return you receive when you get more value and productivity from your PPM solution in a shorter period of time and higher user adoption, then attempting it on your own.

1 Comment »

Project Success Plan Series – Last Segment – Achievable Timeline

I have previously shared my formula for a Success Plan which is:

Success Plan = Realistic Scope + right skilled resources + achievable timeline

I believe developing a realistic scope and applying the right skilled resources are part of the secret sauce to ensuring successful implementation.  In this discussion, we will explore various considerations in determining an achievable timeline.

I love the story of one of my customers recently shared with me.  They were attempting a worldwide CPM (Corporate Performance Management) implementation and roll out that they estimated to take over 18 months.  This was going to include full functionality support of all their current processes, collaboration, and reporting requirements.  During the design session, it was discovered that there were vast differences worldwide with their standard practices.  Those differences required some internal consideration in their system design and internal processes to achieve their long-term goals of having worldwide visibility of the information.  As a result, they considered putting the entire project on hold.  Fortunately, one of the their very timid team members asked the question, "Is a full worldwide roll-out the only option, or could we focus on North America—which we could implement in the next four months pretty easily and then bring on the other entities one at a time?"

This is a great example of everything we have discussed in this series.  Every project has an opportunity to succeed if we can start with what we know we can make happen and prove the impact to the organization in a controlled manner.  The best part of this example is taking the timeline from 18 months to 4 months.  The timeline is one of the most important elements in creating a successful and achievable project plan.

One of the most common statements customers make to me during a Discover or Scoping session is, "I have to have this project live in 30 days."  My response is, "Let’s talk about what you need to accomplish in this project in order for the project sponsors to deem the project a success.  What needs to be delivered?"  Notoriously, they go into a dissertation on everything that has to be included in the project, which becomes a scope definition that cannot realistically be completed in 30 days.

To achieve a proper Success Plan, I recommend the following steps:

  1. Define the project goals and objectives. 
  2. Define the detailed tasks required along each stage of the implementation methodology. 
  3. Review the tasks with the entire resource team that is assigned to the project and apply realistic durations to each tasks.  Look at the calendar and take into consideration holidays, company events, PTO and other assignments. 
  4. This "first pass" should allow for some slack time along the way to take project risks into consideration as well. 

What happens if the project timeline comes out way off of the expected plan?  I recommend the next set of steps:

  1. Once you have a well thought out plan, you can begin working backwards.  If you intended the plan to be complete by June 30th and the plan shows August 30th, then do a second run through on the details and see if you created unnecessary slack or over estimated some task durations. 
  2. The other option is to look at whether you can complete tasks in parallel and utilize multiple resources in order to get more work done in a shorter period of time.  This can condense your timeline tremendously. 
  3. Once you have gone through these processes if your timeline is still not where you want it to be, in this case, an end date of June 30th;  you have only two options:
a. You present your case to management that this is the best plan with the right scope, resources and realistic timeline and they should consider a new deadline date.
b)  Reduce your scope in order to maintain a realistic timeline that you are confident you can deliver on. 
I hope this series on a best practice approach to creating a customer success plan has been helpful.  The planning stage of any project is critical to success.  I would welcome any additional best practices you have determined are important to project success.

0 Comments »

Project Success Plan Series – Continued – Focus on the Right Resources

In my two previous discussions, I was sharing my formula for a Success Plan which is:

Success Plan = Realistic Scope + right skilled resources + achievable timeline

I talked about how to design a realistic scope in my last blog and will continue to go into details on each element of the formula.  In this discussion, I want to walk through some lessons learned from my customers on the importance of applying the right skilled resources to any project.

I love the enthusiasm that exudes from the project team in the first 30 days of any project.  I call this the "Honeymoon period."  We all remember the first 30 days of any relationship or marriage where everyone is all smiles, enthusiastic, positive, and ready to tackle the world.

It is in this period that many mistakes can be made that take a project down the wrong track, including the assignment of resources to the project.

This is one topic I am quite blunt on with my customers.  Once the project scope is defined, it is important to access all the skills required to execute on the tasks to meet the goals and success criteria of the project.  In many cases, my customers have already assigned resources without doing this step.  If that is the case, I recommend that the PM and key Project Sponsors review the skillset of the team assigned to what is required and identify the gaps.  Any major gaps identified is considered a risk to the project.  This would require action from the PM and Project Sponsors to evaluate other resources with the right skillsets and their availability to be assigned to the project.  This may require having upper management discussions for utilizing resources across functions.  If you have a solid business case and value proposition on how this project will effect the company as whole, you will be well armed to pursuade these other functional areas to support you.  Especially if you can restate the value in terms of "what’s in it for them."

The number one concern that my customers raise on this topic is that they don’t have the right resources in house to meet the requirements, even across functional areas.  My recommendation is to begin evaluating an outsource solution.  There are many companies that specialize in various areas of expertise depending on where the skillset gaps are. This could be either industry or best practices knowledge to IT-specific requirements and skillsets.  The key is to spend the time doing the due diligence to understand your options and cost alternatives to those options in order to ensure you are arming your project with the best resources available. 

Remember it is people who make it happen, not technology.  Every project that has the largest impact on an organization is due to the people on the team that applied sound design, best practices processes, quality definition of deliverables, and executed well when applying the technology.

Stay tuned for the last in the series:  Achievable Timeline

0 Comments »

Focus on a Realistic Scope

In my previous discussion on creating a success plan, I shared the secret sauce:

Success Plan = Realistic Scope + right skilled resources + achievable timeline

In this discussion, I want to focus on the first ingredient of establishing a realistic scope.  The scope of the project sets up the approach a project takes.  I always keep in mind that the goal is to define the scope that is achievable within a 60 day cycle.

DanceHave you ever been to a kid’s dance recital?  You know the 3 hours of back to back dances of all genres including tap, ballet, modern, jazz, lyrical and hip hop.  You sit for the entire show to watch one of your family members dance for 6 minutes.  Have you ever thought about the process they go through to put that show on at the end of the year?  Many people wonder how the kids remember all that choreography and perform all those dances.  They do it in small phases throughout the year.  They teach one number at a time by creating classes or small groups of people to focus on a genre for a certain age group.  By having many various small groups working separate dance pieces, they can focus on the quality of their technique and performance abilities.  At the end of the year, they put all these groups together to create an amazing showcase.

I like to use a similar concept when planning projects as well.  There are always long term goals and objectives.  Within each of these, I would define smaller goals and objectives that become the steps needed to get to the long term goal.  Evaluate the areas of the organization that would have the largest impacts or benefits.  It may be necessary to do this exercise within each functional group depending how the project goals impact across the functional lines or the work flows require various collaborations across groups.  Look for the quick wins, functional areas and processes that are struggling the most or could have the highest gains.  Evaluate the ability to define the scope to be able to achieve it within 60 days.

For example,  I had a customer who intended to implement a PPM solution globally.  They had over 500 projects managed throughout various groups.  They started out with this as their scope.  During our Discover and Design sessions, it became clear that the area with the most pain was their marketing group.  They had some critical business needs to improve their management of various marketing projects that would have a direct impact on their customer satisfaction and increase revenue.  It consisted of only 25 key projects.  This became my target for them to define a detailed scope around as our Phase I goals and objectives.  We could accomplish this within the 60 day timeframe and deliver value to the organization with high visibility to show the impact of their new PPM investment.  This became the approach they took to define all their follow on phases, rolling out the solution in a logical priority delivering value on an on-going basis.

The key to success is to work the plan into organized smaller work streams with defined scopes that can be executed within 60 days.  Prioritize them based on highest to smallest impact and value to the business. If the capacity is there, mulitple work streams can be executed in parallel to deliver multiple key objectives in the same 60 day timeframe. This will become the project plan roadmap to delivering the long term commitments.

0 Comments »

Realistic Plan plus Execution equals Value

In the 15 years I have been in the software business and the over 20 years I have been implementing systems, it never ceases to amaze me at the number of implementation plans I review that I instantly know will fail.  A plan for success is simply the right balance of scope, resources and time.  Revolutionary, I know.  We’ve only heard that a million times before.
Gerald Pole Vaulting
However, I can equate it to a story my son shared with me.  My son, Gerald, was a pole vaulter in High School, jumping 15 feet, which put him in the top 3 in the county.  A few of his track teammates would tease him about how easy pole vaulting was and anyone could do it.  So he handed the pole to one of the guys, Jeremy, who was boasting about his ability to do any track event without any coaching.  Jeremy knew it all and was athletic and he was convinced that he could vault as good as Gerald.  Jeremy took the pole and just started running down the runway and attempted to plant the pole in the box and launch himself in the air. When the pole bent, it slammed him right back down on the ground.  He never got more than a few inches off the ground and was stunned by how hard the pole flicked him back on the ground.  Jeremy returned the pole to Gerald and simply said "You the man.  That’s way harder than it looks." He walked away quietly.  He became one of Gerald’s greatest fans at the meets. 

So why do we approach a project implementation in the same way?  Without a good plan that has realistic goals, objectives and defined scoped, along with the right skilled resources planned along an achievable timeline, the project will fail.  Here’s the secret sauce:

Success Plan = Realistic Scope + right skilled resources + achievable timeline

Defining a realistic scope should be something achievable within 30 to 60 days.  A good plan requires planning with the right people in the discussion.  Begin with the high level goals (company, annual, quarterly, etc).  Align the project to one of these goals.  Then further define the goals and objectives of the project that will directly contribute to the high level goal you tied the project to.  Define the requirements needed to achieve the goals and objectives.  Simple and small is always the way to get to a full scale implementation.  Phase the scope into short time cycles (30 to 60 days) so that achievements are delivered as value to the business on an on-going basis.  If you start simple, you can always add additional capabilities or complexity.

The next step is to evaluate the resources needed to deliver the requirements.  This must be the right resource not just anyone who is available.  Make sure the resources defined for the delivery of the project really do have the right skill set to deliver on the requirements.  If the resource skillset required doesn’t exist in house, then look to outsource or bring in the skills needed.  There are many reasonably priced outside resources that can be used to deliver on key elements of a project if managed properly.  When defining the resource pool, make sure to use available work days for those resources (take out PTO and training courses).  Then evaluate what other tasks or projects they are assigned to and determine capacity for realistic available dates of the resources.

The next step is to review the timeline.  Just like a good forecast, it is best to create your preliminary project plan with the main elements required to deliver, following a proven methodology of stages (i.e. plan, design, build, test, deploy) and see what it is going to look like.  Apply the resources you have identified with the available capacity you have defined.  This should give you a preliminary timeline of delivery.

Finally, once you have a preliminary plan that has the scope defined, the right resources assigned that produces a first draft of the timeline, review this plan from a realistic approach.  Analyze eachs stage of the plan and ask questions (i.e. The plan shows it will take 2 weeks to install and setup the solution, does that make sense if you know it takes only a day to do this? or if the plan shows it will take 6 months to complete, can you review your requirements and move some planned deliverables to the next phase?)  Don’t be afraid to change your scope right up front.  If the plan seems like it is too heavy and complex to deliver in a 30 to 60 day cycle, cut the scope to something more reasonable and attainable.  Find the number one or two pain points that can make a difference in the group or organization quickly and focus on delivering that one element.

Make the plan simple, concise and achievable in 30 to 60 days or less.  Anything more will fall into the 75% of projects fail bucket.  I am a believer in 100% of projects can succeed with a realistic plan defined with the right scope, resources and timeline.  Look for more indepth discussions on each of these secret sauce elements in the near term.

0 Comments »

© 2011 AtTask, Inc. All rights reserved.