Launching a project is only the end of the beginning

There are many different perspectives on being ready. IT scared the communication division by announcing project launches that are way to early (normally it’s the other way round).
The problem, as it turned out, was that IT only considered development and some bugfixing, but no content creation, no migration, no rollout and marketing. That leads to announcing bad deadlines: Sending out projectplans that announce an launch but mean “ready to enter content” is closing to setting up the project to fail. – Users expect a launch, but what they get is an empty portal (or even nothing, because the emtpy portal won’t be public).

I have to think about some clear way to demonstrate these differences and the simple, factual dependencies in a media-project – so that they survive every modification, reengineering and adpation to templates and projectplans…

Leave a Reply

Your email address will not be published. Required fields are marked *