Professional Documents
Culture Documents
Management
Framework
Please note the best way to obtain current information and up to date tools and
examples is through the Change and Project Management Framework website which
is available on Diageo Academy (www.diageoacademy.com)
Page 1 of 176
Contents
Contents .................................................................................................................. 2
Introduction ............................................................................................................. 4
Getting Started ........................................................................................................ 5
Tool Overview.......................................................................................................... 8
Thinking Strategically .............................................................................................. 11
T11 Possibility - Issue Identification .................................................................. 12
Issue Identification Tool.................................................................................... 15
T12 Project Definition ....................................................................................... 17
Project Definition Tool ...................................................................................... 19
T13 - From To ................................................................................................... 28
From To Tool ................................................................................................... 30
T22 Workflows and Swimlanes ......................................................................... 31
Sample Swimlane Diagram .............................................................................. 34
T26 - Change Impact Assessment ....................................................................... 36
T26 (Tool I) - Predicting the Impact of Change ................................................. 37
Predicting the Impact of Change Tool .............................................................. 39
T26 (Tool II) - Implementation Experience Assessment ................................... 40
Implementation Experience Assessment Tool .................................................. 42
T32 - Project Closure Document .......................................................................... 43
Project Closure Document Tool........................................................................ 46
Managing the Project .............................................................................................. 50
T14 Governance & Sponsorship Plan ............................................................... 51
T17 Project Plan ............................................................................................... 57
Project Plan Tool .............................................................................................. 61
T18 Project Administration ................................................................................ 62
T19 - Risk Management....................................................................................... 67
T20 Project Dashboard ..................................................................................... 72
T21 Stage Gate Checklist ................................................................................. 75
Stage Gate Checklist Tool ................................................................................ 78
T30 Project Change Control.............................................................................. 79
Project Change Control Tool ............................................................................ 82
Managing the Change ............................................................................................. 89
T15 Leadership Assessment ............................................................................ 91
Leadership Assessment Tool ........................................................................... 93
T16 One Minute Communication ...................................................................... 94
One Minute Communications Tool ................................................................... 98
T23 Change Resistance ................................................................................... 99
T23 (Tool I) - Change Resistance Scale ......................................................... 101
T23 (Tool I) - Change Resistance Scale ......................................................... 103
T23 (Tool II) - The Change Curve................................................................... 104
T23 (Tool III) - Diagnosing Commitment ......................................................... 109
T24 Culture Assessment................................................................................. 112
T24 (Tool I) - Culture Mapping ....................................................................... 113
T24 (Tool II) - Culture Web ............................................................................. 116
T24 (Tool III) - Quinns Organisational Culture Model ..................................... 124
T24 (Tool III) Quinns Organisational Culture Model .................................... 127
Page 2 of 176
Page 3 of 176
Introduction
If you are about to embark on a project or business change programme, no matter
the size, this framework will provide you with the tools and guidance you need to
ensure brilliant execution.
The framework was developed using the best of the many processes and tools
existing in Diageo for managing change and projects. A small cross functional
project team undertook the challenging task of simplifying both the processes and
tools to ensure global - cross function and market relevance; simplified instruction
guides and templates; and easy access for everyone regardless of location in
Diageo.
Analyse
Design
Implement
Launch the solution and execute the change; stabilise the change
and confirm that the desired outcome has been reached.
Sustain
This may all sound logical and easy! The reality is that many people struggle in
juggling all the different aspects that are involved in brilliantly executing a project to
scope, cost, timescale and with consideration for the people impacted. This
framework has been created to assist you in covering all aspects of project and
change management to ensure quality delivery in a simplified way.
Page 4 of 176
Getting Started
Getting involved in a business change project for the first time, or indeed for the
twentieth, can be daunting. To help alleviate any fears and to give you a great
starting position, following is a simple overview to help you get started!
The good news is that much of what needs to be done to make a project successful
is for the most part common sense. Further good news is that you will have plenty of
personal experience to draw from already changes you have experienced at work,
or changes you have made in your personal life. Finally you have this tool kit which
will guide you through what you need to do and when.
There are three key reasons why most business changes are not successful. So
ensure you have these aspects covered and you are a long way there in delivering a
great project! The three key reasons for unsuccessful or only partly successful
changes are: No clear definition of the issue failing to understand the purpose of the
change
Lack of Sponsorship lack of alignment and leadership to make the change
happen
Failure to understand the cultural implications all change is personal to the
people affected. It is part of basic human nature that the initial response to any
change is to react against it, so in making change happen and then sustaining
the change, it is essential to help all those affected get through the intellectual
and emotional concerns that they have about the change being made
What you are doing in the five stages of the change and project management
process can be phrased simply:
Initiate is about understanding the issue and finding out if it is important
Analyse is about deciding on the best solution and organising resources to
make it happen
Design is about getting to exactly what we are going to make happen and
how we are going to do it creating a great plan
Implement is about getting everyone to help to deliver the plan making the
solution everyones solution
Sustain is about keeping the change going and making it a normal part of
everyones day to day life
Before you start it is a good idea to look at all the tools briefly, so you know what is
there to help you. As you go through your change it is worthwhile looking at each
tool in more detail to see how it may help you some tools will not be appropriate,
and it is perfectly OK not to use them; for others you may see the need for them, but
they will not be quite right, again it is perfectly acceptable to modify them a little to fit
them to your change.
Page 5 of 176
Change can be daunting. If you are facing a particular challenge, it is likely a tool will
help with your thinking and to tackle each challenge as they arise. Below are some
examples of how the tools in the toolkit may be able to help you:
Question / problem
Tool to use
Page 6 of 176
The Tools
Page 7 of 176
Tool Overview
There are 22 tools included in the framework. They combine both change and
project management aspects.
To help you in thinking through the purpose of the tools, they have been categorised:
Thinking Strategically
These tools are designed to ensure you complete the right thinking in linking your
project with business strategy and need.
Managing the Project
These tools provide the structure in which to manage your project to budget, scope
and timeline.
Managing the Change
These tools provide the means in which to ensure anyone impacted by the change,
engages with the change and delivers the business benefits of the change
It is the combination of all 3 which will ensure the brilliant execution of your project.
All tools should be viewed of equal importance in managing the project you are
undertaking. Where you have individuals within a project team with certain capability
strengths, you may look to split the completion of tools (eg where you have a project
or change manager).
Page 8 of 176
Tool Ratings
Each tool has been rated:
Easy (green)
Intermediate (blue)
Difficult seek coaching (black)
Tool Structure
The guide for each tool is split into the following sections to ensure you gain a quick
overview to the tool and how to use it and also quickly identify links between tools.
Rating how hard is it?
Purpose why use the tool?
Outcome what you will gain from using the tool?
Structure How to use the tool?
Tips Handy hints in how to use/ complete the tool?
Interdependencies What tools/ materials will help you in completion and what
tools the outputs might feed into.
How to Learn More Where possible extra links to additional information that
may help you have been provided.
Although you have an excellent portfolio of tools to help you in managing your
project, this is only 20% of the job! The thinking and processes you complete are
where you will make or break your project, completing tools as a tick a box exercise
will not ensure your brilliant execution. Ensure you take the time to reflect on the
outputs of the tools you complete and what the real impact on your project is.
Page 9 of 176
Thinking Strategically
Page 10 of 176
Thinking Strategically
These tools are designed to ensure you complete the right thinking in linking your
project with business strategy and need.
Tool
T11
T12
T13
T22
T26
T32
Tool Guide
Possibility - Issue Identification
Phases
A list of questions to help understand the current issue/ challenge, and a frame
of thinking to reach what is possible
OR
Open the mind and cover all the angles
Project Definition
Summarises the scope, objectives, plan, and outcomes for the project to gain
alignment
or
What are we doing written down and signed off
From To
A way to understand the end state that we are aiming for as a result of the
change, and through that, the business and cultural implications and size of
change
OR
Where we start from and where we are going
Page 11 of 176
Rating
Blue - Intermediate
Purpose
To understand the current challenge and the possibilities of the idea, with the
Sponsor in a structured way.
Outcome
Structure
Completed by the Project Manager with the Sponsor during a conversation in the
initiation phase.
Issue Identification
Page 12 of 176
Process
Identify at least the 2 or 3 useful questions from each section of the checklist.
Establish critical elements such as performance promises, targets or behaviours
that should be retained through this change.
Regularly during the conversation use summaries and propose linkages to help
the Sponsor see the issue holistically and generate new insights.
Be prepared to take on resistance.
After the conversation synthesise the information and formulate your own
recommendations.
Schedule a follow up meeting with the Sponsor to align the output and
recommendations and to determine feasibility of engaging potential Stakeholders
(if deemed necessary).
If you agree to engage a wider group, undertake further research/benchmarking
as appropriate.
Business as Usual
New Reality
REALITY
Crisis
Destination 2011
LOW
POSSIBILITY
HIGH
Vertical axis reality: high we know the environment were in; and low - we
dont.
The horizontal axis is possibility, from low to high. When sitting in business
where we know the market, know our people, brands, global growth drivers etc,
we know what works & options available to us are well understood lets call that
business as usual (BAU). This is high reality / low possibility.
In BAU were comfortable, we know the environment it can be a fantastic place
to be.
For some people right now that place is high double digit growth, for others its
low growth but its still BAU.
When things shift, a market becomes less certain, customers change,
government introduces changes that influence our trade, our sense of reality, of
Page 13 of 176
knowing starts to drop. That can take us into a territory well call crisis. This is
low reality/low possibility.
The options available are still narrow, youre still working off the same kind of
thinking you had in BAU what could that lead to?
The markets open, you dont have a fixed view, things are uncertain/changing
but there are lots of possibilities open to you, lets call that thinking the
unthinkable. This is low reality/high possibility. The challenge is to make that
the new reality - understand it, learn to live with it, it has a lot more possibility than
BAU.
When crisis happens, we need to think quickly about our options thinking the
unthinkable. Thats where you go from crisis. Eventually you get used to it and
that becomes the new BAU.
Some people believe you have to go through crisis to get to new thinking thats
a lot of pain to get you to open up new thinking. How else can we prompt
ourselves into that place without having to crash into crisis? What if we move
straight to unthinkable?
Thats the capability we are building - D2011 is Diageo thinking the unthinkable at
a time when our BAU model is in great shape.
Interdependencies
Take insights from:
Tips
Page 14 of 176
General Questions
Strategy
Page 15 of 176
People
Process
Culture
Structure
To what extent will the current structure support or hinder your proposal?
How consistent is this with the existing operating model?
Where does the organisation need to flex to accommodate this?
To what extent will the informal network support or hinder this?
How dependent is this on the current incumbents in the structure?
What has been the history/ success of structural change in the past?
How have others organised themselves to address similar issues?
What are the implications for leadership, teamwork and decision-making?
Page 16 of 176
Rating
Blue - Intermediate
Purpose
The purpose of the Project Definition (PD) is to provide a clear and complete
description of the project. It is the primary foundation defining the outcomes,
objectives, scope, costs, and timeline of the effort. It defines the commitments of the
team to deliver the results. It is used to drive alignment of exactly what the project is
expected to deliver, and to serve as a baseline against which the success of the
project is measured.
Outcome
Aligned definition of the purpose and desired outcomes, scope, costs, and
timeline for the project.
Funding secured to execute the project or the project stage.
Baseline against which to measure the success of the project on its completion.
Communication of the scope and objectives of the project to drive understanding.
Structure
Page 17 of 176
Interdependencies
Take insights from:
Tips
Page 18 of 176
Sponsor
Name
Title
Instructions:
Red text is Instructions and/or examples.
Please erase any red text before publishing; as this text is not intended to be part of the permanent
document.
Please do a Find and Replace of <<Project Name Here>>
with the specific name of this Project eg Diageo Way of Selling.
Page 19 of 176
Document Administration
Purpose
The purpose of this document is to provide a clear description of the project.
It is a:
Single document summarising the project.
Confirmation of the scope, objectives and deliverables of the project.
It is used:
To obtain alignment of the purpose and desired outcomes for the project.
As an aid to communication both inside and outside the project.
To obtain financial approval in many cases (possibly in addition to other documents).
As a basis for subsequent planning and future project phases.
To measure the success of the project on its completion.
Revision History
Version
Revision Date
Purpose
0.1
dd-mmm-yyyy
1.x
dd-mmm-yyyy
2.x
dd-mmm-yyyy
Main Changes
Contributor
The following have contributed to this document:
Name
Role
Project Manager
Contribution
Author
Approvers
This document requires the following approvals:
Name
Title
Role
Sponsor
Signature/Date
Page 20 of 176
Table of Contents
1.
Project Overview ........................................................................................................4
1.1. Background ................................................................................................................4
1.2. Project Description and Scope ..................................................................................4
1.2.1. In-Scope .....................................................................................................................4
1.2.2. Out of Scope ..............................................................................................................4
2.
Project Costs
4
2.1. Project Financials .......................................................................................................4
3.
Business Benefits.......................................................................................................5
3.1. Anticipated Business Outcomes ...............................................................................5
3.2. Project Objectives ......................................................................................................5
3.3. Fit with Strategy .........................................................................................................5
3.4. Impact of Not Doing this Project................................................................................5
3.5. Alternatives Considered.............................................................................................5
4.
Interdependencies......................................................................................................5
5.
Assumptions ...............................................................................................................6
6.
Key Risks ....................................................................................................................6
7.
High Level Milestones ................................................................................................7
8.
Project Governance ...................................................................................................7
9.
Requirements .............................................................................................................8
10.
Technology Considerations .......................................................................................8
Page 21 of 176
Project Overview
Background
Provide salient background to the project. What is the problem? Why has it come
about and how did we get here? A paragraph or a few bullet points is usually
sufficient.
Answer here.
Project Description and Scope
Provide a brief overview of the solution. Avoid repeating details found in other
sections of this document.
Answer here (description):
In-Scope
Outline the proposed scope. Bullets usually work best.
Answer here:
Item 1
Item 2
Out of Scope
Saying whats out-of-scope often adds clarity and removes ambiguity. Bullets
usually work best.
Answer here:
Item 1
Item 2
Page 22 of 176
Project Costs
Project Financials
Include a summary of project financials using the format required by your finance
organisation here. Your finance organisation may require additional information to be
embedded here as well. In absence of other financial guidance, include the following
information:
Fiscal Year: F10
Category
Labour / Resources
Internal (if applicable)
External (contractors)
Vendor Costs
List each vendor separately
Vendor #2
Other Costs
Itemise (training, hardware, software,
equipment, etc.)
T&E
Contingency
Revenue
Capital
Total
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Page 23 of 176
Business Benefits
Anticipated Business Outcomes
Articulate the business outcomes both quantitatively and qualitatively. Your function
may have specific guidelines about categories to include here. A table format usually
works best.
Answer here.
Project Objectives
Include not only what we are trying to achieve, but how well know when we get there
Objective
Alternatives Considered
Are there other or lower-cost alternatives that were explored? Explain those here.
Interdependencies
Project / Initiative
Dependency
Page 24 of 176
Assumptions
What are your assumptions? - Diageo business locations, Skills needed and
availability, Organisations engaged, Partner/vendor engagement, Deliverables and
activities to be delivered - Whats the impact if this assumption is wrong?
(High/Medium/Low)
Assumption
Risk?
H/M/L
Key Risks
Your project may develop a separate Risk Management Plan to detail the risk
approach, footprint, and mitigation plans. If so, refer to or embed that here instead.
The following risk footprint highlights key risks facing the project:
1. Manageable
2. Major
3. Critical
Risk Profile
(D) medium
(G) High
(I) CRITICAL
(B) low
(E) medium
(H) High
(A) low
(C) low
(F) medium
Remote
(<10%)
Possible
(10-50%)
Likely
(>50%)
Likelihood
#
1
Business Risk
Description
Key resource not
available
Mitigation Plans
(risks may have >1 mitigation)
Approach
Category
Mitigation
Owner
Acceptance
Jane Doe
2
3
4
5
Page 25 of 176
Milestones
Most projects will develop a robust project plan (T17) indicating what gets done when
by whom. These milestones should be lifted from that plan. You may also wish to
embed that plan with those details here.
The key milestones for this project as are follows:
Milestone
Date
Project Governance
Information in this section should derive from the Project Governance Planning.
The following key project and steering body resources are responsible for moving the
project forward during its early stages through the Analyse Phase:
Steering Committee
Role
Sponsor
Lead Stakeholder #1
Lead Stakeholder #2
Other key leaders
Name
Title
Name
Title
Project Team
Role
Project Manager
Change Manager
Project Team Member
Page 26 of 176
Requirements
Ensure you capture all types of requirements, such as: functional, legal, CARM,
language, locations, user population, training, data, information, access, security,
technical, back-ups, and support. At a minimum, complete the following summary.
Where appropriate, develop in-depth requirements capturing functional (what the
solution does) and non-functional (how it does it, e.g., response time and user
interface) requirements.
Category
Description Summary
Impact on
Existing
(H/M/L)
Technology Considerations
Many change efforts are dependent on technology. If so, include the technology
considerations or assumptions here. Information such as an IS logical architecture
may be necessary for complex technology-driven change projects. Diagrams are
often used here.
Answer here:
Page 27 of 176
T13 - From To
A way to understand the end state that we are aiming for as a result of the change,
and through that, the business and cultural implications and size of change
or
Where we start from and where we are going
Rating
Green Easy
Purpose
To understand the implications of change and to capture the essence of the
proposed change.
Outcome
Detailed understanding of current and future states, implications, and the size or
scale of change involved.
Clear measures of success for the change and identification of the gaps to be
closed to reach the desired end state.
Structure
The format of the From - To Tool follows the key elements of the Issue
Identification tool - Strategy, People, Process, Culture and Structure.
Review the Issue Identification and any Sponsor or Stakeholder feedback and
identify the key behaviours, processes and structures that will need to change.
Capture the essence of each element of the change in a few words.
Identify how you will measure the change - what will new performance look like?
Start to define the KPIs (Key Performance Indicators).
Identify the gap to close in order to reach the end state - think also about
barriers or blockages that would prevent the end state being achieved.
Summarise the outcomes and review with Sponsor.
Interdependencies
Take insights from:
Page 28 of 176
Tips
The tool is started and built primarily during the Initiate phase, but is relevant and
useful throughout the change so keep it up to date.
The changes captured on the tool should reflect building on strengths, rather than
only addressing negatives.
It is absolutely appropriate to capture things that you do not want to change on
this tool the From and To will be the same, and identifying how you measure
this will drive one of the KPIs you monitor through the change.
Capture the essence of the change in as few words as you can and using as
simple language as you can.
It may be difficult to categorise the change across the headings (Strategy etc) in
the early stages do not be too concerned about this, capture the essence of the
change required and revise later.
Be open to and strive for possibility. Dont be constrained by your current
thinking Stretch your thinking to identify the greatest, most impactful possibility
or end state
Start in the To column this dares you to be different and will ensure your
thinking is not constrained by the current state.
The Measure column can be used to capture what you will observe or see as
different, as well as a Business KPI.
Be aware that measures can be affected by events or things other than the
change. Try to make them as specific as possible.
This exercise can be difficult to complete. Work on it in a way that you are
comfortable with (e.g. some people like to work alone, others like to work in a
group or supported by a facilitator).
Use narrative (tell stories) about how things will happen in the To world to enrich
descriptions and bring it to life (for example, start a narrative from An Operator
on the night shift spots a leak from a pipe and go on from there).
When building or reviewing this in a meeting, be sure to capture some of the
debate that leads to the final conclusion it will inform both the end state and
help you to understand how people will react and think about the change when
you communicate it.
There are many possible uses:
During informal or formal conversation with the Sponsor or Stakeholders
in order to understand the current challenges and future possibilities.
Mobilisation exercise with Project Team.
Page 29 of 176
From To Tool
FROM TO Tool
From
To
Measurements
Strategy
Will strategy need to
change for this?
People
List key groups of
people who will be
affected by the
change and think
about what it will
mean for each of
them.
Process
What processes will
need to change and
how?
Culture
Are there any
behaviours, beliefs,
assumptions that will
need to change to
allow this change to
be successful?
Structure
Clarity around what
the new structure will
need to be and the
implications.
Page 30 of 176
Rating
Black - Hard
Purpose
Workflows and swimlanes are diagrams that help document what work is done by
whom, Building these ensures:
Task sequences and dependencies to achieve a business outcome are
documented.
Accountabilities are clearly understood.
The people and organisations that are involved in delivering from the start to the
end outcome can be identified.
The hand off points are clearly defined.
Ways of working in the new model(s) are clearly understood.
Comparing the future-state workflows with the current ones allows the Project team
to understand the extent to which
People will have to do different things, for which they may need new capabilities.
Existing controls and ways of working will change.
Enterprise View
Process Area
Process Area
Process Group
Process
Process Area
Process Group
Process
Activity
Process
Activity
Page 31 of 176
Task
area of Order to Cash has several Level 2 process groups within in such as Create
Sales Order, Deliver Goods to Customer, and Create Customer Invoice. Each of
these is in turn broken down into Level 3 Processes, which in turn decompose into
Level 4 Activities, Level 5 Tasks, and down to Level 6 Steps.
For assistance with this framework and business process modelling, please contact
the IS Business Process Architecture group or your local Business Process Owner.
Lean: Lean is a way of reviewing processes with the goal of delivering value as
efficiently as possible by eliminating waste (either physical waste or non-value added
activities). Diageo is building capability of Lean and applying Lean principles to core
processes across the company.
Outcome
A summary (including a pictorial representation) that gives
A clear understanding of activity design/redesign.
Understanding of the impact of process changes.
Structure
Step 1
Identify the scope of the workflows that may be affected by your change.
Step 2
For each workflow area, you should:
Clearly articulate the scope
Whats the trigger that starts this workflow?
Whats the endpoint of this workflow?
These starts and ends are usually events
Use POSOM:
Identify the Purpose of the workflow what is it were trying to do? A crisp
one-sentence description is often sufficient.
Identify the Owner of the workflow who decides how this should be done?
Who has ultimate accountability for the work?
Put together the Structure of the workflow logically draw out who does
what in which sequence using a Swimlane format.
Be clear about the Outcomes make sure that the steps support clear
business outcomes.
Define Metrics to measure success of your workflow Think of SMART
(Specific, Measurable, Achievable, Relevant, and Timely) metrics that can
prove you workflow is achieving its desired outcome.
Make sure you are:
Clear whether you want to fix or improve an existing process to meet the
needs of the change or create a completely new process
Change & Project Management Booklet.doc
Last saved 03/12/2009
Page 32 of 176
Step 3
Identify and consult with people who understand the current process (e.g. the
process owner/ functional experts / the people doing the work) to:
Articulate and document the current state
Identify what is working/not working/issues/opportunities
Step 4
Search to identify existing solutions and experts in other locations (Search & Spin)
Set up Challenge and Build sessions with experts or groups of experts to:
Agree new process design
List all the implications of the new design on people and ways of working. This
will be used to create a clear transition plan
Consider leveraging process improvement methodologies such as Lean or the
Diageo Process Framework
Step 5
Use the results - your workflows/ swimlanes - to help build your solution (depending
on your project scope, the swimlanes may be the a large part of the solution youre
building), plan for implementation, and identify change needs.
Ensure you consider the capabilities required to carry out the steps this will input
into training and development plan for the individuals affected by the change.
Interdependencies:
Take insights from :
Provide input to :
T13 - From To
T11 Possibility Issue Identification
T12 - Project Definition
Diageo Process Framework
Tips
Workflow mapping via swimlanes is a great tool for local, non-IS work, but
building full process understanding is very complex. Get help in facilitating the
process and workshops. Someone who is experienced in this area and ideally
understands fully the Diageo methodology for Business Process Modelling best
facilitates
Ensure enough time is made available to do it, it needs to be thorough and
accurate for the detail needs to be fully understood and used properly.
Engage the right people. In addition to someone familiar with the techniques of
swimlanes and workflow analysis, you also need to engage with subject matter
experts who know how it really works, workflow owners who can decide how it
should work, and customers (internal or external) who can validate whats really
needed as a result of the process (business outcomes). Ideally, have the people
who actually do the process describe it and check that it has been correctly
documented
Page 33 of 176
If your change covers a lot of different processes, look to break the work into a
number of logical chunks (eg purchasing processes; selling processes; planning
processes) and organise teams to carry out the work with a central coordinator
Be consistent in briefing all process streams (if more than one) to establish
clear communication/ linkages ideally get them all in the same room at the
same time
Understand what actually happens, as well as what the process should be if we
stick to the rules. There can be significant differences between the two!
Suspend judgement and probe openly as to why a process is not done by the
book.
Recognise that the nature of this highly detailed work can be difficult to maintain
energy for it - ensure you have the right people and do the work in ways that
maximise their energy and inputs
The facilitator needs to help you to understand when you have too little detail and
when you have too much - know when youve got what you need
If looking to improve an existing process, first do an as-is swimlane of how it
actually works (not how its supposed to actually work).
Leverage other tools and methodologies to help in complex cases: Diageo
Process Framework, Business Process Modelling, and/or Lean.
Sales
Shared
Services
Send
request for
goods
Create Third
Party Sales
Order
Purchase
Requisition created
automatically
Create
Purchase
Order
Deliver
Goods to
Customer
Vendor
Receive
invoice for
payment
Receive
goods
Goods Despatched
Customer
Perform PO
Invoice
Receipt
POD
Create
Customer
Invoice
Send
Invoice to
Diageo
Each swimlane diagram must start with a triggering event and finish with an
outcome event.
The diagram flow is left to right, top to bottom.
Each row (swimlane) represents a specific role, group, or function that
performs the activities shown on that row. It should be formatted horizontally
with the lanes down the left side (this way is more understandable), with each
lane separated by a dotted line.
Ideally it should fit on to one page deep and no more than three pages
across.
Page 34 of 176
Manual
Task
Automatic System
Task
System Task
Use of decision diamonds is not necessary (you can just label the lines
coming out of the box with the decision), though can be added if they aid
understanding on lower-level diagrams.
Consider using live workshops to capture your initial workflows. Brown paper
and Post-It notes are great tools to help facilitate this.
A tool like Visio makes documenting and updating swimlane diagrams much
easier than using PowerPoint.
Page 35 of 176
Rating
Blue - Intermediate
Purpose
Outcome
Structure
Core Tools
Page 36 of 176
Rating
Blue - Intermediate
Purpose
To assess the perceived size of the change for a group or individuals and
understand to what degree the change will cause disruption.
To leverage positive energy towards the change initiative which may not have
been predicted.
To test the effectiveness of previous communications in relation to the change.
Outcome
Structure
Use with groups of people impacted or sponsors/team members with a good insight
to how people may be thinking.
Ensure group selected has a representative view
Split into groups of 3-5 (consider make up for dynamic or mix)
Individually complete form without conferring (this could be done in advance of
the meeting)
As a group quickly identify themes of high and low level responses and discuss
how these opportunities can be leveraged, or barriers overcome (capture on
flipchart)
Feedback between groups
Identify key actions and owners (capture on flipchart)
Interdependencies
Take insights from:
Change Resistance
Business Readiness
Risks and Issues log
Used to inform the change
communications
Page 37 of 176
Tips
Use once a change is understood by the group you are working with. This may
be after the Analyse phase or through to Implementation planning. This can also
be after a communication on the change if the reaction is not what you
expected, then the communication may have had an unintended impact
Use when resistance is encountered to surface reasons this can be a more
neutral way of understanding reaction than direct questioning
Decide which of the questions are the most crucial to the success of your change
initiative for each audience.
The discussion and rationale is more important than everyone agreeing where on
the scale the answer fits (so ensure that you leave enough time for this aspect)
Whilst facilitating this discussion, you may present information to people
impacted which they were previously unaware; be sensitive to this
Page 38 of 176
2.
3.
4.
The reasons for this change are clear and easy to understand
5.
6.
I have or can easily gain the knowledge and skills to implement this change
7.
8.
This change will not need me to alter my beliefs on how we conduct our
business how we deal with customers / employees, nature of business
9.
I will not need to feel differently about people or how the business works
10.
11.
12.
13.
14.
Agree
1
2
Disagree
3
4
5
Page 39 of 176
Rating
Blue - Intermediate
Purpose
To identify the experience which individuals impacted have had previous change
in the organisation. This will include areas, which went well (to repeat in the
current initiative) and problems faced (to mitigate against).
To identify the historic data which people have mentally stored about change in
Diageo.
Outcome
Awareness of the problems that may arise from insight into issues of past change
initiatives.
A matrix showing where previous practice has supported or inhibited change.
An action plan to build on the enablers and address areas of particular concern.
Increased engagement with the impacted individuals and stakeholders.
Structure
Interdependencies
Take insights from :
Provide input to :
Page 40 of 176
Tips
Page 41 of 176
10
11
12
13
Rigid policies have made it difficult to change ways in which things are done
14
15
16
17
18
People have expected change to be local and not affect other areas
19
20
Managers have said they support change but acted in the opposite way
21
People expect little from change initiatives due to poor track record
22
23
24
Managers focus was more on departmental image then achieving change goals
25
It was more important to agree with change than to express personal views
Disagree
Agree
Page 42 of 176
Rating
Green Easy
Purpose
Close out all elements of the project, including financials, milestones, resources,
achievement of key success criteria etc., to confirm that its okay to stand down
the project team.
Confirm handover plan for any open/undelivered elements/issues/actions to
whom, etc.
Confirm transition to Business As Usual (BAU) operations.
Assess project effectiveness and capture key lessons learned from the project.
Outcome
Page 43 of 176
Structure
Interdependencies
Take insights from:
Future projects
Tips
This document is most appropriate for repeatable projects, e.g. for those projects
that are part of a wider programme of work, and will be replicated across different
functions/regions, etc. This document should then be stored and used as input as
part of the Initiate Phase for future similar projects. For one-off projects, there
may be less value in the project assessment activities, although it is still
necessary to formally close the project.
Ideally, assessments of the project from the Sponsor/Project
Manager/Workstream Leads should be gathered prior to the project lessons
learned session, to frame the discussion.
When undertaking the lessons learned session, be clear about what drove
success or issues really understand why certain things happened smoothly or
were barriers to success ask Why? Why? Why?
Be clear about what actions will be taken as a result of the project lessons
learned review (who, how, when).
Be clear about who will be picking up any outstanding issues/tasks from the
project (who, how, when).
Aim to limit any successes/issues/actions to 5 each, so it is focussed on the
priority findings.
Any subjective analysis can be added into the document based on project
requirements, e.g. team performance, behavioural change, etc.
Consideration of exit criteria to confirm its okay to stand down the team and
transition to BAU post-warranty, including whether key success criteria for the
project has been met. N.B. This refers to success criteria that can be assessed
Page 44 of 176
immediately at the end of the project; any benefits that are anticipated further
down the line should be re-assessed as part of a full post-implementation review
(often 6 months or more after close of project).
Communicate the results of this analysis broadly dont just keep the results to
yourself and have it become shelfware. The value in this document is to learn
how to do this better next time.
Ensure there is an appropriate celebration of success linked to this being signedoff.
If you are involving a wider team to get replies make this as quick, simple and fun
as you can. Seventy questions on a survey will get low response and poorly
thought feedback.
Page 45 of 176
Date:
Project Title:
Sponsor:
Project Manager:
Workstream Leads:
Financial Analysis
Original
Budget
External
Expense
Capital
Approved
Budget
Recorded
Expense
Pending
Expenses
Projected
Expense
Variance
B/(W)
This project was / was not part of the AOP for fiscal year _______.
Schedule Analysis
Add and remove milestones as appropriate.
Original
Key Milestone
Completion Date
Gate 1 (Initiate)
dd-mmm-yyyy
Gate 2 (Analyse)
dd-mmm-yyyy
Gate 3 (Design)
dd-mmm-yyyy
Gate 4 (Implement)
dd-mmm-yyyy
Gate 5 (Sustain)
dd-mmm-yyyy
Approved
Completion Date
dd-mmm-yyyy
dd-mmm-yyyy
dd-mmm-yyyy
dd-mmm-yyyy
dd-mmm-yyyy
Actual
Completion Date
dd-mmm-yyyy
dd-mmm-yyyy
dd-mmm-yyyy
dd-mmm-yyyy
dd-mmm-yyyy
Staffing Analysis
FTEs
FTEs
Consultant
Original
Approved Plan Actual Days
Variance B/(W)
Plan
(Est.)
days
days
days
days
days
days
days
days
days
Page 46 of 176
days
days
days
From
Operating Scope
Strategy
To
Delvered
Green fill for fully
delivered
Product Offering
Headount
People
Process
Culture
Structure
Roles
Org Design
Skilling
Shift Pattern
Equipment Usage
Process Length
Distribution Model
Orientation
Perspective of
Organisation
Control Behaviour
Creative
Behaviour
Competitive
Behaviour
Management
Structure
CI Capability
Operating Teams
Routine
Maintenance
Cover
Rating
1 = poor,
5 = excellent
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
Comments
Page 47 of 176
Service
Quality and value of the
methodology
Availability of resources
Timely approvals from business
areas
Organizational support of project
Rating
1 = poor,
5 = excellent
1 2 3 4 5
Comments
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
Service
Rating
1 = poor,
5 = excellent
1 2 3 4 5
Comments
Page 48 of 176
Page 49 of 176
T17
T18
T19
T20
T21
T30
Tool Guide
Governance & Sponsorship Plan
Phases
Project Plan
Organise the details of what has to be done by whom and when in order to
achieve the business outcomes
OR
Who does what when?
Project Administration
Helps you organise the details you need to manage effectively
the administration a project
OR
Its not done til the paperworks done.
Risk Management
Monitoring and/or mitigating the events, actions or missed opportunities that
could impact the ability to meet objectives or achieve strategic goals
OR
What should I be careful of?
Project Dashboard
Reporting of the progress of the project plan, milestones, issues, and risks in a
concise one-page format
OR
Hows it going?
Page 50 of 176
Rating
Blue - Intermediate
Purpose
The role of Governance is to:
Create the environment for success through active leadership:
Agree and articulate the vision and scope for the change and its place in
the overall business strategy.
Resolve conflicts and roadblocks that affect the progress of the project.
Role model behaviours and commitment to the change.
Engage the wider business to support the project through its life.
Grant authority to execute the change:
Agree organisation, roles, accountabilities and responsibilities for the
change and sanction alterations, as they are required to progress the
project.
Make decisions that provide resource.
Set policy specific to the change.
Manage the risk associated with the change and mandate the level of risk to
be taken.
Manage the interdependencies with other changes and business activity,
setting priorities and arbitrating over issues.
Verify performance in the delivery of the change:
Confirm that appropriate policies and standards are being followed.
Drive the quality and speed of the change.
Outcome
The outcomes of Project Governance are to:
Increase project success and mitigate risk.
Drive accountability, speed and decision-making.
Drive effective & efficient use of resources.
Model behaviours and demonstrate leadership.
Structure
Success factors in creating and sustaining governance are:
Always have the most fitting leadership structure that will oversee the change.
Use ways of working that enable everyone in the project to be as effective as
possible over the life of the project, and hold people to account for delivering their
responsibilities.
Change & Project Management Booklet.doc
Last saved 03/12/2009
Page 51 of 176
Involve people who will actively and passionately lead and role model the right
behaviours to deliver brilliant results.
For small or lower impact changes the Sponsor may be able to meet all the demands
of governance.
Larger or more impactful changes will require a number of people to provide the
required authority and leadership to make the change happen. These people will take
on formal roles within the organisation of the project, known as the Governance
Structure.
In setting up project governance the output should be:
A structure chart that identifies the governing body(s); the roles within these and
the individuals filling those roles.
A program of meetings that enables the formal interaction to lead the project.
Agreed ways of working, both inside and outside of meetings, that covers each
aspect of the governance role.
Aligned and active leadership of the change.
Sustaining governance ensures that the structure and ways of working are always
appropriate to the needs of the project. The Governance structure for a large or
long-term project should be periodically reviewed, usually at the end of a phase and,
if necessary, adjusted to ensure it is relevant.
A simple governance structure may be based on a model that looks like this:
Steering Committee
Control
Authorities
Sponsor
Cascading
Sponsors
Project Manager
& Change
Agent
Project
Project
Project
Team
Team
Team
Whilst this simple model with one steering committee may work for driving some
projects, a more complex structure may be required if:
The breadth of affected elements of the organisation is too wide for one steering
committee to handle this would drive a more complex implementation of the
governance structure.
Page 52 of 176
The breadth of decisions to be made is too great for one team to reasonably be
able to handle (e.g. knowledge based technical issues; large scale organisation
and cultural impacts).
Specific elements of the change are highly confidential and need to be dealt with
by a small number of people.
Step 2
Sponsor/ Project Manager consults with identified individuals to understand their
position in respect of the change, and the effort they are willing and able to put
into making the change happen. This will drive whether:
The Stakeholder becomes a member of the Steering Committee.
The Stakeholder delegates his authority to another person to represent his
interests.
Step 3
Engage the Steering Committee through a kick off meeting that aligns on the
scope of the change, roles, and ways of working.
Ongoing review of governance is important. There should be a formal review
immediately following the successful passing of a gate into the next stage.
Page 53 of 176
Interdependencies
Take insights from:
Tips
Getting Started
Always, always, always use the T28 - Role Mapping tool to help determine who
should be in the governance structure.
The governance of any change should start small. It is ok in stage 1 to have just
one or two people overseeing the whole change.
A decision making body of more than 7 people has the potential to be
cumbersome and slow (unless they are experienced in working together). With a
very large program of change it simply may not be possible to restrict the number
of decision makers. In this case look for opportunities to create sub groups with
specific decision remits and tie these together in a smaller referral body.
Steering Committee make up
It is better for a Cascading Sponsor or Control Authority to delegate his position
on the steering committee and not have it removed. Rather than simply dictate
to a Stakeholder that your interest is too small, so you are not on the steering
committee, work with them to align on the best way for them to interact with the
project. For example, facilitate a discussion across similar Stakeholders so they
select one person to represent their interests (e.g. if a change impacts 6 sales
regions, get them to nominate one person to represent sales interests on the
steering committee).
Control Authorities with a narrow, specific interest (e.g. verifying that procedural
documents are compliant with standards) should not form part of the steering
committee. They should be engaged for a specific review at a point in time it is
helpful to show this on any summary of the governance structure and within the
project plan. Control Authorities who have a wider interest or are involved over a
long period of time should form part of the steering committee (e.g. financial
oversight).
Commentators should not have formal governance roles. It is essential to engage
them to get their views and foster their advocacy. This should be done through
specific engagement events. As a last resort, this can be done through
Change & Project Management Booklet.doc
Last saved 03/12/2009
Page 54 of 176
attendance at steering meetings, but the sponsor should carefully manage them,
so that they are not disruptive.
Whilst delegation is acceptable, abdication is not. A key individual or part of
the organisation not actively involved in the governance structure is a potential
cause of all sorts of trouble. Watch out for regular non-attendance of meetings or
the sending of a deputy with no decision-making authority as a sign of potential
abdication.
Page 55 of 176
Page 56 of 176
Rating
Blue - Intermediate
Purpose
The Project Plan documents what the project will do by whom and when, and then to
track progress. It is used to:
Document the tasks, steps, activities and deliverables that need to be
completed in order to deliver the desired change. It also documents when
each of these need to be completed and by whom.
Analyse key assumptions such as the approach to training, testing, or
implementation and reflect that analysis in the plan.
Align the project team to drive task ownership.
Communicate intent and timeline.
Provide visibility of sequence and prerequisites (what has to happen before
something else).
Monitor project progress over time.
Outcome
Structure
Although there are many different approaches to project planning available, a typical
approach is shown here. Consider using other approaches that may be more
applicable to your situation.
Step 1 - Assumption Planning
The first step in developing a good project plan is to document your major
assumptions. Much of this information can be gleaned from the Project Definition.
Assumptions to consider include:
Major timeline goals is there a date when this must be completed? Are there
other critical milestone dates that must be met? Externally imposed dates often
become major constraints on your project.
Skill availability similar to timeline constraints, resource/skill constraints can
also influence how you approach your planning. Will you use only internal
Change & Project Management Booklet.doc
Last saved 03/12/2009
Page 57 of 176
Schedule
Cost
Page 58 of 176
At the end of this step, youll have a first-cut of your project plan.
Step 3 - Alignment
Building on step 2, now spend time refining the plan youve drafted in order to build
alignment. Remember, the project plan is what youre asking people to sign-up to
do, so its important that the plan be as robust and accurate as possible, with broad
buy-in and support.
Confirm assumptions
Ask experts in a particular type of task to help validate your assumptions.
Ask people whove completed similar efforts in the past for their input &
experience.
Discuss with your sponsor the implications of your assumptions.
Validate the draft plan
Consider holding a challenge & build session with some experts as a way of
gathering input.
Include key stakeholders, sponsor, steering committee, or other groups as
appropriate to help ensure youve captured all the constraints.
You often need to hold multiple challenge and builds with different audiences.
Alternatively, you can use other ways of getting validation, including e-mail,
WebEx, etc.
Refine the plan
Incorporate the feedback on your assumptions & from your validation sessions.
You may need to do this repeatedly after each session or set of feedback.
Check alignment
Having alignment (not just agreement) around your project plan is critical to your
projects success. Through the plan, youre asking people to commit to
completing certain things by certain times. For resources you control directly, this
is relatively easy, but be especially sure for resources you dont directly control
(such as those borrowed from other functions).
Step 4 - Baseline The Plan
Once you have alignment around your initial plan, you need to create your baseline,
the plan fixed at a point in time. A baseline finalises the scope, timeline, resources,
and cost commitments. Use this baseline to understand and manage the changes to
the project going forward.
Communicate the plan ensuring everyone has the latest copy of the plan and starts
working toward achievement.
Step 5 - Monitoring & Tracking
A project plan is not a static document. It is used to track and monitor progress as
well.
Page 59 of 176
Track progress
On a regular (usually weekly) basis, gather input from everyone working against
the plan as to their progress.
Update the progress in the project plan.
Compare where overall the project team are to where we it is expected to be at
this point in time.
Take corrective action, if needed, by escalating the problem, and/ or creating a
change request to alter the baseline plan.
Publish the updated plan regularly
Ensure the team always knows whats expected of them and when.
Let everyone on the team see how everyone else is progressing.
Review changes to the plan and the implications with the team.
Interdependencies
Take insights from:
Tips
Scale the level of your project plan to the size of your team, duration of your
project, and risk involved. Large, inter-functional projects introducing large
change should have more rigour in their project plans than short local efforts.
Present your project plan in a way that best matches your audience. This may be
a simple list of activities, or some graphic such as a Gantt chart or timelines.
Project plans are living documents they not only capture what you expect to do,
but also form the baseline against which you measure your progress.
For advanced or complex projects, engage with a qualified project manager or
project analyst to develop and monitor the plan.
Dont forget to include a mechanism to track progress against your plan. This
could be done during a weekly team meeting, via an e-mail update, or having
everyone update their own progress directly in a shared copy of the plan.
Regularly remind people of what theyve been assigned to do in the coming
weeks and months. Look out for conflicts like holidays or vacations.
Depending on the scale and complexity of the project, the project plan may be
simple (a set of milestones and assignments) or complex (a complete Work
Breakdown Structure in a tool such as Microsoft Project with dependencies,
resourcing, etc.) But the project plan is more than just the schedule.
Good file management is essential to keep track of your plan. Ensure a copy of
the baseline is kept secure and unchangeable. Use a naming convention so your
files display in date order, eg DWSplanyymmdd.
Page 60 of 176
<<Project Name>>
Project Milestones Report
Com pleted by:
John Kivela
Reporting Period:
1-May-09
to
30-Aug-09
Overall
Green
This period
Red
Amber
Green
Complete
Removed
Added
Legend:
RED Off target, no plan in place
GREEN On Target
Expected
Com pletion
Date
Status
Com m ents
100
110
120
130
140
150
160
<<Stage Nam e or Header>>
200
210
220
230
240
250
260
270
280
<<Stage Nam e or Header>>
300
310
320
330
9999 End (Insert new row s above this one)
Page 61 of 176
Rating
Green - Easy
Purpose
This provides a set of basic project administration tools to help manage your project.
Tools included here include:
Contacts
Distribution lists
Project calendar
Meeting plans
Issues log
Risk log
Action items
Minor Change log
Outcome
Structure
Line up your project administration details as soon as you assemble your project
team.
Keep the various tabs up-to-date as the project progresses. Some sections may
remain relatively static, and others may change frequently.
Agree with your team how information will be maintained. Some teams will have
each person update their information on a shared copy of the file. Other teams
centralise the updates through single person.
Depending on your needs, you may add additional information or tabs to the base
workbook. Alternatively, you may omit some tools, or use alternate versions or
formats.
Instructions for individual tools are included in the following pages.
Page 62 of 176
Distribution Lists:
What its for:
Having a set of common distribution lists for sending out e-mails
Why you want it:
Makes sure you have included everyone!!
Tips:
Assign a central resource to maintain the lists.
Consider using features in Outlook to help manage the list.
Use fully qualified e-mail addresses (such as john.q.public@diageo.com)
separated by a; or a line break in order to ensure the lists copy and paste into
various e-mail systems easily.
Project Calendar:
What its for:
Having one place to go to see peoples macro-level availability all at once whos
on holiday, whos in training, etc.
Why you want it:
The cardinal rule of project planning is knowing who does what when. Without
knowing peoples availability you cant plan properly!
Tips:
Have each team member responsible to record their outages (especially vacation
time)
Consider using features in Outlook to help manage this for your team if
appropriate (e.g., shared calendars, outlook calendar permissions, etc.).
Change & Project Management Booklet.doc
Last saved 03/12/2009
Page 63 of 176
Revisit the calendar at least monthly during team meetings to remind people to
keep it updated.
Add more categories if you need. Or delete those you dont.
Dont try to get too granular.
Enter the first starting date as a Monday in the first cell and the rest of the of the
cells will calculate.
You can also mark dates which are critical to the project so that the team can see
when it will be difficult to be away.
Meeting Plans:
What its for:
Having one place to go to see the major meetings planned
Why you want it:
Lets people know (especially people who join the team later) what to expect for
meetings.
Tips:
Best used for recurring meetings such as weekly team meetings and steering
committee meetings.
Helps you think through what meetings you need to have
Consider using features in Outlook to help manage this for your team if
appropriate (e.g., shared calendars, outlook calendar permissions, etc.).
Revisit at least monthly during team meetings to keep it updated.
Add more categories if you need. Or delete those you dont.
Dont try to get too granular.
Issues Log:
What its for:
Managing your issues is one of the most important things you do in successfully
managing a project. This provides a place to log and track issues to resolution
Why you want it:
Having issues written down with owners and due dates is the best way to actually
stay on top of them and get them resolved in a timely manner.
Tips:
Go through your issue log at every meeting to get updates and track progress.
They should be updated at least weekly.
Escalate issues from the log that you need help resolving.
Add more categories or data fields if you need.
Use dd-mmm-yy format for dates (e.g., 10 July 09) to avoid confusion across
continents (7/10 vs 10/7 being July vs. October)
Keep one master version and guard it closely!
Remember to back this up regularly. Its volatile data that changes frequently but
is also vital to the projects success.
Often there will be a single log for Issues, Risks, and Action Items, as they tend
to track the same kind of information. (Remember issues are risks with a 100%
Page 64 of 176
Risk Log:
What its for:
Usually used in conjunction with a Risk Footprint, the risk log is a way to manage
the risks and mitigation plans.
Why you want it:
Having just identified a risk is not enough. You need to manage mitigations in the
same way you manage any issues.
Tips:
Go through your risk log at least monthly to update and track progress.
Escalate risks from the log, which need help mitigating.
Add more categories or data fields if you need.
Use dd-mmm-yy format for dates (e.g., 10 July 09) to avoid confusion across
continents (7/10 vs 10/7 being July vs. October)
Often there will be a single log for Issues, Risks, and Action Items, as they tend to
track the same kind of information. (Remember issues are risks with a 100%
likelihood of occurring.) Feel free to combine them as appropriate. (Simply add
another column to identify what the row is.)
See T19 Risk Management for more details and alternate ways to track risks.
Action Items:
What its for:
Beyond the project plan, there are often many tasks that need to be tracked.
Everything from set up a review session with Corporate Relations to Order
pizza for the team celebration. This tool helps you track those tasks so they
dont fall through the cracks.
Why you want it:
Therere often more things going on than you can remember. This helps drive
accountability to make sure things happens smoothly.
Tips:
Use this tool at weekly team meetings to record actions and track progress.
Add more categories or data fields if you need.
Use dd-mmm-yy format for dates (e.g., 10 July 09) to avoid confusion across
continents (7/10 vs 10/7 being July vs. October)
Often there will be a single log for Issues, Risks, and Action Items, as they tend to
track the same kind of information. (Remember issues are risks with a 100%
likelihood of occurring.) Feel free to combine them as appropriate. (Simply add
another column to identify what the row is.)
Page 65 of 176
Interdependencies
Take insights from:
Provide input:
Tips
The tools provided here are basic versions, most appropriate for small to medium
sized projects. Theyre a good place to start if you dont have anything else.
If you have a similar tool you or your group already uses and are comfortable with
it, do not feel compelled to use this tool.
Some teams work better using Excel (as is done here), others prefer Word or
even PowerPoint. Use the MS Office tool that best suits your needs. Often a
combination is used.
Typically large projects may use more sophisticated (or even automated)
versions of some of these tools.
You may also wish to add additional tabs of information such as milestone
schedules should that prove helpful.
Consider using this document (or sections of it) as a way to structure your weekly
team meetings.
Page 66 of 176
Rating
Blue Intermediate
Purpose
Risks are potential issues that, if they occur, would have a negative impact on
achieving the change objectives. The Risk Management Plan documents what these
threats to the project are, their potential impact, their likelihood of occurrence, and
steps being taken to monitor and/or mitigate them. It is used to:
Document the potential events that could disrupt the project
Agree to the likelihood of occurrence and impact
Agree an allocated owner to each risk from a management/ containment/
mitigation perspective
Establish and monitor a plan to address each risk
Track risks over time to the completion of the project or until the risks no longer
pose a threat
Outcome
Page 67 of 176
Structure
There are three distinct steps to risk management:
1. Identifying and mapping risks to a risk footprint
2. Developing plans to address, mitigate, and/or monitor risks
3. Monitoring and updating risks and risk plans over time
Calendar
Step
#
Other
process/procedure
Step/Trace
When significant
Risk is detected
Identify Risk
Depending on
Risk priority
Record Risk
Risk
Prioritized
Risk
Concern
immediately
resolved
Risk
dismissed
Determine resolution
Risk document
updated
Periodically and/or
as risk events
pass
Risk closed
Page 68 of 176
(D) medium
(G) high
(B) low
(E) medium
(A) low
(C) low
3)
Unworkable/
Failure to
deliver
I
M
P 2) Serious
fail
A delay/
to deliver
some
C components
T
1) Hit
target but
additional
work
For each risk scenario, the impact and likelihood are assessed and plotted. Risks
plotted in the red areas warrant the highest priority attention and the most detailed
mitigation plans.
Change & Project Management Booklet.doc
Last saved 03/12/2009
Page 69 of 176
1) Remote
(<10%)
2) Possi
(10-50%
LIKELIHO
Page 70 of 176
Tips
Risks that have a 100% chance of occurring are issues, and should be managed
via the projects issue management process.
Risks evolve over time: likelihood and/or impact changes. You should revisit
your risk management plan regularly (at least quarterly) to update it.
Spend your time & energy on risks that fall into the red and/or amber sections of
the grid.
Risk Plans are substantive documents. Generally each risk will need to have its
own plan that includes multiple options. (Think one page per risk.)
Set the impact scale to be appropriate for the project youre working on. May be
quantified in , time, and/or other metrics as appropriate. Try to make these
measurable, so that in the event of a risk becoming an actual issue the impact is
fully understood.
Test whether the risk creating exercise has been too optimistic or pessimistic with
informed individuals who were not participants. Feed this commentary back to a
review session.
Keep a baseline risk plan and the updated versions which reflect the project as of
today.
Interdependencies
Take insights from:
Consult with GAR (Global Audit & Risk) to help assess/facilitate risk sessions for
major initiatives or for coaching on risks.
Tools
The Risk Matrix and Mitigation Plan template are found in tools:
T12 Project Definition
T18 Project Administration
Page 71 of 176
Rating
Green - Easy
Purpose
The project dashboard is a way of communicating project status to a variety of
audiences, including the sponsor, steering committee, and project team members. It
provides a quick, concise one-page update on the projects progress.
It is used to communicate on:
The overall project status.
Status of progress against key milestone and project plan baseline.
Status of resource impacts.
Status of financial impacts.
Summary of key issues and risks.
Highlights & lowlights of the past period.
Plans for the next period.
The dashboard can be used as a means of:
Controlling the project.
Providing input into the project governance process.
Managing project risk.
Outcome
Page 72 of 176
Structure
Any agreed format can be used. It should include sections on overall project
health using RAG (Red-Amber-Green) statusing (see coding guidelines in the
Tips section), sections on milestones, resources, financials, accomplishments,
and future plans.
Dashboards should be completed on a regular basis, usually monthly but for
some efforts weekly.
The PowerPoint template may be used as a basis for the standard dashboard.
For individual status areas, the following RAG guidelines should be used:
Criteria
Green
Amber
Red
At least one of the
At least one of the following
All assessment criteria
assessment criteria
assessment criteria is red or
are green and no major below is amber or some
Overall
some major issue or risk will
issues exist that threaten major issue threatens the
Summary
likely prevent the successful
the success of the project successful completion of
completion of this project
according to plan
the project according to
according to plan
plan
Project is progressing and
Significant tasks behind The project is stopped or
expected to meet project
schedule, but
significant tasks are behind
milestones and end date.
adjustments are being
schedule, and adjustments
Schedule
Any slippage has not
made to deliver plan
cannot be made without
affected the critical path of
dates and hold to the
extending the project
any milestones or end
existing end dates
timeline
date
Planned resources
Resources are not in
Non-availability of resources
including contractors' and place to meet project
Resource
means major tasks are or
vendors' resources are in schedule but a plan
will be behind schedule
place
exists to rectify
Latest estimate at
Latest estimate at
Latest estimate at
completion is running
completion is running
completion is running over +
within 10% of the
over +10% of the
10% of the approved budget.
Budget
Change request is not yet
approved budget.
approved budget,
Change request is
being put forward to
being put forward to
secure funding
secure funding
Page 73 of 176
Amber
On target
Action
>
Red
Off target.
>
Issues present high impact
and/or no mitigation plan is >
in place
>
>
>
Interdependencies
Take insights from:
Tips
Use last periods template as the starting point for this periods template.
Establish how frequently you need this updated. Typically monthly is sufficient,
but for some projects weekly may be necessary.
Consider your audience when developing your dashboard.
Use the RAG guidance below when selecting Red-Amber-Green status.
Page 74 of 176
Rating
Blue Intermediate
Purpose
The purpose of this tool is to:
Make an assessment of the progress of the project, both within the current stage,
and, more formally, to move it to the next stage after sign off by the gatekeepers.
Assess whether the appropriate Project and Change Management tools have
been and will be used.
This tool can be used for all stages of the Change and Project Management
Framework.
Gate Governance ensures a project is progressing according to plan in respect of
time, budget, scope, and quality at the end of the major phases in its life cycle.
Outcome
Using a list of questions, the tool will identify:
A completed Sign-off Checklist against identified criteria.
A Go/No Go decision.
A common view and agreement to where we are and (if applicable) what needs
to be done to complete the relevant stage.
The answers to the questions will build up a list of issues and insights that can be
prioritised and should be addressed either before moving in to the next phase or at
the start of the next phase, as appropriate.
Page 75 of 176
Structure
It is strongly recommended that the sign-off checklist stage be completed in a
structured way:
Individuals consulted should be appropriate to the stage of the project but should
always include the Steering Committee and the relevant members of the Project
Team.
Stage checklist should be prepared by the Project Manager via consulting the
Steering Committee and Project Team members before the Steering Committee
meeting.
Check list review should be part of the last Steering Committee meeting of a
phase.
Within the structured discussion and decision-making process, the opportunity
should be taken to explore and provide input to key issues arising from the
discussion.
Meeting Principles
Open face-to-face discussions are ideal. WebEx can be a substitute.
All gatekeepers present (if members are not available, authority should be
delegated formally or sign off to be given before the meeting).
The Sponsor and Steering Committee make the Go/Stop/Recycle decision,
based on meeting outputs and discussions.
Preparation
Plan ahead - have meetings for discussions scheduled into the project plan.
Appropriate pre-read for the meeting should be circulated 2-5 days prior,
including key issues identified.
Attendees at the meeting should consider key issues and questions they wish to
raise in advance.
If a significant project, you may wish to involve a number of key stakeholders in
completing the sign off checklist.
The meeting should normally be part of the last Steering Committee meeting of
each phase.
The Meeting
Review the questions in the checklist:
Where the Committee do not give a positive answer to one or more of the
questions, a mitigation plan will need to be agreed with an owner and
completion date agreed.
Capture any comments on the specific areas that the attendees make.
Capture key learnings.
Discuss whether the project can move to the next phase.
The Sponsor and Steering Committee makes the overall decision to
Go/Stop/Recycle - based on the results of the meeting.
Post Meeting
Save all documents in the Project Folder as a record of decisions taken.
Ensure action plans to complete milestones are captured and the project team
are updated.
If the decision is to Recycle a decision will need to be made on whether a
further meeting required to review recycled elements (this decision to be based
on the situation).
Change & Project Management Booklet.doc
Last saved 03/12/2009
Page 76 of 176
Interdependencies:
Take insights from:
Tips
Preparation
Ensure that the pre read addresses all the criteria that are to be assessed the
Project Definition may be adequate, or may require expansion to explain
particular elements.
It may be necessary to provide a lot of detail to enable gatekeepers and the
steering committee to make a properly informed decision. Ensure that this does
not deflect from the core of the pre read by putting these elements in appendices.
Articulate the mandate that is being sought at the meeting i.e. dont request that
the project move to the next phase this may be the explicit identification of the
option to be chosen. It may also include agreement to publicise or communicate
the change.
If funding or resources are required in the next phase, they should be identified.
The Meeting
Consider if it is appropriate for members of the project team to be present, either
because it will help their understanding of the decision that has been made, or
because they will need to answer questions about a specific area.
If a decision maker cannot be at the meeting, look for pre-meeting input or
delegation of authority, ensure this includes decision rights as it can be very
frustrating to have unexpected recycling of a decision.
Have a facilitator run the meeting with a key role of getting a deep understanding
of why people are happy or unhappy on a particular criteria.
Ideally the Sponsor should summarise and close out the meeting by explicitly
stating what has been agreed.
Page 77 of 176
Questions
Gov/ Proj
Mngt/
People
Status
Gov
Gov
Gov
Gov
Gov
Gov
Gov
Gov
Gov
Gov
Gov
Gov
Gov
Gov
x
x
People
People
People
People
(x)
People
Page 78 of 176
Rating
Blue - Intermediate
Purpose
Changes are inevitable, yet once the project definition has been finalised,
changes can impact the ability of the project to deliver on its commitments.
Change control helps you maintain alignment in the face of changes. It ensures
that we understand and agree on whats changed, why, and the impact of the
changes on the project.
Outcome
Structure
The rules around when a change request is required should be set by the
steering committee when the project definition is signed off.
A change request is typically required in the following cases:
Schedule: Changes in the overall timeline which impact the project phasing
and/or go-live date.
Scope: Additions to and/or changes in functionality and design. This
includes reductions in scope.
Resources: The start and/or stop dates for project resources (internal and
external) have changed, or a resource is being added or removed.
Budget Overspend: Forecasted total project spend will over-spend or
under-spend the original approved budget by more than X%. Consult with
your local finance organisation for budget variance rules that apply to you.
CapEx or Revenue Switch: Forecasted CapEx or Revenue switch will
exceed the corresponding original budgeted amount by X%, even if the
overall budget is not impacted. (This is necessary since Internal Order
Numbers are opened for each of Revenue and CapEx and can only be
changed with proper approval.) Again, consult your local finance
organisation for rules that apply to you
Page 79 of 176
Interdependencies
Take insights from:
Tips
All change requests should be approved by the project sponsor and project
steering group or nominated authority as dictated by the projects governance
plan.
Consult with your local finance group for rules around financial documentation
and approvals for changes to budget.
The tool is structured to help you think through the factors that are important to a
successful project.
Consider using a Challenge & Build process to review and finalise this
document or sections of this document. Include the right players, issue a preread in advance, then engage in an active dialogue to confirm/refine the content
to reflect all needs.
In some cases, a section of the template may not apply. Simply state the
rationale why it doesnt apply & move on.
Page 80 of 176
Page 81 of 176
Business Unit
Sponsor
Type of Change Request (delete as
appropriate)
Name
Resource / Time / Scope or Design / Budget /
Benefits
Instructions:
Red text is Instructions and/or examples.
Please erase any red text before publishing; as this text is not intended to be part of
the permanent document.
Please do a Find and Replace of<,<Project Name Here>>
with the specific name of this Project eg Diageo Way of Selling.
Page 82 of 176
Approval Checklist
This section should be completed before the change request is appended to the
project definition and before work can commence on a change request. Evidence of
approval must be attached to the change request for CARM compliance and future
reference.
Approver
Sponsor
(ALL Change Requests)
Steering Group
(ALL Change Requests)
Financial Statement of
Authority
(For any Change Requests
with a Budget Overspend
and/or CapEx or Revenue
Overspend and/or change in
FY budget phasing and/or
significant reduction in
tangible financial benefits)
Other Control Authorities
e.g., Process changes,
Technical changes,
Infrastructure
Security impacts, etc.
Approval required
Y/N*
(If N provide
reason)
Y
Approval
provided
Y/N
Evidence of
Approval
(email
attached)
Page 83 of 176
Proposed Change
Describe the change required. Be explicit about what is driving the change request.
Answer here.
Benefits of Change
Detail the impact of the change on the business case. What was the original
business case? (You may insert information from the Project Definition here). List
quantitative and qualitative impacts.
Detail the benefits of the change distinguish new and old benefits as well as
changes to existing benefits. In particular please detail any original benefits which
might have been eroded as a result of the requested change.
IMPORTANT without this section completed your Change Request will not be
signed off.
Answer here.
Impact of Change
Identify impacted processes, projects, functions, regions, applications, dependencies
etc.
Answer in table below and add any additional information
Impact on other projects/dependencies
Is this change adding/mitigating any project risks? List details of the risks and add to the risk
register.
Page 84 of 176
For IS Projects
IS Application and Process related impacts
Affected
Processes
Impact
(H/M/L)
SAP - OTC
SAP - PTP
SAP - RTR
SAP - Mfg
SAP - BW
SAP Roles /
Profiles
Interfaces
Data
Business
Readiness
Infrastructure include details of decommissioning and DR impacts
Schedule
Delete this section if not applicable.
Ensure that any impacts to budget or resources resulting from changes to schedule
are included in the Budget and Resources sections of this document.
Approved Completion
New Completion Date
Impacted Milestones
Date
Define as appropriate.
dd Mmm, yyyy
dd Mmm, yyyy
dd Mmm, yyyy
dd Mmm, yyyy
dd Mmm, yyyy
dd Mmm, yyyy
Page 85 of 176
Resources
Delete this section if not applicable.
Ensure that any budget changes resulting from changes to resources (either from
addition / removal, date adjustments and/or rate changes) are included in the Budget
portion of this request.
Use Remove if the resource has not yet started on the project; or specify the
appropriate end date. A Start Date is not required to modify End Dates for resources
that are already being billed to the project.
New / Remove
Start Date
End Date
Resource
/ Modify
dd Mmm, yyyy
dd Mmm, yyyy
dd Mmm, yyyy
dd Mmm, yyyy
dd Mmm, yyyy
dd Mmm, yyyy
Total Change
Cost
Expenses
Payment Schedule
Percentage
Percentage
Date
Date
Amount
Amount
Page 86 of 176
Budget
Follow guidance provided by your local finance organisation for documenting this
information. In the absence of other guidance.
If there is no budget impact due to this change request, indicate why this is the case
and do not include the tables below.
Revenue
Capex
Revenue
Impacted IO Numbers
Spend Summary
Original approved funding
Total
FY01
FY02
FY03
FY04
FY05
Total
Approved
Change
Amended Request
Capex Revenue Total Capex Revenue Total Capex Revenue Total
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Funding variance
Amended Total Project Cost
0
0
0
0
0
0
0
0
Page 87 of 176
Page 88 of 176
T16
T23
T24
Tool Overview
Leadership Assessment
Understanding how leaders are performing on the project and providing a
framework for individual or group review
OR
Insight into how we are doing
Change Resistance
Understanding where resistance comes from and how well the change has been
understood. Identifying and improving peoples commitment to change.
Culture Assessment
If we are not conscious of the underlying cultures in which our projects are
operating, those cultures will manage the outputs. Edgar Schein
OR
the culture can make or break your project
T25
Communication Planning
T27
Stakeholder Management
T28
T29
Phases
Understanding your Stakeholders, gain greater insight into the issues and vision
associated with your change, and investigate the position of key people and the
barriers / enablers to making your change happen.
Role Mapping
Understanding the people connected to the change, to aid in the building of the
right project structures, governance, communications and engagement plans
OR
This is where everyone fits into the jigsaw
Page 89 of 176
T31
Page 90 of 176
Rating
Green - Easy
Purpose
Outcome
Structure
The leaders can be any individual who is deeply involved in the change e.g.
Steering Committee member
Can be used for self-assessment, or contracting between key people (e.g.
Change Agent and Sponsor) or for team feedback.
Individual(s) can complete the assessment for those being assessed.
If two or more individuals are giving each other feedback - ensure everyone
involved has also completed the form for themselves.
Agree the feedback approach and structure, and ensure participation from all.
Ensure all feedback is specific and relates only to performance in leading the
change.
As a result of the process, individuals should look for connections between their
own observations, the feedback and their development plan, and create an
appropriate action plan.
The outcomes of this process could form part of the next P4G discussion with the
individuals line manager.
Page 91 of 176
Interdependencies
Take insights from:
Tips
Can be used at any time from the Initiate/Analyse stage. Early on it will help set
expectations. Later it will focus more on reviewing performance.
This can be done purely at an individual level for self-assessment, or a team may
agree at the start of a project that periodically (e.g. every 3 months) the
assessment process will be undertaken. Doing this can help overcome the
tendency to do this either only in good times or only in bad!
This is best reviewed in a face to face conversation in a coaching environment.
The assessor should pick the 5 to 7 key things that the individual being assessed
will need to focus on in order to lead the change successfully. This should
include at least 2 key strengths to leverage.
For these areas as a minimum, the evaluation score should be backed up by
explanation and examples of the desired behaviours or results an x in a box is
little help in understanding what lies behind performance and what should be
done to improve it.
As with all coaching tools, this should be used with responsibility and integrity. It
is there to help the individual understand and improve performance, so always
focus on how the feedback can be received in a positive way.
Use Coaching models and behaviours.
Estimated Timing: this takes 20 minutes when done as an individual. 1:1
feedback sessions - 1 hour.
Page 92 of 176
Assessment
Rarely
Sometimes
Often
Page 93 of 176
Always
Rating
Green - Easy
Purpose
Throughout any change program there will be a need to talk to people, either about
the whole change or a specific element of the change. The one-minute
communication is a template that helps to build a communication that can be easily
memorised and used in any circumstances. It will:
Build a common understanding on a topic by developing simple answers to
simple questions
Align the Steering Committee and/or Project team around the core messages on
a topic
The questions are designed with consideration for the different communication styles
of any potential audience. The aim is that any individual will connect strongly with a
part of the communication, and through this understand and engage with the
message.
Outcome
Structure
Page 94 of 176
Focus on the needs and issues of your audience. Start from the position of the
people that you are conveying the message to (not from where you are), leading
with their need.
Be aware of the natural tendency to write a communication that appeals only to
your communication style (the section you find easiest and most interesting to
write will usually be in your dominant style)
It is OK not to use a section, but be sure that this is because there is
nothing to say and not because you are uncertain how to say it.
Testing the communication on different people will help to understand how it may
be heard differently and the different reactions it may provoke
Interdependencies
Take insights from:
Tips:
Effective communication begins with believing what you are communicating; and
conveying belief; it needs to be authentic, and to come from inner conviction; its
about conveying your message with context and feeling if it doesnt have
meaning for you, it wont come across with meaning to your audience.
Understanding the audiences perspective is key; putting yourself in the
audiences shoes.
Communication can be proactive and reactive; if proactive, then plan how, who,
when communication will be delivered within the Communication Plan
A one minute communication can be created at any time in the project e.g. it
can be used at an early stage when the project team is forming to explain the
project objectives
Whilst it is ok to deliver this with a script, always try to get the communication
simple enough that it can be delivered from memory, especially if it is for reactive
use
The one minute communication is often called the Elevator Speech you
enter an elevator on the ground floor and find you are in the company of an
Page 95 of 176
important stakeholder, by the time your journey ends, you have delivered
the message and your stakeholder has heard it, understood it and engaged
with it!
Storytelling can be effective too, it is a great way of winning over hearts as well
as minds.
Page 96 of 176
Direct
Tells
Spirited
Controls Emotion
Displays Emotion
High
expressiveness
Asks
Low
expressiveness
Systematic
Considerate
Low
assertiveness
Direct
Primary focus is on action; what is going to happen and when
Decisive
Communicates actions, plans and deliverables
Spirited
Primary focus is on the big picture ideas, vision
Persuasive
Connects things to form the story
Considerate
Primary focus is on people interactions relationships
Supportive, builds trust
Has good understanding of others needs/concerns
Systematic
Primary focus is on logic, facts
Precise, accurate
Communicates clear statements/formulae or facts
Page 97 of 176
Page 98 of 176
Rating
Blue Intermediate
Purpose
Identify where the resistance areas are within your change project from the
perspective of your stakeholders and individuals who are impacted
To increase alignment to the change rational and implications, increasing
engagement to the sustainable outcome
To recognize the personal impact which change has upon the people impacted
and support them through the journey to commitment
Outcome
Structure
This tool is used most effectively with people who understand the change; it
therefore needs to be completed after the initial communications briefing.
Split into groups of 3-5, ensuring the group selected has a representative view of
the different areas impacted, whilst also considering the dynamics and mix of the
group.
Select the appropriate exercise
Change Resistance Scale (Tool I)
Change Curve (Tool II)
Understanding Commitment (Tool III)
Agree the next steps with the group, and ensure the learning are built into your
communication and implementation planning.
Page 99 of 176
Interdependencies
Take insights from:
Tips
Rating
Green Easy
Purpose
Outcome
An insight into the behavioral and transactional reasons for resistance and
acceptance.
An action plan to address the areas of concern and leverage areas of agreement
to build alignment.
Identify gaps in the communication process.
Structure
Step 1 individually answer the change resistance scale questions
Individuals should complete the form without conferring (either in advance or in
the session).
Ensure individuals are briefed to complete the form for the specific phase of the
change you are examining.
Step 2 - As a group, identify the themes of disagreement and agreement
Facilitators may wish to draw up the scale on a flipchart and have individuals plot
their answers, to visually represent the spread of responses.
Discuss what lies behind the disagreement and what has enabled agreement.
Step 3 Split into smaller groups and identify key actions which will overcome
barriers, or strengthen the areas of agreement.
Identify key actions from the above discussions and ensure that actions have
identified owners.
The responses to the questions should be combined, summarised and an action
plan developed to address areas of concern.
Ensure outputs from this session inform the project risk and issues log, as well as
provide input to the Communications Plan.
Tips
It is best used with one stakeholder / impacted group at a time so that the
reasons for resistance do not get confused, or participants feel pressured to
simply go along with the general agreement of the group.
When the participant groups are big, the questionnaire can be sent out in
advance to be filled in and returned in advance. A summary of the results should
then be shared with the group, and start the process from step 2.
The tool can be used as an ongoing monitoring tool as peoples resistance
changes as the change progresses, throughout the project life cycle.
The responses gathered may also be a reflection of other changes/activities
underway in the organisation not directly related to your change, which may make
it difficult to separate out. When the questionnaire is briefed, ensure individuals
are answering the questionnaire in the context of this specific change and not
generalising previous changes experiences.
Pay particular attention to the responses to questions 10, 14, 15, 19, 20 and 23.
The purpose of the session is not necessarily to gain alignment on viewpoints but
rather highlight areas where more engagement or communication is required.
Agree
1
Disagree
3
Rating:
Black Diamond seek assistance
Purpose
To build understanding of
individual and group response to
change and specifically to
manage positive and negative
responses.
Assist participants to identify
their change journey, and
provide them with strategies and actions to deal with the change.
Outcomes
Recognition that people are all feeling different and this is both normal and ok.
Understanding why people are feeling a certain way, and appreciating that their
peers / teams are likely to be feeling a similar way.
Participants have a clear understanding of the Change Curve and their place
upon it, and strategies for dealing with each stage.
Structure
This exercise is available as a win zip file with slides and handouts (in both a face to
face and a virtual meeting session)
Step 1 the context for change
Provide the context for the change specific to the participants and their business
area.
Explain that you are now going to move into a session on how people experience
change using the Change Curve tool.
Remind everyone that change is a very personal thing it is experienced in
different ways by different people.
Ask individuals to think about how they and other people are feeling about the
proposed change.
Step 2 - Emotion Cards how you are feeling about the change
Spread Q-cards onto the tables. Ask delegates to chose the cards that they feel
reflect how they themselves are feeling about the change.
Ask them to be as honest as possible, as this is important in terms of how they
move the situation on.
Once Q-cards have been chosen, ask the individuals to stick them onto a
flipchart with blue-tac. The group should gather round the flipchart and view the
different pictures that have been chosen.
Encourage discussion highlighting the different choices people have made.
Ask groups to report back one piece of learning they have from the discussion.
They do not need to feedback actual scenarios.
Facilitator to highlight that we all manage and cope with change on an ongoing
basis outside work. Highlight that we should be able to use different experiences
outside of work to help us cope with difficulties and change inside work.
Gather individuals round the table change curve handout and ask them to place
the Q-cards they chose previously onto the quadrant that best represents how
they they may use more than one quadrant)
1. Generate a discussion to ascertain whether or not how people feel is normal.
Encourage individuals to share how people have felt during change in the
past. Ask them to reflect on their previous discussion of own personal
experiences and what they have noticed of others too.
2. Refer to strategies to deal with the change and communication priorities
which discuss what people might hear at each stage of the curve. (found on
change descriptor handout)
Step 5 - Consider where you are personally at and your own reflections on the
change
What steps are you going to take to ensure you fully understand and align behind
the change?
Who will you speak to what additional support do you need?
Tips
It is very easy for people to think about others however we want them to be
open about their own emotions first BEFORE appreciating others.
Encouraging every individual to explain their perspective will give a much richer
understanding across the group do not just rely on those who are more willing
to contribute.
Some people may be further along the change curve than others. Encourage
them to remember how they felt when first informed of the change, and ask them
to share with others how they have moved towards acceptance.
Rating
Blue - Intermediate
Purpose
Outcomes
Advanced identification of the specific issues that groups or individuals will face.
Action plan to address and move the commitment of individuals as a core input to
the communication plan.
Structure
Step 2 - Develop an action plan for these specific audiences considering how
to move them along the commitment curve
What intervention would help build their commitment to change?
What is the most appropriate method of delivery to maximise their engagement
i.e. does it need to be face to face; intervention from the sponsor etc.
Tips
There are three phases and six steps in building positive commitment to the project
and associated changes.
Preparation Phase:
Contact - Have people affected by the change been informed even in the most
general sense? This should certainly include all stakeholders and people impacted
by the change.
Awareness - Has the change description and communication process reached all
stakeholders and those involved/impacted by the change?
Acceptance Phase:
Understanding - Has time been spent - one-to-one - helping those impacted
understand the business case for change and testing the relevance/implications for
themselves?
Adoption - Have people begun to assimilate new ways of working? Are they
transferring their knowledge and understanding to others as good practice?
Commitment Phase:
Use - Beyond trial and experimentation, are individuals taking the changes forward
on the basis of personal experience and personal preference, actively searching and
spinning?
Embed - The changes are now recognised as our new ways of working and best
practice.
The Project Manager has to effectively lead, engage and manage the project through
these phases and be sensitive not just to the information that people have about
change, but also to their feelings about the projects.
At any stage people in the impacted group may experience negative feelings to the
changes.
This will happen during the acceptance phase. It is critical that the Project Manager:
Does not assume that there always is a positive response to the change.
Is alert to the signs of individuals and groups moving through the Change Curve.
Actively explores the negative response in order to build deeper commitment.
Rating
Blue Intermediate
Purpose
Outcome
An appreciation of the existing organisation / team culture and the necessary culture for
change outcomes to be sustainable.
List of high priority risk areas to mitigate and opportunities to build upon to inform the
appropriate way forward for the project.
Easier implementation and sustainability of the intended outcomes of the project.
Structure
Rating
Green - Easy
Purpose
To determine how our organisational / team priorities are driving our culture
An appreciation of the existing organisation / team culture and the necessary
culture for organisational priorities to be achieved
Understanding the implications for desired culture and clarity about the changes
needed
Outcomes
Structure
Step 1 Working in appropriately sized groups, brainstorm all the behaviours
that are seen as typical in the part of the organisation where the change is to
be implemented.
Brainstorming should be done individually, by writing each idea on a separate
post-it note. Use a selection of the following questions to prompt thought
What is important to leaders? How do people know this?
How do leaders communicate their vision? How well do people understand
this vision?
What do visitors remark about when visiting the location?
What do you like most about working here?
What frustrates people most?
What behaviours are encouraged with the new ways of working?
What behaviours are discouraged with the new ways of working?
How do things get done / get started?
How clear is authority / accountability?
How does the decision-making process work?
Whats the balance between team and individual focus?
How is knowledge / information shared?
What do our written communications say about us?
How are meetings conducted / managed?
How easy is it to get time with senior people?
How is performance managed?
What are the levels of trust?
How do people get developed / get appointed?
How diverse is your part of the organisation?
How well does the organisation manage change?
Change & Project Management Booklet.doc
Last saved 03/12/2009
Post-its
Post-its
Post-its
Positives
Diageo
Values
Be The
Best
Freedom to
succeed
Passionate
about
consumers
Proud of what
we do
Valuing each
other
Negatives
Post-its
Post-its
Post-its
Tips
You could replace Diageo Values in step 3 with any of your functional strategic
priorities.
Make sure everyone is involved and can hear what is being said.
Keep the session upbeat and future focussed.
Interdependencies:
Take insights from:
http://www.geert-hofstede.com
http://www.cyborlink.com/besite/
Purpose
Outcomes
Structure
The Cultural Web identifies six interrelated elements that help to make up the
paradigm the pattern or model of the work environment. By analyzing the
factors in each, you can begin to see the bigger picture of your culture: what is
working, what isnt working, and what needs to be changed. (see notes on next page
for a look at the 6 elements)
Step 1. - Deliver a brief overview of the 6 elements of the cultural web
Step 2. - In small groups analyse the culture as it is now
Assign each group a different element of the cultural web to work on
Each group should think about actual Diageo examples (postive or negative)
Share this back with the group
Look at the web as a whole and make some generalized statements regarding
the overall culture. (how would you describe the culture and the themes prevalent
throughout the web)
Stories
Work culture
Promotions
Social Gossip
Rivalries (inter
company and
customers)
lone rangers
Symbols
Type of office
Laptops, Blackberry
etc
Conferences
Terminology
Policies
Job titles
Types of travel
Culture
Control Systems
Financials
Measurements
Reward systems
Key Performance
Indicators
Policies
Power Structures
Formal & Informal
Length of service
who you know
Level
Knowledge
Networks
Organisation Structure
Hierarchy
Grading Structures
Roles &
Responsibilities
Spans of control
Joe Bloggs single handedly turned around this department on $1,000 budget
youll never get a good deal with such and such customer
only people with such and such background are good at that job
You wont get told off for following the process even if the outcome isnt
delivered, but you will get told off for not following the process.
Useful questions
What stories do people currently tell about Diageo?
What reputation is communicated amongst your customers and other
stakeholders?
What do these stories say about Diageo believes in?
What do employees talk about when they think of the history of Diageo?
What stories do they tell new people who join Diageo?
What heroes, villains and mavericks appear in these stories?
What stories exist about other projects?
How have people developed or been promoted?
What style of thinking / communication most valued?
Rituals and Routines
The rituals of organisational life are the special events through which the organisation
emphasises what is particularly important and reinforces the way we do things
around here'. These rituals can be enablers or barriers to an effective organisation
and will have an impact on the sustainability of your project. For example;
Taking a department out for drinks and a meal whenever there has been a
particularly busy period at work. This signals that effort is appreciated and that
work is rewarded with some play time.
Holding weekly team meetings that always last an hour regardless of the agenda
may reflect that prioritising our time is not important. Similarly it may ensure that
we always reserve enough time for simply connecting and dont only focus on
tasks (depending on your perspective)
Holding P4Gs at least twice a year ensures that we focus on our development
and dont leave it to chance
Having one busy period after another becomes a habit and often doesnt leave
much time for reflection or re-energising
All of these mechanisms communicate and reinforce the values and beliefs of the
organisation.
|Useful questions
What do customers expect when they have an interaction with Diageo?
What do employees expect ?
What would be immediately obvious if changed and which one would you
want to keep?
What behaviours do these routines encourage and what core beliefs do
these rituals reflect?
When a new problem is encountered, what rules do people apply when
they solve it?
What routines do you not understand the reason for?
How is coaching used and who do we apply it to?
Symbols
Symbols such as brands, office facilities, cars, dress code and titles, or the type of
language and terminology commonly used become a short-hand representation of
the nature of the organisation or department.
This includes all of the visible features that people who come in contact with the
organisation would see and can be created to directly reflect the values. For
example;
People often feel more connected to a workplace if they have a permanent desk,
instead of a hot desk which they cannot personalise
Useful questions
Is company-specific jargon or language used? How well known and usable by
all is this?
Are there any percieved status symbols used?
What image is associated with your organisation, looking at this from the
separate viewpoints of customers, suppliers and employees?
Are there differences in how policies are applied to different people?
Organisational Design and Structure
This includes both the structure defined by the organisation chart, the roles and
responsibilities of those people within the structure, and spans of control. They often
delineate important relationships and emphasise what is important in the
organisation. For example;
If clear design principles are not in place, the structure will often have more to do
with the leaders beliefs, philosophies and personal ties to existing organisational
members than pure logic about how to get the organisation to work the most
effectively.
Useful questions
Is the structure flat or hierarchical? Formal or informal? Organic or
mechanistic?
Where are the formal lines of authority and where are the informal lines
what should be encouraged / discouraged?
Are roles and responsibilities clearly defined?
What spans of control exist and are these enablers or barriers to efficient
ways of working?
How easy is decision making or issue resolution?
The way that budgets are allocated also underpins assumptions and beliefs as to
the priority placed upon a function / goal
The way of accomplishing goals and the management processes used are
indicators of what is important
Useful questions
What process or procedure has the strongest controls? Weakest controls?
Does every member of the team know their individual contributions?
Reporting up the organisation can be complex and demanding and is often
about explaining why things arent right.
How is CARM percieved and how simple is it to exectute?
What incentive plans exist and what behaviours do they encourage?
Do employees get rewarded for good work or penalised for poor work?
Do we reward the How of performance as well as the What?
What reports are issued to keep control of operations, finance, performance
etc... ?
What KPIs exist within your area?
In busy times, what are the first deliverables to be deprioirtised?
Power structures
These are the people that have the greatest amount of influence on decisions,
operations, strategic direction, and actual execution. The most powerful groupings
within the organisation are likely to be closely associated with this set of core
assumptions and beliefs. For example;
Power through personality (a junior person who can rally the troups behind an
idea)
Useful questions
Who has the real power in the organisation?
On what basis do people assume power in your team/ organistaion?
What do these people believe and champion within the organisation?
Who makes or influences decisions?
How is this power used or abused?
Tips
The Stories, Rituals & Routines, Symbols can be used to add high energy to a
session, watch out however as your time can run away here
Maintain a balance of positive elements of the culture, and avoid the session
simply becoming a moaning session
Ensure that you probe for specifics in all elements of the web so that you avoid
having a generic list as outcomes
For all its elusiveness, corporate culture can have a huge impact on an
organisations work environment and output. This is why so much research has
been done to pinpoint exactly what makes an effective corporate culture, and how
to go about changing a culture that isnt working.
Interdependencies
Take insights from:
Purpose
Outcomes
Structure
Step 1
Brief the questionnaire instructions
Complete the questionnaire individually
Transfer scores onto the scores sheet adding up totals.
Plot results to create two graphs using 2 different colours for now and
preferred
Step 2
Explain the model
Individuals might want to start to discuss which represents the current culture, but
try to keep this to a minimum until after they have completed the questionnaire.
Step 3
Compare results within the team, looking for consistencies and inconsistencies
and exploring what lies behind any similarities and differences
Consider outcomes in relation to FromTo outcomes, identifying key issues
what would you need to do more or less of in the preferred culture?
Step 4
Consider the potential actions that would be necessary to bring about the
required change in behaviour, to support the change
Change & Project Management Booklet.doc
Last saved 03/12/2009
Low
Control
The Create Culture
Inward
Looking
The Control Culture
High
Control
Tips
Interdependencies:
Take insights from :
Provide input to :
Dominant Characteristics
Now
Preferred
0
60
10
10
30
20
60
10
When all the questions have been answered, transfer scores to the summary sheet
(p 32). You then map these scores to the graph (p 33) using 2 different colours to
represent the Now and Preferred state.
1.
DOMINANT CHARACTERISTICS
NOW
PREFERRED
A.
A. _____
A. _____
B.
B. _____
B. _____
C.
C. _____
C. _____
D.
D. ______
D. ______
Total 100
Total 100
2.
ORGANISATIONAL LEADER
NOW
PREFERRED
A.
A. _____
A. _____
B.
B. _____
B. _____
C.
C. _____
C. _____
D.
D. _____
D. _____
Total 100
Total 100
MANAGEMENT OF EMPLOYEES
NOW
PREFERRED
A.
A. _____
A. _____
B.
B. _____
B. _____
C.
C. _____
C. _____
D.
D. _____
D. _____
Total 100
Total 100
4.
ORGANISATIONAL GLUE
NOW
PREFERRED
A.
A. _____
A. _____
B.
B. _____
B. _____
C.
C. _____
C. _____
D.
D. _____
D. _____
Total 100
Total 100
5.
STRATEGIC EMPHASIS
NOW
PREFERRED
A.
A. _____
A. _____
B.
B. _____
B. _____
C.
C. _____
C. _____
D.
D. _____
D. ____
Total 100
Total 100
6.
NOW
PREFERRED
A.
A. _____
A. _____
B.
B. _____
B. _____
C.
C. _____
C. _____
D.
D. _____
D. ____
Total 100
Total 100
Create
Compete
Control
Create
Compete
Control
1. Dominant Characteristics
2. Organisational Leader
3. Management of Employee
4. Organisational Glue
5. Strategic Emphasis
6. Criteria for Success
TOTAL:
Divide by 6:
Collaborate
PREFERRED SCORES
A
1. Dominant Characteristics
2. Organisational Leader
3. Management of Employee
4. Organisational Glue
5. Strategic Emphasis
6. Criteria for Success
TOTAL:
Divide by 6:
Collaborate
50
50
Create
Collaborate
40
40
30
30
20
20
10
10
10
20
30
40
50
Control
10
20
30
40
Compete
50
Rating
Blue Intermediate
Purpose
Outcomes
Clear understanding of:
What you intend your audience to hear and do as a result of each communication
your communication objectives.
Who you need to communicate with.
Your main messages.
The methods/ channels youll use and when.
The measure of success.
How and when you will build up each of your communication events.
Resources and budget that are needed.
Structure
The communication plan is created and updated on a regular basis by a member or
sub group from the project team. It should be reviewed and approved by the steering
group.
There are three key steps in building up the plan
Step 1 - Plan the Methods and outcomes
Use the tool below to plan the method and outcomes. Each engagement event
should be on a separate line; there may be a number of events over time for each
audience.
Audience
From
To
Key Messages
Communication
activity
The unique
ref no for
this comms
event
Who is the
audience?
Measurement
Responsibility
Interdependencies
Take insights from:
Project budget
T16 One Minute Communication
Tips
Audience identification and outcome planning:
Use role mapping (T28) to identify everyone that needs to be engaged, and how
these individuals can be grouped into audiences for specific communication
events.
Throughout your planning, focus on the standpoint of the audience, rather than
the standpoint of the project team or communications team. For example, the
project team may want to explain the difficult journey to get to a proposal, the
audience may only want to hear what the proposal is.
Building the communication
Have a small group of people (ideally two or three) build the communication. One
person working alone can become focused on a particular element to the
exclusion of others or get stuck on finding a way to articulate a message well.
More than three people becomes unwieldy
If possible, test the communication with people who have a similar knowledge of
your change to the target audience they can filter out assumptions and jargon
Use communication experts within the business
The best communications are the simplest. Remove as many jargon and
buzzwords as you can; take out complex business language.
Try to take time out as you build the communication. If possible, build it over two
days, so you come back to it after a number of hours away a fresh mind will
see new opportunities and issues to make it better
Who should deliver the communication
A person who has a significant role in the Change project and can communicate
on it authentically e.g. Steering group member or one of stakeholders who are
going through the change.
Knowledge of the communication content is key.
Credibility with the audience and power to motivate will bring real listening.
Communication Method
A guide to communication methods is provided below.
Put yourself in the audiences position, and think about how you would like to be
communicated with
Often there is a necessary element of compromise e.g. you would like to talk
individually with people, but you need to get a message out at a point in time.
Look for ways round the problem, and ensure you acknowledge the compromise
Remember - Storytelling, as one communication tool, is a great way of winning
over hearts as well as minds.
Rating
Green- easy
Purpose
Achieve greater clarity of the end state and purpose of the Change Project.
Gain further insight into the issue and understand Stakeholders previous
experiences of projects and change.
Identify the motivation of key stakeholders on a scale of Oppose to Make it
Happen and detail, the risks, issues and opportunities associated with these.
Outcome
Structure
Using the role map, identify which stakeholders to talk to in a formal engagement
session.
Engage key Stakeholders around the project.
Map Motivation, Impact, and Influence of key Stakeholders/ groups.
Decide on actions required to manage your stakeholders and include within the
communication plan.
Core Tools
Purpose
For Sponsor and Change Agent to achieve greater clarity of the end state and
purpose.
To identify key Stakeholders views of the change.
Gain further insight into the issue and understand Stakeholders experience of
similar situations.
Outcome
Structure
Tools primarily used early in the project in Analyse phase, although can be used to
engage with Stakeholders into Design 1. Sponsor Meeting.
2. Key Stakeholder Meetings.
3. Consolidate Information into Response Summary & Feedback to Sponsor.
Step 1 Sponsor & Project Manager Meeting
Complete the Stakeholder Engagement template with the Sponsor
Forward a completed copy to the Sponsor as a record of what was agreed.
Step 2 1:1 meeting between the Project Manager & Key Stakeholders
Discuss the defined project end state and purpose as understood by the Sponsor
and Project Manager so far, using questions from the T11 Possibility - Issue
Identification tool as appropriate.
Ensure all possible options are explored and pros and cons captured.
Ensure you have enough information to judge level of Stakeholder commitment.
Complete a Stakeholder Response summary for each Stakeholder / group.
Step 3 Consolidate Information into Response Summary & Feedback to
Sponsor
Summarise responses identifying the current situation, end state, purpose of
change, high level options and giving your recommendation.
Share and discuss the feedback.
Decide if
Further research is required, particularly in relation to costs, timelines and
resources.
Benchmarking is required / what the external radar is telling you.
No further work is required if the issue is not being taken forward.
Change & Project Management Booklet.doc
Last saved 03/12/2009
Tips
This session can either be incorporated into a wider meeting agenda, or may be
scheduled specifically for this activity
If the change will not come as a shock for the Stakeholder, then a pre-read will
allow you to spend more time engaging around thoughts, feelings and questions
in relation to the change instead of spending most time on briefing and not
concluding on the so what.
Ask open, probing questions which reflect good coaching behaviours as in
Breakthrough Performance Coaching.
Present exact Stakeholder feedback use their words.
Do not dress up difficulties or lack of agreement to your project, this data is an
early indicator of challenges you will face in the Implement and Sustain phases.
Build knowledge of the issue from advocates of the change in preparation for
meetings with likely resistors
Interdependencies
Take insights from:
Purpose:
(Why are you trying to do it and what are the business benefits?)
Due Date:
End State:
(List all the viewpoints about potential end state)
Purpose:
(List all the reasons for change and potential benefits)
Stakeholder Reaction
(summarise the early insights you have into the Stakeholder - their motivation or influence on
the project)
Recommendation to Sponsor:
(Should the work proceed or not)
Purpose
Outcome
Structure
Tools primarily used early in the project in Analyse and Design phase:
1. Identify motivation towards the change.
2. Identify the amount of impact this change will have upon this Stakeholder
group.
3. Identify the amount of influence (power) this Stakeholder has upon the
change or other individuals.
Option 1 Sponsor & Project Manager discussion
1. List all of the Stakeholders by name or group down the left hand side, and the
amount to which this change will impact them / their teams.
2. Next mark with a X where you assess the persons commitment to be at present
on a scale of Oppose to Make it Happen.
3. Mark with an O where you assess their commitment needs to be to ensure the
change is successful.
4. Mark an arrow between the X and the O to indicate the shift required in an
individuals attitudes.
5. Now consider the amount of influence that this person has upon the change itself,
or other people within the change.
6. Consider the implications of your findings.
7. Test the assumptions that you are making.
8. Create an action plan and agree how you will approach this.
Option 2 Discussion with an individual Stakeholder or as a group
Introduce the concept of Stakeholder analysis, and invite the Stakeholders to tell
you where they are in terms of Impact, Motivation and Influence in relation to the
project
OR
As a group - Write the names down of all key Stakeholders on post-it notes and
stick them onto a poster of the graph on the wall according to motivation, impact
and influence.
Probe to understand why this is and try to establish what it would take to move
them to where you feel you need them to be for the change to succeed.
Change & Project Management Booklet.doc
Last saved 03/12/2009
Create an action plan and agree how you will approach it and make this a specific
element of your communications plan.
Group /
Individual
Person A
Role(s) in
the change
Sponsor
Change
Impact
(H, M, L)
Influence
(H, M, L)
Oppose
Neutral
Let It
Happen
Help it
Happen
Person B
Advocate
Person C
Stakeholder
Group A
Targets
XO
Make it
Happen
Notes
Tips
Ensure that you allow enough time for the discussion, this is where the most
value comes from.
You may set up a meeting specifically to conduct this exercise or you may do as
part of other discussions.
Identify the key Stakeholder groups early and map their position at the outset.
Revisit in later stages as you evaluate efforts to improve positive attitudes and
engage Stakeholders.
Stakeholders all have influence, whether it is formal power invested in a position
of authority or it is social power of being able to persuade others to support or
oppose change.
Those with higher influence are likely to be your most useful supporters or most
dangerous opponents, thus influence analysis helps you to prioritise your focus
on Stakeholders (and risks and issues)
Some Stakeholders will actively support the change, putting their necks on the
line and working hard to help it succeed. Others will work the other way,
vociferously seeking to scupper your efforts.
Help it Happen and Make it happen are where much focus often happens.
However there is often a silent majority in Let it happen or Neutral where
rather than taking positive action can subtly support or oppose the change by
allowing things to happen or quietly blocking and hindering progress.
Neutral are often playing a waiting game, looking for who is going to win.
Once they have made their decision they will move quickly to Oppose or Help It
Happen. Work hard to convert them and you may well win the game.
Be aware that the data in your Stakeholder map represents your perceptions
about other people and they may not necessarily agree with you! So it is wise
to keep this sensitive information very confidential - never print or leave your map
lying about
Ask the questionwhat would it take to get you to a win win position on this?
Stakeholder analysis, could be an important element in deciding your preferred
options, and could be used to evaluate several options at the same time.
Need to ensure that Stakeholders are clear on the end state, dont undersell the
end vision just to gain agreement.
Change Champion:
takes personal
responsibility for
ensuring success
Influence (Power)
Low
Oppose
Neutral
Let It Happen
Help it Happen
Make it Happen
Interdependencies
Take insights from:
High
BEN
PAUL
JOHNs
TEAM
ADAM
AMY
LAURA
Influence (Power)
LISA
MATT
Oppose
Low
Neutral
Let It Happen
Help it Happen
Make it Happen
Rating:
Blue - Intermediate
Purpose
Outcome
This role map can then be used as a reference in many of the key pieces of work that
will be completed in relation to the change for example creating or refining the
governance structure; understanding the cultural impact of the change; creating or
refining the communication and engagement plan; understanding the best solution
through comparing different role maps.
Structure
Identify the individuals who are the control authorities responsible for these areas
and map these onto your role map.
The output will look like a complex organisation structure chart this is a simple
example!
Example - implementation of new production measure
Operations Director
G
Finance Director
CA Carm; financial practices
Operations Manager
S
Team Leader
T
Operators
T
Procurement Director
A
Technical Manager
CS
Craft
T
Key
G
CS
S
CA
PM
T
PTM
Gatekeeper
Cascading Sponsor
Sponsor
Control Authority
Project Manager
Individuals Impacted
Team Member
Advocate
Reporting lines
Authority Influence
Agent Accountability
NB:
People can play more than one
role in a change
Final role maps should include
names
Interdependencies
Take insights from :
Provide input to :
T13 - From-To
T12 - Project Definition
T22 - Workflows & Swimlanes
Commitment model
Tips
General tips
Generally drawn as they are now - major projects may also benefit from creating
an end state map that reflects how the structure will look on completion of the
change but remember that one map can only be for a single point in time.
Change & Project Management Booklet.doc
Last saved 03/12/2009
There may be a temptation to reduce the size of the map by only looking at
individuals who are significantly impacted resist this temptation you may
ignore the people who hold the keys to success.
The mapping of all the impacted individuals and their reporting lines may show
that they are only linked at a very senior level in the organisation (e.g. MD Diageo
PLC). This is when you look to identify Cascading sponsors who can make the
change happen in a part of the organisation, and bring them together in the
Governance structure.
Once you have mapped all the roles and control authorities, you may find people
who are very vocal on the change are not there these are the Advocates.
The map can be used with an assessment of T27 - Stakeholder Management to
get insights into issues and concerns. The map can be used at governance
sessions to frame discussions on some of the issues and review the validity of
action plans to resolve them.
Tips on how
Choose people who know the project well and also understand the business and
political landscape to create or critique the map. This may require adding people
to the project team. The need for confidentiality may restrict who can be involved
in the early stages of role mapping. It is important that gaps in understanding and
assumptions made are recorded and identified as the map is used.
Mapping the impact of different options may be a useful tool to help decide the
right option to implement more people impacted = more chance of failure! This
should be done in the planning phase.
Tips on when
The map can only be created when the project scope is well enough understood
that the people who are impacted can be mapped quite often this is possible
when the first draft of Project Definition is being created.
The map should be created as early in project life as possible. This may be
before the project team has been identified and up to speed and help to define
either the project team or the governance structure.
The map should be reviewed when significant milestones are achieved
especially after key gate decisions- the gaps in knowledge should get smaller
over time.
Early in the project the maps may identify roles and units within the organisation.
By the time the project moves into implementation the detail should include the
name of each individual.
Estimated Timing -Time to create a map will vary dependant on complexity - a
map including Stakeholder Analysis, Commitment Model and action planning
could take 2-3 hours.
Purpose
Outcome
Structure
Core Tools
Rating
Blue - Intermediate
Purpose
Outcome
Structure
The LNA for a project will use a range of existing data (often the rational for the
project) and newly sourced data (testing assumptions)
Identify the To State - The awareness, knowledge, skills and application level
required to achieve the business outcome for each impacted group.
Assess current capability level - Create methods & metrics by which to test the
current capability across the impacted audience (FROM state) e.g. online test,
task simulation, focus groups, pulse survey, 360 feedback.
Execute assessment & gap analysis - Balance time, cost and breadth v depth
of assessment.
Gap analysis and action plan - Document the FROM - TO state, identifying the
gaps and opportunities to be leveraged.
Example online needs analysis completed by the individual (using survey monkey)
Example SFIA skills framework used in Global IS. Completed by the individual and verified by
the Line Manager
Tips
Interdependencies
Take insights from:
T13 - From To
Purpose
To apply the appropriate design and delivery methods to the required learning
solutions
To allow for flexible learning in order to support a population that is diverse in
terms of learning styles, languages spoken, geographic locations and ways of
working
Outcome
An inclusive learning culture, matching capability build to your employees learning
preferences to help accelerate their learning
Clear support materials for both the learner and the facilitator (elearning, session
outlines, learning workbook, job aids etc)
Effective utilisation of resources (balancing time, budget, facilitation and
infrastructure)
Capability plans align to the Diageo Learning Strategy and contribute to high
employee engagement results and are a source of attraction in the external
market
Structure
The design of the capability build should involve a review of existing learning
solutions from across Diageo to avoid duplication of effort, and to ensure that new
messages are embedded into other learning outside of your immediate project
scope. This ensures a sustainable learning outcome
Examine the outputs from the Learning Needs FROM TO Analysis
Explore the constraints/ opportunities available e.g. Quality, Time, Cost, Resource
Identify the appropriate blend of learning methods to meet the knowledge, skill or
application needs
Identify the evaluation mediums to be utilised throughout the capability activity
plan
Design the capability build solutions & access methods considering learning styles
and the diversity of your learners
Example classroom training
using interactive exercises, in
multiple languages
Tips
70% of learning takes place through doing (applying knowledge and skills on the
job, collaboration with others, making mistakes), 20% through assessment,
feedback and coaching, and 10% through formal learning methods (classroom
training, e-learning modules, lectures).
Be very clear with stakeholders the impact of learning through doing. Can
mistakes be made and rectified quickly. Is time pressure to complete tasks
quickly a key. Test the output of this exercise to ensure it is realistic and use the
results to inform the capability build design.
Create/ redesign learning objectives clearly before considering the method to use
to achieve the desired outcome; what do you want the learner to know, be able to
do and what support with they get when they apply the new knowledge or skill in
reality?
Think about how you will stimulate the learner. How do you want to learner to
think or feel during and after the learning activity; motivated, reflective, excited,
inquisitive, confident?
Use the actual work environment (or simulate as close as possible) to ensure that
the capability build is as close to the actual application environment as possible.
Using peers or leaders from the team where possible uses the existing skills
within the user group, and ensures that these same people can be a sustainable
support to the application of this learning long after the trainer has left.
Involving the end user in the design process as much as possible will act as an
early engagement tool for your project (this can include focus groups, pilot
workshops, beta testing of e-learning modules).
Think about the speed at which people absorb information. Using a self directed
e-learning module, listing to an audio recording, or reading an article before a
face to face session will help those people who require more time to absorb new
information. This may be because this person is totally new to the subject, or
they learn best by reflecting before presenting their questions. The information
may not be presented in a learners primary language, and whilst verbal dexterity
in a secondary language may be high, reading or immediate application of that
new knowledge may be slower.
The last participants in a rollout of modules should get the same experience as
your first (e.g. the SL from the function does a 15 minute context setting
introduction, however cannot commit to doing this session for every group.
Consider having the session recorded for future groups so that everyone has the
same opportunity.
Consider the total cost of the solution, eg having an interactive e-learning module
designed at a cost of 50,000 is far more cost effective for a rollout to 1000 field
based people (50 per person) instead of the cost of transport, the time out off
the job used travelling before and after the learning activity. In addition this
method will allow people to learn when is convenient to their ways of working.
This method however may not be appropriate if the size of the group was only 50
(1000 per person).
When collaboration with others is essential, a self paced e-learning module in
isolation will not be appropriate regardless of the group size, however using a
virtual learning classroom will avoid unnecessary time away from home for the
participant, and the associated costs to your business. Equally a self paced elearning module with a follow up Telecon & webex to take questions and test
understanding may be an excellent solution.
Your functional capability team, or the Global Learning & Development Manager
will be able to coach you further in Learning Design and Methodologies.
Interdependencies
Take insights from:
T29 (Tool II) - Learning Needs Analysis T29 (Tool III) - Capability Build Execution
Plan
Previous learning activity evaluation
results
T29 (Tool IV) - Learning Measurement
and Evaluation
T25 - Communication Plan
Purpose
To plan the roll out of the capability build in line with project timescales, business
constraints, and participant and facilitator resource availability
Ensure the wider project plan remains on track and within budget through regular
status reporting, and stakeholder management
To increase participant engagement in their learning lifecycle with Diageo in an
engaging manner.
Outcome
An effective learning management process; with minimum time spent by the
participant on admin and maximum time spent on learning activity and
application
A clear calendar of activity which incorporates all learning activity and associated
resources so that time and cost expectations are transparent
CARM and procurement process rigour is applied to all external supplier
relationships and intercompany cross charging
The desired capability outcomes are achieved and sustained
Structure
The capability build execution plan is often part of the much larger project plan and
will follow the same best practice principles with regard to cost management,
milestone tracking, and risks and issues mitigation.
Determine cost schedule and charging mechanism/ budget codes in line with PtP
guidance
Agree roles and responsibilities of the team (project team, subject matter experts,
facilitators, line managers, administrators)
Agree and gain sign off on the activity plan for both individuals and teams
(communication, dates and times of specific sessions, pre & post work, and time
for application and follow up)
Create calendar of events & schedule offerings/ instances
Manage resources (materials, Webex / Telecon details, room bookings,
refreshments etc)
Execute plan with regular status reporting to project team
Tips
Executing the plan often happens at the busiest stage of your project. Be sure to
consider all the demands on peoples time and energy, and ensure that the plan is
agreed by the main stakeholders to avoid any delay
The line manager has a core role to play in the embedding and measurement of
capability application; ensure they are sufficiently engaged in their role and
responsibilities
Do you have the same people responsible for delivering against every activity?
Will your participants suffer from knowledge fatigue? Do participants have enough
time to apply their knowledge and skill before learning something else ?
Consideration should be made to predictable business activity which will stall your
activity plan (e.g. merchandising days, business results announcements, run up
to Christmas supply production). It is not just the participants who may be
constrained, key speakers and facilitators may be unavailable, or room availability
may be low.
Ensure that you are aware of key dates; national / cultural holidays, annual leave
peaks, and as general rule do not schedule activity on a Friday afternoon when
participants are not at their normal place of work (concentration levels
significantly dip when people are thinking about the motorway traffic)
Using the Diageo Academy to schedule classroom, elearning and virtual
classroom will automate many processes (sending out joining instructions, Webex
details, track attendance, provide status reports, assist with cross charging). This
will significantly reduce the admin time for both the participant and the project
team member tracking the activity plan
A blended learning approach must be maintained to ensure the learning
outcomes are achieved.
It is important to make your activity plan sustainable for both current participants
within the plan and new team members who join at a later date
Your functional capability team or the HR Talent Delivery team will be able to
coach you further, in building an execution plan
Interdependencies
Take insights from:
Purpose
To gauge the immediate response to learning activity and make in the moment
changes to the effectiveness of the activity ensuring that it fills the identified gap
in knowledge/ behaviour change defined in the learning needs analysis
To monitor the degree of business readiness of participants to the future To
requirements and course correct where necessary
To learn how successful the organisation is in using learning to drive sustainable
performance improvement
To identify lessons leant for future change capability build plans
Outcome
Learning activity achieves the desired To state
Delegates have the necessary tools and are motivated to realise and sustain the
change project
Capability build plan achieves its desired outcomes in the most time, cost and
learning efficient manner
Structure
The recognised evaluation methodology in Diageo follows Kirkpatricks 4-stage
model of evaluation.
Level 1 Immediate Response to Learning - Conduct an immediate
participant reaction at the end of the learning activity
Level 2 Knowledge and Skills retained - Measure the learning taken place in
terms of knowledge and skills through questions, assessment, or simulation.
Level 3 Individual/ Team skills application or behavioural change - Assess
the skills applied and behavioural change of on the job performance
Level 4 Organisation Use measurements to understand the effect on project
outcomes and the sustainable solution
Do something with the outputs !!!
Tips
Ensure you take action as a result of the evaluation insights.
Learning evaluation can become an industry in itself. Ensure that the inputs
justify the outputs and you do not suffer paralysis though analysis with no useful
insights
Typically more time is spent monitoring the knowledge retained than application
of that knowledge. Too often we leave the 70% informal learning to chance and
do not have adequate follow up
Use online tools wherever applicable as this normally reduces the collation time
and allows more immediate insights to be attained
What to evaluate should be designed in the Design and Methodology stage, and
often use the same methods as those used in the Learning Needs Analysis stage
Your functional capability team, or the Global Learning & Development Manager
will be able to coach you further in Learning Evaluation
Interdependencies
Take insights from:
Rating
Green Easy
Purpose
To assess whether the business and individuals impacted are ready for the change that is
imminent.
To measure readiness of the business and individuals impacted through survey
questionnaires across four key dimensions: Awareness, Understanding, Acceptance and
Alignment.
Outcome
A common view and agreement to where we are and what needs to be done to ensure
the change will be successful.
Support for a go/ no-go decision to begin implementation of the change.
Structure
Usually takes the form of a questionnaire of the individuals impacted, ensuring all change
activities are having the desired impact of getting the business ready for the change.
Typically, the survey is done via Survey Monkey shortly before the change is due
to be implemented. May be sent to all or a sample of individuals impacted.
Respondents should rate their current perceptions of statements, through Definitely
Agree/Agree/Neutral/Moderately Disagree/Definitely Disagree.
Results from the questionnaire are then summarized and discussed by the steering
committee / those sponsoring the change locally:
Definitely Agree and Agree are Desirable
Neutral indicates improvement areas
Moderately Disagree/Definitely Disagree indicates areas for immediate
remediation.
An action plan should be developed based on the questionnaire results, if necessary to
course-correct for ALL Moderately Disagree/Definitely Disagree responses. Depending
on the situation, these interventions may be necessary before the change is implemented.
Interdependencies
Take insights from:
Go-Live decision
T27 Stakeholder Management
T25 Communications Plan
T29 Capability Assessment & Build plan
T19 Risk Footprint
Page 168 of 176
Tips
Sign off of the survey results and necessary plans is typically done by the Sponsor and/
or the Steering Group.
If the sponsor decides to move ahead to implement despite business readiness
assessment indicating problems ahead, this should be clearly identified as a risk
and appropriate risk mitigation plans put in place to address these.
Questions in the tool are example questions. They are not prescriptive and can be
tailored/amended to ensure they are relevant to the required audience.
Can be combined with Communications activities if required.
Target audience for the assessment survey should include, but not be limited to the
following groups:
Business Acceptance Group (BAG) individuals
Market Champions
Stakeholders
End Users/ Individuals impacted
Collect demographics to ask respondents to identify which part of the business/which
group they are part of in relation to the project; this will help identify where actions are
required for specific functions/populations.
The timing should, ideally, ensure results are available before the element being tested
has gone beyond the point of no return!, so that a no-go decision is still possible.
For big change programs it may be better to test readiness for focused elements, (eg
implementing in geography, go live for a specific system)
Though principally undertaken before go-live, it can also be used as a pulse check over
the life of the project and the same questions can be asked during different phases to
check on business readiness progress.
Survey Monkey web tool is usually used as the main application for this activity.
Could also undertake these questions in a face to face interview with key
stakeholders. If used in this way, you should take the opportunity to really probe
them as to why they are responding in the way they do, especially where their
responses indicate the business is not ready for the change.
Use in conjunction with Stage Gate checklist, standard project progress reporting, issue
and risk management, and training and communications assessments to obtain full
picture of business readiness.
Possible actions to course-correct for responses that indicate the business is not ready
for the change would include but not be limited to: further stakeholder engagement in
specific functions/areas of the business; additional/follow-up training; set up of additional
post go-live support arrangements/materials; further communication, including one-toone/location specific briefings if applicable; competency checks where new
processes/systems are to be used and people do not feel comfortable with them. Any
additional activity should then be followed up with further business readiness assessment
for that part of the business.
Category
Awareness
Understanding
I understand how the changes the project will bring will affect me personally
I understand when the change will be implemented
I believe the change is really needed
I am confident that sufficient resources have been made available to support the
change
Acceptance
Alignment
Glossary
Glossary
Although all terminology has been standardised, we know within Diageo that we love
to create our own language.
A glossary of key terms has been compiled to help clarify any words you may not
recognise, or be unsure of the meaning.
Term
7 S's
Accountable
Explanation
The McKinsey 7 s framework is a way of describing the way a company is
organised and what it does. It is the basis for the possibility identification
tool
A person who is accountable for a change is the individual who the
organisation has charged with making sure the change happens
Advocate
Alignment
Analyse
BAG
Capability
CARM
Cascading
Sponsor
Challenge and
Build
Term
Explanation
Change curve
A representation of the way that people react to change and how that
reaction develops over time. Based on extensive research, initially through
medical studies of people reacting to serious illness, and widely accepted
as the instinctive journey for people when faced with change.
Commitment
(financial)
Commitment
(personal)
Control Authority
These individuals provide one off expert input to a project e.g. IS Systems,
Finance, and Legal. Where more significant input is required these
individuals should form part of the steering committee.
Cost Benefit
Analysis
The broad term used for the financial analysis of a change, or for
assessing the options that may be the solution for the change. Detailed
analysis of payback or NPV will be part of this.
Deliverable
Design
Elevator speech
End State
Engagement
Facilitator
Term
Explanation
Flow diagram
Framework
From To
A core tool describing the current state and the end state when the
change has completed
Gate (stage)
The formal closing of one stage of a change / project and moving in to the
next stage. This may be done through review of a document, but more
usually through a meeting. Additional gates may be put in the middle of
any phase of the change the purpose of these should be clearly
understood across the project and aligned on within the governance
structure.
Gatekeeper
Govern(ance)
Implement
The 4 formal stage of the change project, in which the change is formally
launched and executed
Initiate
st
Interdependency
A separate change or event that will involve activity that will have a direct
effect on the outcome of the change
KPI
Manage (a
project)
To run the project by organising the work carried out by the resources on
the project and to oversee the progress of the project. Often confused with
Governance. The Sponsor, Change Manager and Project manager need to
be completely aligned on who is doing what within the change.
Mandate
Authority to do specific things formally given from the correct authority level
within the governance structure.
Methodology
Term
Explanation
Milestone
Mitigation
The means by which a risk is made less significant, either by reducing the
impact if it occurs or by reducing the likelihood of it happening
OND
Pilot
A test of the change, either the solution or way of implementing it, in which
it is implemented in a controlled fashion with a small subset of the target
population. The aim is to iron out any problems ahead of full
implementation. Pilots should be reversible, or highly flexible if this is not
possible other forms of testing should be used to prove solutions or
methods.
Project Definition
A document that summarises all the key aspects of the change, both what
it is and how it is being done. This is a document that will change as the
project changes over time. It can be referred to by lots of different names
PDM; Project brief etc.
Project Manager
Project Team
RAG
Regression test
Resource
The people who are formally responsible for doing things to make the
change happen.
Red Amber Green a way of measuring performance or criteria. The
standard approach is Green = OK; Amber = some problems that need to
be resolved, but nothing serious enough to stop the change or require
significant intervention; Red = major problems, serious enough to
potentially stop the program, so requiring significant intervention to put right
Testing that the change will not affect processes or activities that it is not
intended to affect. Often used in relation to systems changes, but should
be a consideration in any change.
Something that will be formally used in the project to make the change
happen. Mostly used to describe people, but can be used as a term for
money.
Risk
Used to describe an outcome that is not planned or intended, but that may
arise from the change. The outcome will be, in some way, worse for the
business. There is a tool for Risk Assessment and Management
Root Cause
Analysis
Scope (in)
Term
Explanation
Sponsor
A formal role within the project structure. The sponsor is accountable for
the change happening and therefore is the ultimate decision maker. They
can stop or start a project and provide the resources for the project.
Sponsorship
Stakeholder
Steering
Committee
Success Criteria
Sustain
Swim Lane
UAT
Workstream
Zero Base