When does the stakeholder need the information? How does she get the right information? On which device is it presented? What does it look like? What is the regularity? Etc.
These roles and requirements are the starting point in determination of the goals of the BPM initiative, its scope, timing and the business case.
Besides this, roles and requirements determine a lot more, i.e. the members of the project team and the project board, the way the process is designed and described, the key-performance indicators that will be incorporated in the process, the way the process is communicated and presented and the way the process can be governed and controlled.
Most of these points in the user-centered approach have been described in the other subjects and chapters of this book. This chapter focuses on the Communication Management aspects and therefore on the BPM user roles used within the process portal.
Once AirTide has designed and modeled their processes the repository contains a big source of data and knowledge. It is important that this knowledge should be presented to the different stakeholders in the most suitable way at the appropriate time.
While setting up the BPM portal, AirTide needs to be aware of the requirements of all the requirements from the stakeholder. All stakeholders will access the BPM portal for their specific view of the process model including detailed information such as:
- business rules,
- organizational entities,
- KPI’s and performance measures,
- system support,
- location data,
- master data,
- risk & compliance measures.
In order to provide this information in the right way, at the right time and according to the users requirements AirTide has created a BPM communication strategy and plan.
The BPM communication strategy and plan contains the answers to four questions[i]:
- What do we want to say? – The message
- When will we say it? – The timeline
- To whom do we want to say it? – The audience
- How will we say it? – The channels
In the case of AirTide the answer to the first question is aligned with the deliverables of each BPM project stage, for example:
- These are our agreed on processes.
- Here can you find them.
- This is how to read them.
- This is how the change process works.
- These are the process goals, the performance indicators and the measures.
- These are the business rules, risks & compliancy regulations and measures.
- This is how you can read and use the process model.
- These are the documents used in the processes.
The answer to question two is related to the project stages. The information is presented at a moment that best suits the purpose of the message.
We can define four stages or communication[ii]:
1. Awareness; during the BPM strategy and set-up, as building blocks are being defined, various process communities are create and continuously informed about the BPM transformation progress and future plans.
2. Pilot; when main BPM building blocks have been established in the BPM transition and pilots are showing first results, all audiences should be informed about the pilots and the overall BPM roadmap. In addition, BPM trainings should begin.
3. Implementation; when the BPM transition has been completed, a continuous communication plan should be set for all audiences
4. Continuous feedback; Throughout the BPM transformation, feedback mechanisms should be in place to measure the progress being made in the communication efforts.
For example; in order to gather the information as input for the process model workshops are held. This is still the awareness stage. In this stage the community existing of HR employees is being informed about the BPM goals and approach. It is important that contributors to the workshop know exactly what the scope is of the processes, what kind of information is needed and how it will be used in creating the model in ARIS using the BPMN language. An example of communication in the second stage is training of people in pilot environments in usage of ARIS Business publisher.
For the answer to the fourth question an analysis was made of all the stakeholders. Stakeholders or the audience is then grouped based on their interests regarding the BPM project and based on what the BPM projects expects from the stakeholder group. Per stakeholder group their interest, the expectation and the used messages and channels, the way the messages are presented as being the answer to the last question, is presented in the communication matrix.
Figure 4: example of a communication matrix
With this matrix and the roll-out of the several communication messages using the right channels B-Air was able to keep all stakeholders aligned and informed.
There are several things to keep in in in BPM communications:
- Make sure all messages are aligned in content and time, and there are no inconsistencies.
- Used channels should be aligned with the message and with the audience.
- Channels used should be easy to access at the right time and place for all stakeholders in the audience.
- Create clear definitions of each stakeholder group. However don’t create to much stakeholder groups and don’t deviate on a too detailed level.
- It should be clear who is in charge of the deployment of the BPM communication strategy and plan; who is the communication officer?
- Have all stakeholder definitions in place before creating the actual Business Process Model so you can communicate the scope, impact, requirements and validations.
- Use the stakeholder definitions while creating the Business Process Model in deciding the modeling conventions such as: the detail level needed, the objects used, the definitions given to events and actions and the naming conventions.
- In selecting the channels make sure you align with the devices used for communications. For example, are people using mobile devices then be sure to align the communication protocol and also the messages.
Next time we will discuss New Developments and Innovations in the final part of BPM Communication
[i] Business Process Management – The SAP Roadmap; Galileo Press; Snabe, Rosenberg et all.
[ii] Business Process Management – The SAP Roadmap; Galileo Press; Snabe, Rosenberg et all.