Here is text about running a project

lfjalökfjlasdjkflasjf

fasilfjadsölfkjadsökjfasf

asdfjlkasjfölasdjflödsjfklöadsfj

asdfjkashföldsjhöfjsadlfjkösalfjlök

The overview on the right is an example used for rolling out retail networks. It worked for DK, as well as NL.

Basically the phases worked like this:

  • Each area was a roll-out phase where we’d roll out according to a similar detailed script, an additional one page document.

  • The descriptions would mention anything special needed, like if there’s systems differences.

  • Most teams were involved in each phase, but once or twice we needed additional expertise.

This one is for an event organisation. Here again, the document covered all phases.

And again, detailed documents were additional. Such as the script for all the actions needed on the day itself, or design specifications of the booth and other bits.

For a website launch, we found that we needed most was a detailed script of what needed to be done. So we just kept a list in excel.

Of course certain timings were important, but this was a very concrete task based part of a larger rebranding project. We had some specific documents on the side, instructions with the website hosting company for example, but our project, that still included several roles, only required it to be a list of tasks really.

And it worked.