Agile is a software development approach. However, it is now applied not just in software development but also features prominently in project management and operations management. With the increasing popularity of agile, change practitioners are also rushing to re-position and tailor their work to support the agile environment.
On top of the basic agile ‘manifesto’ that outlines agile principles, there are now numerous organizations providing the technicalities of how to implement and support agile. Many are overwhelmed by the various practices such as scrum, kanban, refactoring, etc. Agile may be applied to a project team, program, or portfolio level.
I went through the Scaled Agile certification process and was amazed at how much basic common change principles are embedded within the agile approach. Through the multi-day training course, case studies and the examination, I was quite interested in how a lot of foundational change principles that are common sense for us in change management, are somehow ‘new’ for technical leads or project managers. Agile incorporates what change managers have been calling out all along. To read about how Ray and Charles Eames showed us agile project delivery click here.
What are some of the foundational change management principles incorporated within agile?
Individual interactions over processes and tools
The nature of technology environments is that technical professionals are valued by their technical know-how. Therefore, when there are problems and opportunities for improvement the first that comes to mind is usually a technical fix. We all know of Technology departments that are fantastic in designing technical solutions and features to resolve problems.
However, the agile manifesto is focused on people and interactions. Teams work best when there is constant interaction to ensure effective communication, clarity and understanding of the work at hand. Processes and tools can resolve problems when the teams and people that develop them are clear and aligned. Processes and tools are also to be used by people. So testing to what extent these meet people needs will determine their success.
This principle is music to our ears as Change Managers have always been proponents of influencing the project team to focus on people and behaviours, rather than systems and processes. People are the centre of what Change Management is about and this principle, as a key tenet of agile, highlights the role of people and behaviours.
Early involvement of stakeholders
Agile projects can move fast. As a result, it is critical to bring people together early in the project development lifecycle to ensure there is clear alignment and understanding. Moreover, it helps to foster team relationships early on. Typical practices include bringing a wide range of stakeholders including project sponsor, subject matter experts, technical leads, change lead, business leads, etc. early in the project inception stage in workshops. Assumptions are drawn out. Expectations are set. Relationships are built. This then sets the stage for effective team performance.
Change practitioners have always touted engaging stakeholders early on to ensure buy-in and alignment. This goes beyond just formal communication. This is about having a discussion, a dialogue and being able to test assumptions to drive full clarity early on across the project team.
Empowering team members
Traditionally the project manager would be the key decision maker in all aspects of the project including solution features and which member works on which piece of work. This traditional command and control style has now given way to a more empowering approach of managing a team and getting a better outcome … from having teams make most of the decisions about the solution and its features.
An inherent part of agile is about enabling decisions to be made at the level where those roles have the most information at hand about the subject. For example, rather than the project manager making the decision about what the solution looks like, the team who are involved in the details of the solution more than anyone else would make those decisions as a team. In fact, effective agile teams are often self-organized. The project manager’s role is about coaching and enabling versus making decisions on behalf of the team. His/Her role is about clearing the way so that there are no obstacles to complete the work effectively.
The work of change managers have always focused on team dynamics and employee empowerment is a foundational principle for team development and engagement. A part of the change manager’s role is supporting the development and functioning of the project team. This involves designing the role in a way that maximizes engagement and empowerment. Designing the right organization leadership is also high on the agenda of Change Management. Open and autocratic leadership means that the leader encourages innovation, experimentation, and open discussion about the work at hand.
Effective agile projects are based on the design of having team members of different disciplines, often from different departments, collaborating to achieve an outcome. The diversity of having team members from different disciplines working together brings different perspectives. Hence more innovative ideas are generated than having one team where everyone approaches the problem in the same way due to similar functional backgrounds and skill set.
Agile practices to support cross collaboration include cross team daily stand-ups, release planning, retrospectives, etc. These practices require that different disciplines come together to contribute to the project.
A constant challenge and focus for Change Management is on fighting silos and promoting collaborative behaviors toward the project end state. change managers typically achieve this through workshops, communication, campaigns, and influencing leaders and the initiative sponsor. We also do this through role design and fostering the right culture and behaviours.
Design bite-sized changes
One of the most fundamental agile principles is the idea that rather than launching a very large big-bang approach to change, it is better to break down the changes into smaller pieces. The change should be iterative, incorporating continuous learning and improvement. In this way, the risk of big failure is avoided and replaced by much smaller failure risks.
Change Management is concerned with matching the size of the change with the change capability and capacity of the impacted audience groups. Bite-sized changes are easier to digest for users. We avoid the risk of change fatigue and disrupting business-as-usual. Change managers intuitively assess the ability of users to accept changes. Smaller pieces of changes are always more palatable than large big changes.
Agile acknowledges very explicitly that the ultimate responsibility for the adoption, success and ongoing improvement of lean practices lies within an organization’s manager and leaders. The leaders are responsible for steering the organization toward agile and lean behaviours. This responsibility cannot be delegated. Leading agile involves role-modeling the right behaviours, providing the right environment for teams and ensuring that there is continuous team learning.
So, for those who come from a more technical background and are learning about agile – look no further than foundational change management principles to truly understand many of the core agile principles. For those in Change Management, do not be overwhelmed by the various agile jargon and the various technicalities and practices. Look into the core change principles you already know and preach before supplementing these with agile practices. Let these be the foundation as you practice agile, as agile is more about the principles and the mindset, than the technicalities and peculiar practices.
To check out our Ultimate guide to agile for change managers click here.
If you’ve found this article interesting, please ‘like’ and share this with your connections.
The change management profession has grown by leaps and bounds. This is proportional to the speed and magnitude of change that organizations are currently going through. To manage this complexity, a lot of large organizations have created ‘enterprise change management’ or ‘portfolio change management roles’ to tackle this.
In the same way that there are portfolio managers to manage a suite of projects, organizations are realizing that portfolio change managers may be needed to effectively drive change success. Like the portfolio manager, the portfolio change manager also manages a particular group of initiatives. This grouping is usually done based on the size of change initiatives and or business groups. There are also examples of groupings by ‘value stream’ or program clusters. For example, a portfolio change manager may be in charge of all technology projects and supporting the technology group, whilst another portfolio change manager support sales and marketing initiatives or back office groups.
To download our infographic on how to manage a change portfolio click here.
As a new field, there is not a lot of ‘how-do’ guides for the new portfolio change manager. A quick scan of the internet found very little substance in term of all facets of the work of the portfolio change manager. This guide is written to fill this gap and to help those starting out in this role or decisions makers considering creating such roles to build change effectiveness.
To effectively manage the change initiatives within the portfolio, the change portfolio manager needs to proactively work on the below 7 key areas:
1) Service offering
Defining the service you are offering to the organization is one of the most critical activities. To do this, you need to conduct an assessment of where the organization is at and its various needs for change management services. Key questions to ask include:
How mature is the organization in managing change? You may want to refer to the Change Management Institute’s model of Change Maturity here to understand the different stages of organizational change maturity
How much change is the organization going through? This will help determine the capacity of services required
How much investment is the organization willing to make to support change management? There may be a budget already set or you may need to make a recommendation based on any available internal or external benchmarks
What are the most critical needs? Conduct stakeholder interviews or workshops with senior managers, middle managers and frontline groups to understand current change challenges holistically.
After understanding the needs of the organizations and where the organization would like to head to in its change management objectives, one can then define services required.
Common services offered by a portfolio change manager or portfolio change management function includes:
Coaching and advisory (e.g. for managers and leaders in driving change)
2) Service Delivery
After defining the service provision, the next activity to focus on is how these services will be delivered. This depends on organizational needs, resources available and the skills of available practitioners in the group. Examples of service delivery options include:
Low involvement – Consultation
Change activities are managed and driven by the business or project teams with targeted support from the Change group
The change group is engaged as required over the life cycle of the project to provide guidance and consultation
In terms of change capability, this involves advising and consulting with the business as required
Moderate involvement – Partnering
Change activities are mostly delivered by the Change group with ongoing involvement from the business and the project team
A resource is assigned to support the initiative over the whole life cycle. However, this may not require 100% full-time support and involvement may ramp up or down depending on project needs
In terms of change capability, this involves working on significant pieces of deliverables such as change capability intervention design and delivery
High involvement – Full Delivery
Under the full delivery model the Change group is directly accountable for managing all change deliverables, working alongside the project and business teams
One or more full-time Change resource may be assigned to the whole project lifecycle, including specialists such as communications, learning or even organization design leads
In terms of change capability, this involves significant work on a range of change capability interventions such as a range of learning programs, building air traffic control systems and individual leadership effectiveness assessment and coaching
3) Manage resourcing & Forecasting demand
Depending on the services offered and business requirements, the Change team composition may look different. For example, for some organizations where the need is more on coaching and advisory services, fewer but more senior Change practitioners may be needed. On the other hand, for another organization where the focus is more on project delivery, the focus may be placed on a number of Change Managers and Change Analysts to support initiative delivery.
Key decision should be placed on achieving a balance of permanent headcounts versus contractors. Permanent in-house practitioners will have a deeper understanding of organizational needs and how the organization works. Contractor staffing is beneficial so as to allow the flexing or resources up or down across initiatives. Organizations that only rely on Change contractors usually fail to significantly build business change capability and maturity over time. This is because over time Change Management is seen by the business to be an activity done by contractor practitioners, thus not diluting their accountability. The group may also leverage external providers as needed for specialist skills or to offset any requirement peaks.
Forecasting demand is an important activity to get right so as not to set stakeholder expectations that cannot be fulfilled. Demand forecasting for Change services involves the following:
Extrapolating any change capability organizational requirements into anticipated FTE resource levels. This may be done in consultation with the project management office (PMO), Human Resources and Senior Managers
In resourcing for project delivery, the team needs to work closely with the PMO and project portfolio managers to anticipate demand. The Change group should also align with the PMO on any prioritization processes so as to be ‘joint-at-the-hip’ in focusing on critical initiatives that have been agreed to be the most strategic and valuable first and foremost.
In scoping for each initiative the Change group needs to ensure that it is included and involved in the inception of the initiative. Often Change professionals are engaged when the project is well into implementation and when it may be too late to ‘fix’ any change issues. To adequately scope an initiative key questions to be asked include:
How many parts of the business is impacted? How many employees?
What is the magnitude of the impact?
What is the complexity of the change? Is it innovative or disruptive? Do we anticipate significant transitional efforts involved?
What are the behavioural impacts?
Are customers impacted?
How are key stakeholder groups impacted? Could there be potential for stakeholder sensitivities?
To support purely agile projects, the Change group needs to define change deliverables throughout each phase of the initiative delivery cycle. From then, determine the resource requirement. Foundational change management work will still be applicable within an agile environment, including conducting change impact assessment, planning for change, measuring readiness for change and building business transition capability.
4) Portfolio management
At the lower end of the maturity curve, the Portfolio Change Manager may spend most of the time scoping for change resources, managing delivery, managing change professionals and liaising with key stakeholders. These are absolutely necessary activities. However, to really move up the strategic ladder the Portfolio Change Manager also needs to be able to influence the planning of the initiative portfolio versus only focusing on the delivery end of the curve.
In most organizations the PMO is tasked with managing the initiative investment and planning process. Most would refer to strategic objectives and goals and through this define the overall slate of initiatives for the coming year. Key data used include financial targets, initiative benefits, initiative resourcing and investment cost, and timing. The Portfolio Change Manager is often not involved in this process at all, or best, invited for comments around ‘change saturation’ or ‘change collision’ that are not substantiated by hard data.
To be at the decision table in planning effectively for change, the Portfolio Change Manager needs to be equipped with data to aid insight and decision making. How? By building an integrated view of change impacts. Currently, a lot of organizations still use a series of disjointed spreadsheets to try and articulate the change impacts across initiatives. The problem with this is is that:
The data is based on a person’s judgment in terms of whether an initiative has high, medium or low impacts, and not linked to structured impact assessments
The three categories of high, medium and low are mostly inadequate when the organization is going through a significant number of initiatives. Each category could include such a big range of impacts that it may not be precise enough for the business to use this data. Can the business use this data to forecast frontline impact and resourcing levels? Definitely no.
The spreadsheet is also extremely manual, consuming significant time. And it also becomes out of date very quickly and so may not be trusted by senior leaders or the PMO. Large companies often have more than 100 initiatives. At this scale, a manual spreadsheet is inadequate to meet business needs.
To address this problem, The Change Compass is a digital tool designed to make it easier for the Change Portfolio Manager or the PMO to piece together all the change impacts across change initiatives. Each initiative owner inputs change impact data and the system prompts the user to update the data. The interface is intuitive and draws out the impacts step by step. The Portfolio Change Manager and other managers are able to instantly generate various reports. In a nutshell it helps the organization to manage the ‘air traffic control’ of landing initiatives. Moreover, it enables:
Single view of change impacts on the business, and allows diagnostic view at different organizational levels, e.g. team, sub-division, divisional and enterprise levels
Forecast business operations readiness and resourcing impacts from changes, e.g. frontline resourcing required, engagement channels required, stakeholder groups impacted, etc.
Measure/Model impact of changes on business performance indicators. Understand correlation between change impact and customer satisfaction, service availability or other measures
View integrated heat map of all change impacts on customer experience, customer segment by customer segment
Build business change capability through change data and effective routines
Upgrade change work to become more strategic, leveraging data to have strategic conversations and support data-based business decision making
Support agile ways of working through managing iterative and continuous change across the board
To check out our article on how to better manage a change portfolio click here.
5) Change Governance
The Portfolio Change Manager should work with the PMO and senior managers to ensure the appropriate governance and routines are designed and set up. To do this, analyse the business requirements in connecting different stakeholder groups to ensure alignment, buy-in, visibility and ownership of the initiative slate. Portfolio change governance bodies should include attendance by PMO, senior business leaders and the Portfolio Change Manager should focus on reporting and tracking on business impacts, business readiness, delivery milestones and delivery risk identification and mitigation.
Typical routines that the Portfolio Change Manager should assist in establishing include:
Business unit level change planning and cadence (focused on initiative delivery)
Business unit level change capability and program intervention planning and tracking (focused on change maturity)
Initiative portfolio level planning, risk management and tracking
Change team meeting
As needed, enterprise level change planning and cadence
6) Change metrics and reporting
Whilst change impact data is critical to support the work of change governance bodies, there are other initiative-level metrics that the Portfolio Change Manager needs to be focused on in tracking and reporting. These include:
Change readiness surveys
Learning and development tracking and results
Communication metrics such as hit rate or readership rate
Stakeholder confidence ratings
7) Methodology & tools
Currently, there is a significant trend of moving towards agile project methodology in most large organizations. This means that there are less focus and reliance on documentation, long planning cycles but more on effective conversations, stakeholder alignment, and constant iteration and learning. On top of this, a lot of organization are also moving toward scaled agile methodology (agile at organizational level vs. within an initiative). The Portfolio Change Manager needs to define key change deliverables and work approaches that suit his/her organization (acknowledging that agile may not suit every organization or every initiative).
Having effective change tools means that the business can self-help and the change practitioner can better coach and develop the business. For the Portfolio Change Manager useful tools may include:
Change scoping assessment tool for initiatives
Change resource estimation tool
Change Impact Assessment template/tool
Change plan template. For agile environments this would be the Change Canvas
Capability and skills assessment
Change readiness assessment
Change framework for the business to help uplift change capability. This should focus on key change outcomes and competencies for any change leader, written in a language they can understand
The Portfolio Change Manager is tasked with a complex set of tasks in driving a set of change initiatives for the organization. He/she needs to have the people skills to influence a range of stakeholders to transition to the new state. In addition, the person needs to possess business acumen and analytical skills to support the PMO and senior managers to make the right decisions to drive change across initiatives. Whilst not exhaustive, this guide calls out key critical areas undertaken by the Portfolio Change Manager. To be successful going forward, the Portfolio Change Manager needs to constantly deliver value and provide insight through leveraging digital tools and hard data to be at the decision-making table.
A lot of organizations are increasingly focused on improving overall change maturity. Rather than simply executing projects on an ad hoc basis, organizations are realizing that building change capability is not only necessary but also, can be a competitive advantage. More mature organizations are able to respond to market forces and implement strategies faster and more effectively.
The 2 most popular change maturity models are 1) the Change Management Institute (CMI) Change Maturity Model, and 2) Prosci’s Change Management Maturity Model. Both of these models are centred around 5 levels of maturity. These 5 levels are organizational competency levels. In the following, we will look briefly at each of the models.
A. CMI Change Maturity Model
The Change Management Institute (CMI) Change Maturity model is based on 3 functional levels where maturity may be built. This includes project change management, business change readiness and strategic change leadership. There are 5 maturity levels in each of these functions, starting from Level 1 which is considered foundational, though to Level 5 which is the most advanced. This is a very useful maturity model as it postulates that to build effective change maturity one needs to focus on not just project execution, but also building change capability and readiness within the business. It also calls out change leadership and governance is also critical in driving change maturity.
B. Prosci Change Maturity Model
The Prosci change maturity model is based on a generic model of change management competency for an organization without specific reference to particular functional areas per se. The model references mainly the areas around project execution, business capability and readiness, and senior change leadership. A key part of change maturity is a formalized set of change management practices including wide-spread organizational acknowledgment and formalized methodology. A central part of increasing maturity is change management training.
Both models refer to project, business and change leadership elements in driving change maturity. However, the CMI model has a broader acknowledgment around the importance of agile, continuous improvement as a sign of maturity. Another part of maturity is developing the right cadence, business processes, and governance. Whereas, for the Prosci model, there is less specific coverage in truly embedding change practices within the organization through the abovementioned supporting processes. There is also a very strong focus on implementing initiatives.
What is missing in the current change maturity models?
The gap in the current change maturity models is in truly embedding change management principles and practices within the organization. Embedding change management within the organizations is not just about driving all that is necessary to implement initiatives. It is also not just about building change capabilities to support initiatives in leaders and employees. It is about working with various functions across the organization to embed change management principles and practices. This includes wide-ranging functions or departments such as Risk Management, Marketing, Strategy and Human Resources.
By working with different parts of the organization, we start to build change capability holistically. Again, this is not just about individual capabilities. It is also about the ability to apply change management principles and practices within different functional areas. When this happens across the organization, we start to have practices, capabilities and supporting processes and structures to support continuous change.
In the below, we examine examples of how change management principles and practices may be embedded and applied within 7 functions, including Risk Management, Strategy, and planning, Operations, Project Management, Human Resources, Technology, and Marketing.
1. Risk Management
How are change management principles and practices applied in risk management? Risk management includes the assessment of change risks. This includes a variety of risks such as the ability execute changes, the pace of changes as well as the magnitude of changes.
Risk professionals may be able to leverage from change management analytics to make data-based risk assessments. This includes analytics such as business readiness indicators. However, even more valuable, would be the level of change impact on the organization and customers. Armed with change impact data, the risk professional is able to make data-based assessments and better support the business in understanding risk profiles. Through this, the business can also make better decisions. For example, with significant change impacts and limited change capacity, this may significantly increase the risk profile for successful business execution and performance.
2. Strategy and planning
Strategy formulation is usually focused on meeting industry and environmental challenges in reaching organizational goals. Often, this involves trends and data such as financial and other organizational data. A key part of strategy formulation should also be taking into account change capability of the organization. This includes the availability of change leadership talent at different levels within the organization. The capability of strategy execution, including the ability to execute at the level of change velocity and change volume as designed in the strategy.
Strategic roadmaps should take into account historical data on how the organization has executed particular volumes and velocity of change. For example, with The Change Compass, strategy practitioners may analyze historical business performance factors and the respective change impact volumes and pace over time. Insight from this data is critical in effective planning. There is often very different data set with different parts of the business. It could be that a more change mature part of the business is able to undergo a higher volume of change and still meet performance targets, whilst another business unit struggles under similar change volume.
Effective strategy execution planning should also take into account supporting structures and processes required in successful execution. These include governance structures, reporting, cadence, and even communities of practice. All of these can be effectively designed to build successful change execution.
Change Management is a core part of Operations. Therefore, there are lots of natural opportunities to leverage change best practices within Operations. This includes building change management capabilities in employees and managers. It also includes building effective employee engagement channels, as well as effective learning and development mechanisms.
With the right change data and analytics, Operations is able to effectively plan for business delivery. For example, with analytics from The Change Compass, Operations may be able to make predictive assessment of the impact on business performance as a result of change impacts forecasted. Historical data on change impact levels and performance results become powerful predictors of future performance. Key decision making will then need to balance the need to drive change velocity, benefits targeted, and balancing business performance.
How this analysis and decision-making process becomes systematized and embedded within the operating cadence is key. Those Operations functions that have built in the right processes are able to generate better insights and better decisions. They are also able to have more valuable conversations on change capacity, change maturity, and business performance management.
4. Project Management
This is probably the most understood of all functions in terms of the role of change management. Most large organizations have change managers delivering various projects. Some have portfolio change managers and even enterprise change manager role. Most parts of change management work as represented in this function, including change capability building, change methodology, portfolio management, and project delivery.
5. Human Resources
Human Resources is another area where there is a natural application of change management. Change Management professionals sometimes report to the Human Resources function. Human Resources Managers and Business Partners are also increasingly tasked with leading and supporting the people side of change.
Building change management capability is often a key part of a learning and development function. Training courses, as well as change management frameworks, are devised to support people leaders or those impacted by change. Counselling and career advice are typical support services for those whose jobs are impacted by change.
However, there is significant value in managing restructuring initiatives as a change project where typical change management rigour is applied. This includes change impact assessment, change plan, stakeholder analysis, etc. A structured approach will avoid significant failings such as insufficiently engaging impacted stakeholders or inadequately mapping out processes, systems, and supporting structures impacted by the change.
Project change management professionals sometimes report to Technology business units in undertaking change support for technology projects. However, the value of change can extend beyond this. Often only large projects are staffed with change support. A significant portion of technology changes impact stakeholders and/or users. However, due to the lack of change management skills organizations often experienced badly implemented technology initiatives that fail to consider user and stakeholder impacts.
There is also opportunity to leverage organizational change management practices in technical change management. With the right organizational change management data analytics, the technical release management function may better releases and deployments. Technical releases have organizational implications and the two disciplines can be better linked for better planning. For example, with quantitative change impact data, there can be longer-term planning on when technical releases will make sense, taking into account organizational impacts.
7. Marketing and customer experience
Change management practices of analyzing customer change impacts should be a key component of Marketing and customer experience professionals. With effective stakeholder alignment and engagement the Marketing function can also better line up the organization around the external positioning of the company and what it stands for. Marketing campaigns, product launches, and communications should also embed standard change management practices such as impact assessment, change analytics, change loading analysis, and change planning. In this way, the organization can truly work towards becoming what it is touting to the customer.
Organizations often claim that the customer is their number one focus. However, how many organizations truly have an integrated view of the various change impacts on the customer? This should take into account both the changes the organization is driving as well as other changes the customer may be undergoing with market or industry changes or trends.
This article has outlined some examples of how change management principles and practices may be applied to a range of functions to help develop the overall change maturity of the whole organization. Change maturity is not just about developing stand-alone methodologies for projects and managers. It is not just about supporting the delivery of initiatives. The value of change in its most mature state comes when it is truly embedded within various parts of the organization.
A typical scenario for a lot of program meetings goes something like this. The program spends the bulk of the time discussing program cost, delivery progress, technical risks and resourcing challenges. And when it comes to Change Management reporting, we are often left with a few anecdotes from stakeholder interviews, and often the only real quantitative reporting comes in the forms of training completion, readiness surveys and email communications hit rates.
One wonders why Change Management is often glossed over as fluffy and soft vs. strategic and quantitative. Even for those who intuitively believe that managing change ought to be important, most lack quantitative data that demonstrate clearly how change progress directly impacts business outcomes.
How does a business manager, program or a change practitioner demonstrate the true strategic value of tracking change initiatives in order to highlight any risks and achievements? In particular with a group of initiatives.
Here are a few ways in which change impacts may be captured and reported in a quantitative way to support strategic decision making, starting with a birds-eye-view and sequentially drill down deeper to understand the scenario to aid strategic decisions:
1. Customer Experience Impact
One of the most profound ways in which change progress may be reported at a strategic level is by the extent to which initiative change impacts are shaping customer experiences. How are customer experiences shaped as a result of the suite of changes taking place?
Do initiatives result in positive or negative impact on customer experience? E.g. does it improve or worsen a service delivery speed, functionality, quality, etc. Legislative initiatives for example may result in negative experiences depending on the nature of the change.
Is there too much change going on at the same time?
Does the customer give a damn about the change?
2. Change Impact dashboard
A good high-level view of various change impact data for an executive dashboard may include:
Initiative quantity and type (technology, product, policy, etc.) throughout the calendar year
Impact level and type (go-live, training, customer, etc.)
At-a-glance pie charts and bar graphs are ideal for summarizing multiple axes of data within a 1-pager
3. Change impact heat map
A good heatmap can be one of the most visually memorable reports on change impact with options to drill down into colour-coded divisional and sub-divisional impacts across the timeline indicating both the number of initiatives as well as the levels of impact.
4. Detailed initiative schedule
A detailed initiative schedule is helpful as we start to drill down to analyze which initiatives are contributing to business and delivery risks. Data may include initiative names, impact level, impact type, and impact dates across the calendar year. One starts to get a detailed understanding of which initiatives are high impact, contributing to change fatigue or could be better-communicated in-synchronisation with other initiatives to reduce complexity for the audience.
5. Initiative report
After we have a clear understanding of the initiatives that we need to work on aligning to improve the overall execution and delivery effectiveness we then move to clarify the details of each initiative. At this level, the reporting contains a description of the initiative, contact persons, delivery timeline and business impact data. The report, therefore, should contain sufficient details to allow very actionable steps to connect, discuss, and plan for change alignment between initiative, portfolio and business owners.