Enterprise Software Solutions – On Premise, In the Cloud or Managed

Main Considerations for a human workflow

Main Considerations for a human workflow
In this “Knowledge” centric economy, people are often involved in business processes in order to provide decisions, judgments and other inputs that a system on its own can’t produce.
When “people” are involved, there are special considerations that are extremely important. I am listing these considerations at a high level below. I plan to blog about these in more details in the near future.
  •  You need to create a list of roles and users who will participate in the process. Usually, there are three categories of roles – Submitters, Approvers and Workers.
  • You need to detail out what information each person will be able to view and what he/she will need to input.
  • You will need to eliminate repetitive or unnecessary data entry. If there is a way to retrieve the information from backend system, it is annoying to ask a user to enter that information manually.
  • You will need to provide users ways to track status of their requests as well as view their past requests.
  • You will need to provide for escalations when people don’t “behave”. You can find more details around escalations in my earlier blog post.
  • You need to consider how people will be notified of their tasks – email, text alerts, and mobile notifications.
  • You will need to define what tasks are individual and what tasks are performed by teams
  • You will need to handle delegation and out of office situations.
  • You will need to factor in strategies for when a person leaves and has pending tasks.
  • You will need to define governance especially around process ownership and administration.
You need to answer these questions for any/all “Enterprise-grade” BPM/Workflow projects. While this seems like a lot of work, a good BPM solution/Platform (likes of K2 BlackPearl) has features and functionality to navigate you through them.