Lesson on Managing Issues

Must read

IT Project Teams are STILL driving competitive advantage

IT Projects are perfectly placed to shape the future of business as we emerge from this pandemic Businesses need to be leaner and more innovative. It’s time for IT Project teams to say, “Hold our coffee, watch us do our thing” – this is our moment.

Embrace the change: Getting to grips with new IT systems

New IT systems for a growing business can be an exciting prospect and deliver many benefits, but how do you convince employees to embrace...

5 Skills Needed To Drive Future Projects

Why do projects fail? It's a question that invites a lot of interest and significant statistics. And there are no wrong answers here. Skills shortages...

Does a Project Manager Need PM Qualifications?

What makes a successful project manager is a combination of their academic abilities, experience and skills, both "soft" and "hard" skills i.e. communication skills...
nevilleturbithttp://www.projectperfect.com.au
Neville Turbit has had over 20 years experience as a Project Management and IT consultant and almost an equal time working in Business. He is the principal of Project Perfect, a Project Management organisation based in Sydney, Australia that specialises in helping companies put in place the "Project Infrastructure" to better manage projects.

Here is another lesson I learned from a real life project.  This one relates to managing issues.  On one occasion I was called in to look at a struggling project.  The project had about 100 staff but seemed to be going around in circles.  Progress had slowed if not stopped.

The first task was to get to grips with why.  The problem turned out to be many problems.  Almost every aspect of the project was bogged down in problems that were causing the wheels to grind to a halt.

The project was to implement SAP in a manufacturing organisation.  The team doing the data conversion were waiting on the team doing the database design before they could proceed with the conversion testing.  The team doing database design were waiting on feedback from SAP in Germany regarding some customisation before they could finalise their design.  The team in Germany were waiting on input from the manufacturing as to how they wanted to handle component specifications.  This was just one example.

All the problems had been raised as issues and were being considered but had been delayed because everyone seemed to be reliant on someone else making a decision.  Schedules were constantly being revised.  Just getting all the relevant people into a room seemed impossible.  A sub group would write up a proposal which would be circulated for agreement, and usually the proposal would not work for another sub group.  Decisions were taking weeks.

The problem was there was too much activity and not enough action.  My proposal was to stop the project for two weeks and solve all the problems.  The typical response was:

“We can’t stop the project.  We are too far behind now!”

Finally sense prevailed.  We actually identified about 30 major issues.  Some were related to others and some unrelated.  For each issue we identified the core problem.  Where did it all start?  What was the thing we needed to solve to enable subsequent decisions to be made?

We treated the issue resolution as a project running two weeks.  By identifying the resources we needed to solve each issue, we were able to schedule multiple workshops and ensure everyone who needed to attend was present.  For those not participating in the exercise, we had them working in a support role.

  • When decisions were made they could work on the implementation of the decision.
  • They were involved in gathering information to allow the decisions to be made and tested.
  • Some work could proceed regardless of the issue roadblocks.

One problem we did encounter was the logistics of having enough meeting spaces.  Fortunately there was a nearby hotel that had conference facilities we could use.  We also had to involve people on the other side of the world in teleconferences so we basically ran workshops for 18 hours a day in some cases.

The workshops ran from half an hour to a few days.  Yes, one did get resolved in half an hour.  It was just a matter of getting the right people in the room at the same time.  Timing was unpredictable and we were constantly shuffling timings of meetings.  In fact we ended up publishing a new timetable twice a day.

All meetings were facilitated.  An independent person ran the meeting to focus the group and ensure all views were considered.  They were typically non experts who had nothing but common sense to contribute to a solution.  Because they were not experts they could ask the basic questions that sometimes removed the complication.  I remember one issue which related to catering for multiple overtime rates for different groups of people.  The differences were minor.  The facilitator asked if anyone had costed the expense of managing the rates versus the cost of a single rate.  Another group did the exercise and found it was cheaper to have a single rate at the higher level than lots of minor rates.

At the end of the first week, we were down to about ten significant issues.  Some people were able to get back to project work as roadblocks had been cleared.  After two weeks we were down to about two or three issues that were still being worked on.

What we learned was that sometimes it is best to stop.  If things are getting out of control remember the old adage.  When you have dug yourself into a hole, stop digging.  The project team had a much different view on resolving issues.  As the project proceeded, they gave much more importance to fixing problems.  If an issue came up, the Sponsor made sure everyone who was involved made themselves available to resolve the issue as soon as possible.  The Sponsor required all significant issues be escalated to him, and the impact of the issue on the project had to be stated as part of that escalation process.

Another lesson was that all experienced project managers know there should be a proper issue resolution and escalation process in place but business leaders may only pay lip service to such a process.  It is only when things start to go pear shaped that they see the value in the process.  Just because it is documented some where, does not mean it will be accepted or followed.  Occasionally a bit of pain is needed to teach people the value of a project process.

 

Neville Turbit is principal of Project Perfect.  Project Perfect sell Project Management Software as well as consult on projects and undertake Microsoft Access Development

 

- Advertisement -

More articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.

- Advertisement -

Latest article

Training project teams on global projects

An exciting new project has started involving teams from right across the globe – both within the organisation and from external suppliers....

Project Management Lessons learnt from Covid Holiday Disruption

The very definition of Holiday (Noun - an extended period of leisure and recreation, especially one spent away from home or in travelling), is an entirely flexible parameter to work within, so how do we adapt? And what Project Management lessons are to be learnt from this summer?

Project management for the ‘new normal’

We live in strange times. Who would have thought last year that 2020 would be the year of Covid-19, the year of...

Long-Term Strategies To Help Manage Your Team Remotely

The world has changed profoundly since COVID-19. No one saw a global pandemic coming but now isn’t the time to panic. Instead,...

10 Steps for Planning and Implementing a Successful Branding Project

Your brand is perhaps your most valuable asset. It defines your organisation’s reputation and visibility in the market. The strength of your...