October 2, 2015 | Author: PM Hut | Filed under: Project Management Best Practices
How Transparent Are You?
By Kiron D. Bondale
PMI’s Code of Ethics clearly illustrates the value placed on transparency in the project management profession – both the Honest and Fairness sections of the Code contain standards which echo the importance of this attribute. This includes transparency in decision-making as well as being truthful, accurate and timely in our communications.
But just how transparent are we really on a day-to-day basis when we are managing our projects?
Do we share what we are doing to respond or resolve each and every risk and issue (no matter the criticality) with key stakeholders?
Do we automatically set our schedule or cost health status to red the moment we exceed approved baselines, no matter how slight that variance?
Do we bring each and every requirements change to our sponsor as change requests?
Do we document each and every step taken along the path to making a critical decision?
Of course not.
Too much transparency can undermine credibility in a project manager as quickly as incompetence does. It also encourages sponsors and other stakeholders to engage in micromanagement.
I’m not advocating deceit. If your project is genuinely in harm’s way, it is your responsibility to make sure this information gets shared with the right stakeholders in an objective, timely fashion. If you know that a certain path of action will benefit your company but not your customer, you should be open about that.
But never forget that a large part of project management is stakeholder expectation management. Our stakeholders are expecting us to be trustworthy and competent which means that while we need to be transparent we also are expected to use our judgment.
Judgment is a key difference between someone who is managing a project and someone who is merely reporting on its status. Otherwise, most project management information systems would have the triggers for health status indicators or alarm notifications hardcoded whereas most of the time, these features are fitted with manual overrides. The designers of these systems understood that no matter how advanced are the rules which you’ve codified for evaluating project health, you can’t remove the human judgment element from the equation.
Yelling “Fire!” in a packed theater might be a lesser offense than not having working smoke detectors in a similar venue, but they are both criminal acts.
Kiron D. Bondale, PMP, PMI-RMP has managed multiple mid-to-large-sized technology and change management projects, and has worked in both internal and professional services project management capacities. He has setup and managed Project Management Offices (PMO) and has provided project portfolio management and project management consulting services to clients across multiple industries.
Kiron is an active member of the Project Management Institute (PMI) and served as a volunteer director on the Board of the PMI Lakeshore Chapter for six years.
Kiron has published articles on Project and Project Portfolio Management in both project management-specific journals (PM Network, PMI-ISSIG journal, Projects & Profits) as well as industry-specific journals (ILTA Peer-to-peer). He has delivered almost a hundred webinar presentations on a variety of PPM and PM topics and has presented at multiple industry conferences including HIMSS, MISA and ProjectWorld. In addition to this blog, Kiron contributes articles on a monthly basis to ProjectTimes.com.
Kiron is a firm believer that a pragmatic approach to organization change that addresses process & technology, but most important, people will maximize your chances for success. You can reach Kiron at [email protected]
This entry was posted on Friday, October 2nd, 2015 and is filed under Project Management Best Practices. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.