A few years ago, I held my first Strategy Review Meeting (SRM). We had a great agenda and flow. We had strong presenters going over the progress we\u2019ve made. Our KPIs were giving us trend information allowing for great discussion. Our project updates were giving leadership visibility into our scope, schedule, costs, quality, issues, risks, resource constraints, schedule delays, etc. I then saw a few executives shifting uncomfortably in their chairs as we discussed more projects. Some looked frustrated. Questions started racing through my mind. Are these project reports the same reports given at sponsor meetings? Did I see these same reports at the project review board or the steering committee meetings? Was this redundant information?\u00a0 The answer to all of the above – yes. It then hit me – there wasn\u2019t enough strategy in our strategic project reporting!<\/p>\n
So, can there be \u2018strategic\u2019 discussions around projects beyond traditional project reporting? Can leaders\u2019 conversations really be elevated from the weeds to 30k feet?<\/p>\n
Absolutely!<\/strong><\/p>\n Reviewing the progress made on strategic objectives (goals) is critical for any organization looking to improve their strategy execution. Getting a performance review cycle from concept to operational is a significant undertaking requiring collaboration between senior leaders, strategic planning staff, objective owners, project sponsors, project managers, data entry staff, data analysts, etc. Most organizations start with quarterly SRMs and break down their reporting into two topics \u2013 projects and KPIs.\u00a0 Discussions around these two items give us a decent picture of how we are doing and what needs to get done moving forward.<\/p>\n Roles<\/strong><\/span><\/p>\n Project Managers (PMs) and Project Management Offices (PMOs) have earned the well-deserved reputation of being able to increase the chances of project success. Among other things, they track project progress and report on project-level elements to ensure projects get the attention needed and continue moving forward. Strategic planning staff and Strategy Management Offices (SMOs) facilitate the planning process, document the strategic plan, and monitor\/coordinate the reporting of progress made on the plan.<\/p>\n \u00a0The problem<\/strong><\/p>\n Two common mistakes I see SMOs and planning staff make are to either adopt a PM\/PMO project reporting format simply because PMs and PMOs know projects best or they allow those reporting to follow a format they like and most will migrate to the same source for templates – PMs and PMOs. The issue with this? Project-level reports are meant to give a picture of the project. Most do not provide visibility into the impact those elements (e.g., schedule delays, cost overruns) have on the strategic plan.\u00a0 Using a project-level report format at a SRM also creates redundancy in project reporting which may lead to frustration and a lack of interest in the strategic planning effort.<\/p>\n \u00a0A solution<\/strong><\/p>\n It is important to start with a simple format. The goal is to transform the organization over time and rushing or complicating this effort may create unnecessary risks to the transformation process. Refine the SRM project reporting format to capture the direct impact a project\u2019s performance has on your strategic objectives, KPIs (immediate and projections), and possibly, higher elements such as your themes and vision. Focusing on the impact to strategy elevates the SRM discussions to the right altitude and forces senior leaders, project managers, project sponsors, etc. to think and prepare differently.<\/p>\n A simple SRM reporting format for presenters to follow is:<\/p>\n