Driving Transformational Change with Problem Solving and Effective Status Reporting

Organizations that seek to build the right kind of PMO should work closely with their executive leadership teams and human resources department to attract and hire problem solvers and not just the run-of-the-mill certified project manager. Former management consultants are good resource pools to tap into given their training often focuses on generalist analytical and problem solving skillsets. Moreover, they typically possess the communication “soft skills” required to manage and serve a variety of stakeholders from the C-suite down to the tactical level.

The Problem Solver’s Approach to Executive Status Reporting

In a previous article (Lessons for Launching a Project Management Office (PMO) To Support DSRIP Implementation), we talked about the importance of obtaining commitment from executive leadership teams in order to launch PMOs successfully. Buy-in can deteriorate quickly if leaders can’t obtain reliable, data-driven information from their teams to monitor project progress, understand pain points within the organization and quickly execute decisions to break down barriers towards achieving results that support the overall business strategy. One of the key roles of any successful PMO is to provide that information through weekly executive status reporting in order to drive the decision-making process. It is important to note that reporting activities should occur weekly in lieu of a biweekly or monthly cadence in order to surface risks and issues as early and often as possible. Project managers adept at problem solving will often connect with their customers daily in an unobtrusive manner (once again highlighting the important of having strong communication skills) in order to gauge the health of an activity, workstream or project.

While there is no universal executive status report and dashboard that fits every organization, we have found that reporting against critical path milestones that have been pre-identified, analyzed and agreed upon with the project’s executive leadership is a good start. The traditional definition of critical path indicates activities that must start and finish on their designated dates, or else there are negative impacts to the end date of the entire project.⁴ As we emphasized, project managers who act as problem solvers versus task trackers work iteratively with executive leaders come up with the “right” critical path details that are simple, transparent and common sense for monitoring projects. PMOs must make a cultural shift from “the more detailed information the better” to providing just enough of the right data to leadership about ongoing initiatives.⁵ In other words, it is important to know your audience and understand that executives get the most value from status reporting when they have a quick and easy reference to make decisions on a minimum weekly basis. What determines “quick and easy” will differ depending on the person. Since no one leader is alike, it is important for project managers and their executive leadership teams to set content expectations for reporting during pre-planning or planning stages. This process requires a high degree of flexibility and adaptability on both sides. Project managers should have a broad range of soft skills competencies such as communication, conflict resolution, persuasion and facilitation.⁶

Generally, most effective status reports center around critical path milestones, which are often presented in a dashboard view where colored indicators representing whether progress is on track (green), at risk (yellow) or has major issues (red). There are also sections to call out risks and issues (along with proposed mitigation steps or solutions) and support information on activities through the next week. It is also important to note that the objective of status reporting is not to achieve “green” statuses week over week. Creating a PMO environment where lots of green equates to success leads to a culture where project managers will do anything possible to keep from turning an indicator yellow or red, and avoid calling out risks and issues to force a tough conversation.⁷ The purpose of executive status reporting is to facilitate a continual process for leaders to prioritize resources for new projects and make decisions around troubled projects such as allocating additional resources, pushing out launches or killing projects off entirely.

Executive status reporting is just one facet of building the right kind of PMO to help an organization get things done along the way to meeting strategic goals. The foundation for ensuring that these components are value-added will ultimately depend on the people who manage and execute those processes and tools, often in ambiguous and political environments. The strongest PMO foundations will contain a cadre of problem solvers who are willing to hold leadership teams accountable and are capable to help them succeed.

Bridging the Gap

As we have worked with our clients to develop their PMO capabilities, we have seen them benefit from these practices. We know that there is often confusion in the beginning of project implementation, and we help our clients ease the transition by guiding them through the process of identifying and prioritizing their project management requirements, staffing and training their PMO teams, and standardizing and promoting a shared toolset. COPE Health Solutions can assist your organization to assess your current project management capability, and develop a clear vision and operational plan to implement your project management office. Through our partnership, we will build a PMO that is both integrated with your organizational strategy and will drive the management of your project portfolio.

For more information, please contact info@copehealthsolutions.com.

Footnotes:

¹ Brill, Steven “Code Red.” TIME March 10, 2014: TIME.com Web. 1 March 2014.

² Schoen, Mebula. “Seven Best Practices for a Highly Effective PMO”. Gartner. 10 March 2016.

³ Buchanan, Stewart & Lars Mieritz, “Free Your PMO to Be the Accelerator for Change, Not the Brake”. Gartner. 8 October 2013.

⁴ https://www.pmi.org/learning/library/moving-work-breakdown-structure-critical-path-6978

⁵ Schoen, Mebula. “Seven Best Practices for a Highly Effective PMO”. Gartner. 10 March 2016.

⁶ Schoen, Mebula. “Seven Best Practices for a Highly Effective PMO”. Gartner. 10 March 2016.

⁷ Apfel, Audrey L. “Best Practices for Project and PMO Reporting: Creating Effective Executive Dashboards”. Gartner. 21 December 2011.