Frequently Asked Questions

1. Can Maven be used for transitions?

Yes it can, and ideally should be. We would suggest looking at transitions in two ways:

Key point – once you build the model, operations / change can then take over from there to optimize the process further.

2. Who are the ideal Maven users and how much time and effort does it take to train them

Users may be of two types - Basic user (inputting the base models into Maven) and Advanced user (analytics to arrive at ‘to-be’ models). Both these users should have a process excellence/ business analysis skill/ mentality.

Base user characteristics – Some experience with the business domain, has done some process modeling. Training time ~ 2 weeks.

Advanced user – Black belt type person with experience in implementing change initiatives. Training time (post basic training) ~ 2-4 weeks.

Maven specialists are typically available to help mentor/ coach/ review with respect to the first few engagements.

3. Scenarios where Maven can be used

  1. Digital definition of existing operating model (visual tool)
  2. Operating model optimization (“to-be” state)
    • Cost reduction
    • Cycle time reduction
    • Controls configuration and effectiveness
  3. Ideal use for processes that have multiple activities across multiple teams (across locations)
  4. Can be used even where multiple processes are run but across different business areas (not inter-related). While this is an not ideal use (as compared to related processes), the following can be achieved in such cases:
    • Shared services across these business areas (common functions)
    • Cross-skilling – e.g. in an assignment, there were 8 different queues… each of which did not have scale – hence leading to large buffers by queue to address time and control coverage requirements. In this case Maven recommended cross skilling and creating 3 teams; hence reducing FTEs by 20% with better controls! This was done keeping in mind – volume patterns, turn-around time requirements by team, skills, controls (e.g. need to keep activities separated)
    • Point optimization within these processes by business area
  5. Business problems – below is a typical set of business problems that Maven helps to address

4. Benchmarks – does Maven support benchmarks

Maven does not speak to industry benchmarks by process. But it enables the user with analytics that can help with benchmarking initiatives within the process model:

5. Can Maven help with identifying which re-engineering levers can and should have higher priority?

An advanced user can look at the following analytics to make initial hypothesis:

6. How does Maven compare with other tools?

To our knowledge, there are no comparable tools that cover the breadth and depth of functionality with respect to operating model design and change as Maven does.

There are certainly great tools in the market that address specific aspects of an operating model…. process repository/models, simulation engines, risk & controls, HR complexity/ skills etc.

Maven differentiators are:

  1. Ability to look at an operating model in totality – due to this the speed to arrive at ‘to-be’ optimized models is a few weeks. Existing mechanisms and tools take 3-6 months (OR more) to arrive at ‘to-be’ state
  2. Better results – Maven algorithms help with ‘multi-variate’ optimization to help identify ‘a’ point on the efficient frontier (refer diagram below). The efficient frontier is a curve based on ‘current constraints’ ….. cost v/s time v/s controls.

The key difference as compared to existing tools is that Maven provides ‘an’ answer on this curve as compared to simulation points (e.g. Monte Carlo). The issue with simulation is that it is just that…and it is time consuming, is probabilistic, needs advanced statistics, there are far too many different points without pointing to any in specific… how do you choose where you want to be with any degree of assurance?

7. Availability of data is often a big challenge. How can this be addressed?

While it is important to provide Maven the right data (accurate, complete), it is noted that

8. Can Maven handle Volume and AHT variance

Volume variance: AHT variance: This can be captured using ‘decision’ boxes in the process map. So, if there is an activity that takes 3 minutes or 15 minutes depending on the complexity, break this into 2 activities using a decision box.