Project Story Outlines 2

January 31, 2013 at 1:58 pm Leave a comment

Following on from my previous post I present – part 2!

In these story outlines I’ve tried to focus on making the organisation as the main character, by which I mean the organisation is the thing which is changed by events, for better or worse.  It was surprisingly tricky – I’ve never really played around with non-living things as characters before and I found it awkward to put write from that position.  In the end I think they get my point across and I think these are by far the safer options if you’re going to be writing a project story for any kind of official audience.

Option 3
Type – How the organisation has changed
Events – cross-department communication, preliminary work begun, progress made on improving current systems to a point where they could feed into a system in the future.
Message – Change is happening (and more needs to happen) even if there are no concrete results yet.

Scene – Organisational context for project, the need, desired outcomes etc.

Development – Existing issues are uncovered that need to be dealt with first.  Work begins on the fundamental issues in each department.  Chanels of communication are developed slowly between departments.

Crux – change doesn’t happen quickly enough to warrant continuing with the project

Outcome – Some new channels of communication now exist which will facilitate all cross-department project work in the future.

Option 4
Type – Lessons learned
Events – learned things the hard way
Message – Acquired knowledge for the organisation

Scene – Organisational context for project, the need, but also the barriers that exist from the start.

Development – Project vs management structure difficulties are quickly an issue as are communications between departments and interfaces between technical systems.

Crux – Becomes clear that it would be more beneficial to try to resolve some of the fundamental organisational issues first.

Outcome – Project highlighted important weaknesses in organisational attitude towards projects and existing CRM and technical systems.  This will inform future work to streamline processes and systems.

Option 5
Type – Promotion of the outputs
Events – what the outputs will do for the organisation
Message – Something good has/will come out of it

Note: this is the hardest type to do with the scenario I’ve picked and would work better with a project that actually had even relatively successful outputs (what does that say how about how likely I think it will be that projects will be successful? o_O)

Scene – The project – how it failed and what the lessons learned were.

Development – plan for integrating the lessons learned

Crux – the direct affects of this

Outcome – how this will improve the organisation as whole and help going forward.

These outlines I think are more platable that with the PM as the main character, but minimising or ignoring the place of the actual actors has it’s own pitfalls which I’ll have a look at in my next post.


Entry filed under: Digital storytelling, storytelling for projects.

Project Story Outlines 1 Project Story Outlines – Review

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed


%d bloggers like this: