It seems Chris Summer’s revelations about the new Workflow have started some nice discussions. A lot of people want to give workflow a proper chance and meaning in the workflow discussions and implementations.
Just to make my point I’d like to work with images. Looking at the main image of this post is what everyone hopes workflow will do to their content flow in the organization. Making every piece of content go into the appropriate lane and reach the destination without delay.
But, a workflow implementation can very easily cause the opposite (see image below). Content is waiting for actions by someone, which can easily become a big
traffic jam of content. At this point solving the jam is more important than editing and reviewing each piece of content. This is usually the moment Workflow “temporarily” gets disabled or simplified.
Anyway, the future brings new hope! Now read some of the other blogs posted about Workflow:
- Will bundles be the saviour of Tridion workflow?
- Aint Got No (SDL Tridion) Workflow… Blues?
- Why we don’t use SDL Tridion Workflow
- Workflow Dreamin’
Chris Summers is reminding is once again how important it is to treat your Tridion implementations like a Star Trek Federation Starship (gotta keep it a bit geeky here…) and maintain a proper log of every action you do. To avoid pulling out your hair after upgrading. I quote:
So my lesson for the day is “Always keep a log of every file you manually change on a server, even if it is a hot fix, and make sure you don’t save any files that you open when debugging”. Now I know that’s not news to any of you, but just in case…. Now you know a way to repair the damage.