The SDL Tridion MVPs were chatting on Skype last week, and the subject of workflow came up. One MVP told us he was working on a particularly interesting workflow challenge, and another shared the fantastic one-liner “Rule #1 for SDL Tridion Workflow: Don’t do it”.
Now based on my last post “Welcome back SDL Tridion Workflow” I thought it would be interesting to take a look at why so few clients implement SDL Tridion’s workflow solution for managing their content. After all, I bet 9 out of 10 clients list workflow as a feature in RFIs when making their WCM selection shortlists.
- I believe workflow is one of the least explored areas of the SDL Tridion WCM offering. As such, the knowledge among partners and consultants in the field is very limited. No consultant will talk-up a product feature that they don’t fully comprehend, so most workflow implementations get pushed back to second or third phases of their implementation. Often resulting in workflow being pushed back indefinitely.
- Very few clients really understand the business processes behind the creation and revision process of their content. Again, leading to workflow implementations getting placed on the back burner.
- Those clients who really do understand their content creation and revision process often fail to differentiate between tasks and interactions that are informal processes that occur between colleagues compared to tasks that need to be formally managed with a rigid business workflow. This often results in overly complicated Workflow Process Definitions that end up stalling the content creation and revision process when fellow editors are unavailable to work on items assigned to them.
- Content editors often work on batches of items that need to be processed and released in packages. Implementing such a solution is often very timely and expensive.
- There is no out-of-the-box solution for notifying editors when items are assigned to them. As such it is common for items to sit in workflow until the assigned individual actually logs into the SDL Tridion GUI.
I genuinely believe that each of these 5 issues can be easily addressed, and make the SDL Tridion workflow offering a standard in all implementations.
- Lack of understanding of a solution can easily be addressed by partners and consultants simply researching the product. The current offering is really capable of achieving many client requirements. Those of you, who have actually implemented workflow, please share your solutions so that we can all learn from them. Understanding of the product will lead to feedback and evolution of the current offering.
- Helping clients understand their business processes can often be facilitated through a series of interviews, and simply observing the client’s interactions with their editorial counterparts. Even if workflow becomes a phase two feature (which I actually recommend), have a business analyst watch the authors and editors working before attempting to define the processes for the CMS.
- This one is somewhat paired with #1. Once more consultants understand what SDL Tridion Workflow can really bring to the table; it is much easier to help clients break down their 20 step business flows to a few simple steps inside the content manager.
- This one was pretty hard to do with all releases up to SDL Tridion 2011 SP1, but I have high hopes from the new “Bundles” based solution in the coming release.
- Notification I will address in my next post, but if we are lucky, we may see that appear in a future release too.
So that is my two cents, what excuses do you have for not implementing workflow in your SDL Tridion implementations and what features would you like to see in the next release?