Showing posts with label process. Show all posts
Showing posts with label process. Show all posts

Wednesday, 29 May 2013

Business learning from walking: 1. The plan is not the event

Picture from grough.co.uk
Advice is never to leave for a walking adventure without a map and compass – and a sandwich, drink and set of waterproofs is also a good idea.  In business we have our plan as our map. But just as the map we read and mark while sitting in the comfort of our warm and dry home, the plan we create in our offices is never going to be what actually happens.

 A tree may have fallen across the path – a barrier to change is discovered that the plan didn't take into account.  Someone twists an ankle – a key staff member goes off on long term sickness. It snows – a new directive from on high impacts the organisational plan


Never set out without a plan, but never assume that having spent hours (or days, weeks, months) on the plan that the event is now sorted. The plan is prework. No imagining beforehand can take the place of an actual walk under the trees, beside the sea or over a field. Similarly, no amount of planning can predict the actual path and experience that any organisational change will take. 

Tuesday, 29 May 2012

Managing the legacy of your project

Ending a project is as chaotic an affair as the start up. After the flurry of the beginning and the more measured stage of making progress, we are then faced with wrapping things up.  So what do you want to have as the legacy from your project?

Mostly it's all about figuring out how to keep the website going, debating where to put the useful resources that have been developed, and managing the process of celebrating results and saying goodbye to project teams.  But is this enough?

Project outcomes are good - and always worth advertising.

But what is your legacy? By legacy I mean the long term, sustainable, "thing" that has resulted form your program. Sometimes this isn't seen clearly until years later. There's an excellent paper I commend you to read which covers the difference between people, process and product legacies.  I particularly like the "reuse" concept.