Managing your Steering Committee
October 19, 2009 @ Better Projects from Craig Brown
Tim van Gelder writes a post on how boards use information and make decisions.
Two key pieces of information that I took away from the post are that Boards will share better if they think they are solving some kind of factual issue as opposed to making a judgement requiring consensus.
Boards share information better if they use a structured discussion process, rather than just indulging in the usual kind of spontaneous conversation.
The idea here is that Boards need to be actively engaged in managing things. For me and you it is our project steering committees and governance groups. How do we get them more involved in the project?
By making board members participate in certain decisions they 'own' the solution more than if they just front up and rubber stamp a progress report.
Every report on project success or failure includes mention of close customer engagement as a key success factor. Frontline managers are not the customer. The sponsor and steering committees are much better embodiments of the customer, as they are the ones paying for the product your project is delivering. Getting your board members involved is a step in the right direction.
In order to help boards collaborate more, Tim endorses a McKinsey recommendation to augment proposals and recommendations with a 'red report' or the counter argument to the actual recommendation.
This is a common approach used in project management: the infamous 'three options' including or augmented with the "do nothing" option. Depending on the time and relationship you have with your board/sponsor, and the importance of your project what can you do to get them more involved in your next board (or steering committee) meeting?
This article is syndicated from Better Projects . The original article is available here. Read more in Better Projects, Project Management News .
No tags for this post.
Reminder : PMToolbox has ZERO tolerance to copyright violation and agrees to follow strictly PMI's Professional Responsibility. That's why each post on this site includes a link to the original version at its source site.
Comments
Got something to say?
Articles
Application Development Methodology
PMO
Customer Relationship Management
procurement
Cost Benefit Analysis
Information Engineering
It White Papers
Tools
team
Crm Applications
Deliverable Templates
Business Case
Systems Development
Ganthead
Resources
portfolio management
Project Office
best practices
Program Management Office
communications
Risk Management Programs
Schedule
Project
human relations
Project and Program Management
Microsft Project
templates
Risk Analysis
Cost
Knowledge Management Processes
Information Technology Planning
Methodologies
integration
Issue Tracking
ROI
Package Selection
MS Project
Business Intelligence Tools
contract
Quality
Gantthead
Scope Management
Project Management
program management
