Tuesday, 3 January 2012

A Blueprint for Change - Detailing the Future

When embarking upon a change programme or project, it is a good idea to know something about what the programme or project will put in place ... obviously.  Some outputs are often available: the programme 'vision'; the business case; a high level programme brief.  However these will mostly likely not contain sufficient detail of what the business will look like when the programme or project completes.

It can be invaluable to create and maintain a Blueprint.  I stumbled across the concept of a Blueprint in the 'Managing Successful Programmes' guide produced by the UK Office of Government Commerce (OGC).  Prepared as early as possible in the life of the programme or project, the Blueprint describes the business as it will be implemented to deliver the capability and benefits described in the vision and business case.
The Blueprint describes:
  • the business functions, processes and working practices in scope and how they will change
  • management and reporting and governance structures
  • new and amended services with statements of how the customer will perceive, experience and benefit from these
  • how people will be organised and skilled
  • information needs and technology enablers
  • other resources, capabilities, internal and external services
  • relationships with internal functions and new and existing suppliers.
The advantages of maintaining a Blueprint are that it provides:
  • a living summary of high level requirements expressed in terms of the end game
  • a reference to support the business case
  • the single, authoritative source for briefing all stakeholders, programme and project team members
  • a source of material for all communications events, ensuring continuity and consistency of messages.
At a very early stage the programme or project team will be able to better articulate what is being attempted.  It will help those involved see for themselves how their worked might be affected.  It supports the process that helps people respond to and manage their natural response to change.

The Blueprint may also be extended to include high level statements of the timeline and major milestones.  It may include, where required, the 'end states' as they will be at key migration steps or stages.  It may say something about how the change programme or project will be approached - providing high level direction for programme and project plans and initiation documents (PIDs).
Typical contents for an extended Blueprint are included in a MindGenius map that is available for download from Biggerplate - just click 'Programme and Project Blueprint'.
The map is also available as a MindView map by clicking here and a MindManager map on Biggerplate here.
imageThe images used in this post were created using MindGenius.  If you would like to know more about MindGenius, do visit the web site and try the product free for 30 days.

Should you decide to buy MindGenius, Peace of Mind Blog can offer a 10% discount.  Just use the discount code at the checkout on the MindGenius web site or quote the code in any correspondence with MindGenius.

To claim the 10% discount please use the code:  MGELST


Project Timeline Software said...

I really like the idea of your project blueprint. Organization really is key in implementing a big project.

Jamie Nast said...

Steve - What a great application! Good work.


Steve Rothwell said...

Thanks, Jamie. Happy New Year.

I have maintained the Blueprint as a map during initial development and discussions. Later I export to Word for circulation as a 'standard' programme or project document.