MM: Let’s get your take on three basic philosophies for workflow. First, we have the top-down, complex, and expensive policy-managed routing systems that can model and automate for complex enterprise-wide workflows. Second, you might have a prebaked workflow system that says, “Here is a procedure.” It’s a matter of turning on and off switches, configuring a prebaked workflow system. You see a lot of those in traditional DAM systems, where basically I’ll call it “workflow light.”
The third workflow philosophy, that we find in Cumulus, says, “We’re going to work bottom up with individual users and say, ‘What does this particular user need in terms of access, metadata and automated activities?” This might entail installing embedded Java plugins (EJaPs) to the end-user client or server-side equivalents of embedded server plugins (ESPs).
This third workflow philosophy enables you to optimize the productivity at the level of activities and tasks for individual users from the server’s entire classes of users or the whole operation.
Would you amend or expand upon any of that?
JK: The only other thing I would amend on that is certainly, I always like to keep the IT professionals in the loop, as well. They weigh in on certain items that will help and protect our organization, as well on the way things should be engineered and how best to do it—not only for the users, but also for the organization.
But yes, you hit it very well, Michael. Very accurately.