Project Smart ~ Exploring trends and developments in project management today

Calendar icon
Adobe PDF icon

Has Your Project Team Considered All the Key Dimensions of the Problem?

~ By Rune Aresvik

Blue and white cubes with questions

Many readers have mentioned to me that they feel that a lot of the projects they sponsor (even the successful ones) are often on "automatic pilot." This typically happens once the project teams feel that they understand the problem and have decided on what they believe to be the most appropriate direction for solving the key issues facing the project. The consequences from this can be severe. The most dangerous consequence is often that key aspects of the problem are overlooked. More common is that the team has not analysed all the relevant dimensions to the problem, and therefore has not developed complete and optimal solutions.

An example of a similar situation from my own work was a project team in the insurance sector that was developing a new structure for a company in response to key legislative changes. A key component of the project team's work was to look at the key business drivers for succeeding in the new environment. In a meeting the team presented their key hypotheses, which seemed to make sense. However, a clarifying question was asked about one of the success-drivers suggested by the team, and this lead to a broad discussion in which several new success drivers were identified which the team had not considered. Luckily, this did not happen in the final presentation to a SteerCo, but in a pre-meeting.

This type of situation can easily be avoided by borrowing a methodology used by consultants called a Blue Team (sometimes it has a different name). The methodology helps ensure that project teams are shaken out of the "automatic pilot mode" and have considered all relevant aspects before the end of the project. This methodology can easily be adapted to internal project teams as well, and is guaranteed to improve the overall quality of the work delivered.

A Blue Team is a structured meeting typically held once, maybe twice, during a project. In this meeting, the project team gives a short presentation on what it believes to be the key issues (if the meeting is early in the project) or key hypotheses (if the meeting is later in the project). The presentation is given to an invited group of people who are not directly involved in the project. The guest list for the Blue Team should include people with relevant knowledge and experience to the issues being dealt with by the project. Typically the people invited have market knowledge, technical expertise, and/or process experience.

The invited group needs to be able to quickly understand the issues being discussed, and is meant to be critical in the questions they ask, the comments they give, and the suggestions they make. However, the participants also need to understand that their comments and questions are meant to be helpful to the team. The Blue Team therefore needs to find a balance between criticism and support. One way of achieving this is to clearly state upfront that the process is meant to help the project team, and therefore only the project team can decide how to use the criticisms, ideas, and suggestions coming out of the meeting.

Even in the best of cases, the Blue Team is tough on the project team, as they (by definition) will get criticism on the work that they have carried out. Given the psychological barriers related to receiving criticism, even a project team with good previous experiences may have to be forced to carry out the Blue Team. My recommendation is therefore to make Blue Teams a standard part of all complex projects that you sponsor, thereby avoiding any choice or discussion on the process.


Rune Aresvik is a consultant with more than twenty years of experience in project management training and project management consulting. Go to Rune's project management blog for more articles.


Comments

Be the first to comment on this article.

Add a comment



(never displayed)



 
2000
Out of 56, 14 or 27, which is the largest?
Notify me of new comments via email.
Remember my form inputs on this computer.

Tracking a Risk

Dial showing three levels of risk management

Risk management is a vital part of project management. Learn four key steps to help you evaluate and mitigate any risks on your project.

Taming MS Project

Gantt chart and plan

Microsoft Project can become a huge overhead, even for seasoned project managers. This article contains some tips and tricks that will help you tame the tool.

Resourcing Project Managers

Project manager jobs advert in a newspaper

Ironically, although resourcing production team members is a significant part of a Project Manager's role, very little focus is placed on resourcing the Project Managers themselves.

My Budget is 10% Over, Now What?

10 percent red wood sign with golden background

Suffering a budget overrun? Here's three key things you can do mid-stream on a project to help get the budget back in line with the original plan.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Peter Earnshaw commented on…
Pareto Analysis Step by Step
- Tue 4 February 2:03am

Lesiba Matlou commented on…
Writing a Funding Proposal
- Sun 26 January 5:18am

Tim Rumbaugh commented on…
10 Golden Rules of Project Risk Management
- Sat 28 December 6:48pm

Latest tweets

General Project Management • Re: How to Determine Resource Allocation https://t.co/3dnEwB6Q0Z about 4 days ago

General Project Management • Re: Best Project Management Software? https://t.co/HyQCVlHo1Y about 7 days ago

General Project Management • APM Full Membership https://t.co/O5GdicubRr about 9 days ago