• Products
    • Demos
    • TaskMap Standard
    • TaskMap Pro
    • Capture for Excel
    • TaskMap Central
    • Upgrade
  • Downloads
    • Trials
    • Templates
    • Free Role List
  • Training
    • Self-paced Tutorials
    • Online Seminars
    • Calendar
  • Solutions
    • ITIL Suite
    • SOX Expert Suite
    • SPM Roadmap
    • Consulting
    • Process Conversion
    • Process Templates
  • BPM Blog
    • Process Mapping
    • Process Discovery
    • Process Analysis
    • Improvement
    • Change Management
    • Articles
  • Support
    • Product Support
    • TaskMap
    • FAQ's
    • Contact
    • Self-Paced Tutorials
  • About
    • Contact
    • Partners & Resellers
    • Background

  • About the BPM Blog
  • BPM Blog Sitemap

BPM Blog

BPM made simpler

« When things go wrong–troubleshooting
Managing changes in the project »

Getting your project out of trouble

Mar 27th, 2011 by TaskMap

Listen and access

Listening is defined as “hearing with attention”. I like that definition, because some project managers hear but don’t listen to what is being communicated. In some cases the individual may also be nervous about bringing this news to you, and may therefore emphasize certain parts of the problem and not others. This is one reason why an initial reaction to the issue should be avoided if possible.

For example, a team member may let you know that they are going to miss an upcoming deadline and that the primary cause of this is another person or vendor not delivering what they need. After you listen to the issue and examine all factors, you may find that the problem is more like half the vendor’s problem and half the other team member. If you immediately react to the message the vendor is late, the fact that your team member did not provide them with an earlier deliverable may have caused the problem in the first place.

This is an important point in project management, if your team members know that you react badly to bad news, they will try and avoid delivering it to you. My earlier point of shooting the messenger applies here. As a project manager, you want all the news about the project, both good and bad. This is needed to take the necessary action when issues arise.

Once the problem is known, then take the necessary time to assess its impact on the project. By determining the severity of the issue, the action plan that will result may differ considerably.

Determine an action plan

Once the severity of the problem has been determined, then you need to build an action plan to solve the issue. Depending on the significance of the change, so will your action plan’s contents. For minor changes increased resources, staff or some parallel process activities might provide the results. More significant changes will require more drastic actions to be taken. Typical plans could include:

  1. Minor course correction within scope of existing plan;
  2. Significant impact on current budget or deadlines – need to build document change and agree revised project plan with changes factored in;
  3. Huge impact on plan – may be necessary to re-budget or access the viability of the current project.

Change control

Figure: Action plan process options

Once this assessment is made prepare for action; whatever the level of change involved.

Take action

Some project managers are good at listening and even planning, but seem reluctant to take action. Like jumping off the diving board for the first time, going down the ski slope or any first time challenge, the action has to be taken.

No amount of research or planning will take the place of someone doing something. If the investment has already been made to resolve the problem, then just do it. Ensure that the action plan includes communication with all team members, not just those impacted by the changes. At times of trouble, over communication can help motivate the team, take on the new challenges and give new life to the project. Action steps should include:

  • Communicate the plan to get the project back on track;
  • Determine specific actions for individuals or groups;
  • Ensure all members understand the impact on the current plan and schedule;
  • Slow down or stop activities that may be affected.

Excerpted from Finish What You Start by Michael Cunningham

Tags: bad news, deliverable, drastic actions, important point, initial reaction, minor changes, necessary time, parallel process, project management, project managers, severity, team member, team members

Posted in Change Management, Process Improvement, Project Management

Leave a Reply

