Vantage Point - 8 points of view for evaluating a BPM product

Today let me tell you a little story, A detective story with 8 witnesses, each with different points of view. This story is based on a Hollywood movie, "Vantage Point"

Wikipedia describes the movie as “a 2008 American political action thriller which focuses on an assassination attempt on the President of the United States as seen from a different set of vantage points through the eyes of eight strangers…Displayed with eight differing viewpoints, an assassination attempt on the president occurs, relayed in a time span of 23 minutes. Each time the events unfold from the beginning, a new vantage point is shown revealing additional details, which ultimately completes the story of what actually took place during the incident and who was involved in the conspiracy.”

Let me introduce the 8 witnesses in my story. Each has a different point of view. The basic idea borrowed from the movie is that we get closer to the answer when we have multiple vantage points. As we move from one vantage point to the next, you will get a piece of the puzzle. When you have seen all the eight vantage points, you will have all the pieces of the puzzle. You will get closer to the answer. 
  1. The Business Analyst: Our first witness is the "Business Analyst" . His job is to model an optimum process that can serve the business and have end-to-end automation. How will he do this? 
    • First he would have to collaborate with the business users working on the as-is process, evaluate the bottlenecks with the As-is process.
    • Next he would need to discover the IT assets that will support him in modeling an optimum process that is executable and meets his business user's expectations from the To-Be process.
    • Simulate this process for various business scenarios and provide a realistic view of costs, units and time.
    • He should then make sure that his process meets regulatory requirements, extracts the right KPIs for the management, make content seamlessly flow with the process.
  2. The Prudent Architect: Now, let us shift focus from our Business Analyst to our Prudent Architect. Imagine you are the old fashioned Prudent architect that each business process must be a function of Business, Applications, Data & Technology architectures in that order. 
    • How will you ensure that your architecture vision is implemented in the way you visualized
    • What are the key factors that will ensure that change in process model does not affect a change in user experience, governance, integration artifacts, data model etc.,
  3. The Smart developer: Now let us put ourselves in the shoes of the smart developer. What does the developer need when implementing a process. 
    • Clear sense of direction: Thankfully our business Analyst has done his job when modeling the process and has already modeled the optimum process that meets business expectations
    • Sound architecture: The smart process developer now enjoys a layer of safety which has been taken care by SCA, service mediation layer, adapters to connect to legacy applications & various underlying transports
    • Ease of implementation : Easy to use wizards when connecting participating applications, people, content. Ability to add rules, analytics etc.,
    • Ease of team development and deployment: The smart developer works in the ecosystem of several others who participate in implementing the process. Together they need a system of continuous integration. When they are closer to staging & production. Ease of deployment of team artifacts is paramount.
  4. The Business Owner: How would a business owner think about process automation. We know one thing about her, she would certainly think out of the box, unlike our Prudent Architect. If she can save money & time with stable processes, she will consider automating the processes end-to-end. 
    • How will she get visibility on how value is being made by process automation.
    • How will she ensure that people responsible for their tasks are turning around in time delivering maximum profitability & user satisfaction
  5. The process participant: You are the quintessential process participant, you participate in many processes quite frequently. Right from the time when you were on-boarded into your company, when you salary account got created, when you applied for that home loan, when you procured something, when sell something, when you file you tax returns etc. You cannot escape from participating in a processes. I am sure you you've had some expectations from the processes you've participated in. Couple of mine are
    • I'd like to know the current status of the process I am participating in
    • Could I be notified when things are going according the plan, but if there is something amiss, I want to be alerted.
  6. The IT Administrator: IT administrators fear a lot, they worry about micro events that occur in the infrastructure they own. Any uncertainty in the data & audit traces means that need to act fast. That is why
  7. The Value oriented Management: Imagine you are a value oriented manager who is responsible for business process automation at your company. How would you show value to the business owners. You could do many things, but let us talk about the 3 most important things
    • You could build a business case for BPM.
    • You would focus on automating processes which are low in complexity & high in value first
    • Show business owners how they would save money & time.
  8. The Enterprise: You see, things carry on, because they have carried on. The business has been around for so long and people have this status-quo bias, this inertia which prevents them from change. Moreover, there are people, who don't want this change. Plus, of course, the company depends on the contributions of these very people.I think we all agree that the real cost of automating a process is hardly in the BPM product you choose. The real cost comes in the form of status-quo. 

The choice really is up to you.You can put yourself in the shoes of any of the above 7 witnesses and rationalize your choice. I do know you get closer to the answer when you have multiple vantage points. Having just one vantage point in a detective story is not good enough. Having 8 is rather cool!!

Post a Comment:
  • HTML Syntax: NOT allowed

Oracle Fusion Middleware based Solutions for business use cases.


« August 2016