logotyp

Analysis guidelines

Analysis guidelines

Beware of analysis paralysis when you process inventory. Triage first, then prescribe a solution.

When doing analysis on a large number of business processes, trying to do an end-to-end analysis for each process, one by one, is not advisable. You should balance the time and effort with the benefit to be effective. In this section, we provide several guidelines for bulk analysis and how to do two levels of business analysis in Blueworks Live.

Level 1 analysis

Level 1 analysis should focus on looking at symptoms and leading indicators of opportunities for improvement. Level 1 analysis seeks to categorize each process in the inventory within the Process Improvement Tactics matrix. The categorization paves the way for Level 2 analysis.

The Process Improvement Tactics matrix represents the high-level generic recommendation that the process is likely to benefit from. The matrix also implies the type of Level 2 analysis that should be performed to obtain specific recommendations for each category.

As a part of doing Level 1 analysis, we suggest that the following attributes be recorded (as detail fields if using Blueworks Live) for each process model in the inventory:

  • Process level attributes
    Table 3.2.6/1
    Process attribute Description
    Volume On average, the number of instances of this process that are started per year
    Total Cost On average, the activity cost of each instance of the business (hard cost, opportunity cost, rework cost, risk exposure costed average)
    Total Benefit On average, the dollar value of the benefit per instance to the business; for example, revenue, customer satisfaction, brand loyalty
    % Rework in the process Amount of time that some or all of the process needs to be redone to have an acceptable outcome.
    Potential Automation Benefit Whether this process benefits from automation. The analyst can quickly provide an instinctive answer to this question without extensive calculation or statistical analysis. Answers include high, medium, low, or none.
    Confidence in Analysis The confidence level of the analyst that the values provided for the fields reflect reality. Questions to ask are: Were you talking to the correct people? Are they biased? Did you spend sufficient time validating? Are you extrapolating too much? Answers include high, medium, low, or none.

  • Activity level attributes
    Table 3.2.6/2
    Activity attribute Description
    Volume On average, the number of instances of this process that are started per year
    Total Cost On average, the activity cost of each instance of the business (hard cost, opportunity cost, rework cost, risk exposure costed average)
    Total Benefit On average, the dollar value of the benefit per instance of this activity to the business; for example, revenue, customer satisfaction, brand loyalty
    Integration Effort To automate this activity, whether a significant effort is needed to build an integration to a system outside the BPM platform. Answers include high, medium, low, or none.
    Value Added Whether this activity is beneficial in any material way to the process itself or other dependent processes. Answers include high, medium, low, or none.
    Potential Automation Benefit Whether this activity can benefit from automation. The analyst can quickly provide an instinctive answer to this question without extensive number crunching or statistical analysis. Answers include high, medium, low, or none.

Level 1 analysis can be done by categorizing permutations of the values of four basic fields (Volume, Cost, Benefit, Automation Effort) from the above set of activities, against the Process Improvement Tactics matrix.

If you captured these fields in your Blueworks Live space, export your space to a tool such as Microsoft Excel to generate the type of analysis shown in the following section.

Typical Level 1 analysis mapping

Table 3.2.6/3
Process symptoms and attributes Applicable process improvement tactic
Volume: Low
Cost: Low
Benefit: Low
Automation Effort: High
Leave Alone
Volume: Low
Cost: Medium
Benefit: Medium
Automation Effort: High
SOP Optimization
Volume: Medium
Cost: Medium
Benefit: Medium
Automation Effort: High
Blueworks Live Automation
Volume: High
Cost: Medium
Benefit: High
Automation Effort: Medium or High
BPM Swivel-Chair Automation for Consistency
Volume: ? (implies unknown)
Cost: ?
Benefit: ?
Automation Effort: Medium or High
BPM Swivel-Chair Automation for Visibility
Volume: Medium or High
Cost: Medium or High
Benefit: Medium or High
Automation Effort: Medium
Hybrid BPM Automation
Volume: High
Cost: High
Benefit: High
Automation Effort: Medium or Low
Full BPM Automation

Level 2 analysis

A good way to think of the levels is as follows:

  • Level 1 analysis is as an initial diagnostic and triage tool for processes.
  • Level 2 analysis is the subsequent prescriptive solution that can alleviate the foremost detrimental symptoms in the process.
  • Level 2 Analysis should focus on building a business case and specific process improvement recommendations.

Table 3.2.6/4

Applicable process improvement tactic Level 2 analysis
Leave Alone Rationale for why this process should be left alone. An “anti” business case.
SOP Optimization
  • A set of recommendations for modifying standard operating procedures without introducing any automation
  • A new to-be process for documentation in Blueworks Live
Blueworks Live Automation
  • A new to-be process built as an automated process application in Blueworks Live
  • The use of standard Blueworks Live reports for automated process applications
BPM Swivel-Chair Automation for Consistency
  • A new to-be process built for documentation in Blueworks Live.
  • A new to-be process built for swivel-chair implementation in BPM.
  • A business case for the effort involved in implementing the above, outlining the quantifiable consistency benefits to the business unit funding the initiative.
  • An analysis plan that eventually leads to a reclassification of this process within this matrix
BPM Swivel-Chair Automation for Visibility
  • A new to-be process built for documentation in Blueworks Live
  • A new to-be process built for swivel-chair implementation in BPM
  • A business case for the effort involved in implementing swivel-chair, outlining the quantifiable visibility benefits to the business unit funding the initiative
  • A limited pilot release plan for the swivel-chair implementation, to minimize the impact of dual work inherent in swivel chair
  • An analysis plan, which eventually leads to a re-classification of this process within this matrix
Hybrid BPM Automation
  • A new to-be process built for documentation in Blueworks Live
  • A new to-be process built for Implementation in BPM, with some integration to back-end systems
  • A business case for the effort involved in implementing the swivel-chair, outlining the quantifiable benefits to the business unit funding the initiative.
  • A limited pilot release plan, if necessary, for the swivel-chair implementation, to minimize the impact of system stability and potential swivel-chair work in Release 1.
Full BPM Automation
  • A new to-be process built for documentation in Blueworks Live
  • A new to-be process built for Implementation in BPM, with integration to all necessary back-end systems
  • A business case for the effort involved in implementing the swivel-chair, outlining the quantifiable benefits to the business unit funding the initiative
  • A limited pilot release plan, if necessary, for the swivel-chair implementation, to minimize the impact of system stability in Release 1