During my tenure of helping organizations gain greater value out of their BPM investment through adding multiple applications to run and grow their business, it became apparent that while the concepts of governance are widely appreciated, the tactical steps on how to approach the topic are not straightforward. I regularly hear questions such as:
- Why do we need this group/role?
- What is the expected responsibility of this group/role? How is it unique from the others?
- What level of effort is needed to sustain this role?
- What type of individual should be filling this role?
- How do these roles work together to ensure success?
Through this series of Articles, I aim to answer all of these questions by highlighting the primary groups needed in order to provide oversight, guidance, and stability during the rapid growth of your BPM practice, as well as a closer look at a standard structure to reach that goal.
While I will mostly be focusing on large programs with many applications servicing multiple business needs both in progress and deployed in production, the concepts I will cover are critical to success even from the micro view of a single project's lifecycle. The diagram below provides a peek of how each group is orchestrated to create a harmonious whole, even from this small scale:
Your company's corporate culture has its own needs which will feed into your specific definition of governance and alter the roles and responsibilities outlined. No two organizations end up exactly the same. My aim in these Articles is not to necessarily be prescriptive – that would be impossible without knowing the specific personalities and needs within your BPM landscape. Instead, these Articles should be considered guidance on the responsibilities that typically need to be addressed when tackling the governance question.