Written by Ryan McVeigh – VP of ECM Solutions, Sales
Recently I was in discussion with our team as we contemplated a response to a proposal request. This particular request was heavily focused on workflow which lead to a spirited discussion. It occurs to me that often at Zia, we are cautious about scoping workflow implementation work. There’s good reason for this, as workflows are that type of software in our business that is heavily utilized by our client’s users, so we have to get them right. Workflows also typically have integration points with other pieces of software. What that tells us is that there is reason to be clear on both the technical and user-facing components of the implementation. Interestingly, the Java portion of this isn’t really the hard part. Our team agrees that ultimately writing the software, drawing the diagram and creating the workflow isn’t where the time is spent. I find that I get caution from my team around duration of workflow implementation and when we look closely at why that is, we can attribute the overall effort to three distinct areas.
View the full post at ContentPeople.com now.