Click here to cancel reply.

  • Archives

    • March 2012 (1)
    • February 2012 (3)
    • January 2012 (4)
    • December 2011 (11)
    • November 2011 (16)
    • October 2011 (17)
    • September 2011 (20)
    • August 2011 (21)
    • July 2011 (21)
    • June 2011 (22)
    • May 2011 (22)
    • April 2011 (23)
    • March 2011 (26)
    • February 2011 (28)
    • January 2011 (31)
    • December 2010 (31)
    • November 2010 (20)
  • Recent Posts

    • Business Process Modeling
    • Education
    • The issue of organizational culture
    • A VERY SHORT HISTORY OF PROCESSES
    • Process Dashboards: Identifying and flagging risk levels
    • Process Dashboards: Analyzing timeframes
    • THE CASE FOR PROCESS DASHBOARDS
    • Is 2012 the year that version control finally takes hold?
    • How to listen carefully to your team–Reflective listening skills overview (Part 8)
    • How to listen carefully to your team–Reflective listening skills overview (Part 7)
    • How to listen carefully to your team–Reflective listening skills overview (Part 6)
    • How to listen carefully to your team–Reflective listening skills overview (Part 5)
    • How to listen carefully to your team–Reflective listening skills overview (Part 4)
    • How to listen carefully to your team–Reflective listening skills overview (Part 3)
    • How to listen carefully to your team–Reflective listening skills overview (Part 2)
    • How to listen carefully to your team–Reflective listening (Part 1)
    • TaskMap Update: version 4.0.5
    • BPM BLOG Summary for week ending 2 December 2011
    • The Tutorials are coming … the tutorials are coming
    • The psychology of spending and how it can help BPM ;-)
    • Happy Thanksgiving
    • BPM Blog–The need to refine
    • Processes as instruction tools
    • BPM Blog Weekly summary 11.18.2011 with video blog
    • Project and Processes (responses to the questions)
    • Projects and processes
    • Thinking things through
    • Happy 11.11.11 and BPM Blog summary
    • TaskMap Automated tutorial: TaskMap Capture for Excel
    • Customizing fields in TaskMap 4 Professional
    • Prioritization in your life
    • The need to refine
    • Happy Anniversary BPM Blog: A good first milestone
    • Training the trainers
    • Power
    • BPM Blog summary for week ending 28 October 2011
    • Customized process mapping
    • Agile methodology: The case for a blended Agile
    • Additional displays: Are they worth the money?
    • BPM Blog summary week ending 21 October 2011
    • Thoughts matter: How thoughts affect our actions in everyday life
    • BPM Summary of automated tutorials on the TaskMap menu
    • Automated tutorial—Save as process folder
    • Automated tutorial—Task Links and how to use them
    • Automated tutorial for Task Details
    • TaskMap Tutorial—Save as PowerPoint
    • Check my TaskMap
    • BPM Blog summary week ending 7 October 2011
    • Renumbering Tasks in TaskMap
    • Customizing roles names in TaskMap
    • Adding tasks to a Page–add task to page Dialog
    • How to add tasks to pages using the auto connect feature in TaskMap
    • BPM Blog Summary Week ending 30 September 2011
    • Towards Perfection
    • BPM in the Legal Profession
    • BPM BLOG SITE MAP
    • Rigor and our business processes
    • BPM Summary Week ending 23 September 2011. The Case for a Blended Agile
    • The Case for a Blended Agile: Part 4-Agile Stepping Stones Approach
    • The Case for a Blended Agile: Part 3-What a blended approach looks like
  • RSS Get the BPM RSS feed

  • Posts by category

    • Change Management
    • Compliance
    • Law Processes
    • Legal processes
    • Org Charts in Visio
    • Process Analysis
    • Process Discovery
    • Process Improvement
    • Process Mapping
    • Project Management
    • Uncategorized
  • Tags

    best practices bpm budget business analyst business process category change change management computing group dashboard decisions discovery discovery phase efficiency flowchart flowcharts goals and objectives governance harvard job management change management project map methodology mike cunningham milestones personality process documentation process improvement process mapping process maps project management project managers quality standards return on investment risk role names sox compliance target task library team members technorati time and money timeframe Visio willingness

Home • Products • Downloads • Templates • BPM Blog • Training • Contact Us • SiteMap

Copyright © Harvard Computing Group, Inc., 1994-2011. All Rights Reserved. TaskMap is a registered TradeMark of Harvard Computing Group.
Harvard Computing Group, 225 Cedar Hill Street, Suite 200, Marlborough, MA, 01752, USA Tel: 978-800-4590