What should you look for in your workflow tool? #2

Welcome to the second in a series of checklists that will help you evaluate workflow tool vendors. This week we focus on Tooling.

The design tooling for building workflows must include:

What Why?
Support ‘point and click’ so business users can build workflows Applications can also easily be built by (non-technical) business users in an intuitive way
Support developer tooling so professional software engineers can extend workflows Some apps built by the business can become so successful that the dev team need to build out the sophistication beyond the skills of drag and drop business users
Be brandable Allows you to make your applications look and feel professional
Be a direct representation of the app i.e. the diagram is the app Making it easy for anyone to visualise the exact workflow required to improve productivity
Allow multiple authors to edit collaboratively Facilitates true in app collaboration between HQ/branches/field personnel/customers etc.
Be extensible Allows your IT team to tailor the tooling to your specific project needs ensuring project success
Be browser based Access, build and modify apps anywhere!
Allow printing of designs Download and share workflow flow charts with others for comment and approval – share your flow methodology with everyone
Be API first To truly integrate and provide real-time workflow, technology must take an API first approach.