Skip to Content
Author's profile photo Owen Pettiford

From Business Analyst to Disruptive Innovator – The destiny of a true BPX

For Enterprise SOA to continue to take a hold in the SAP world and make a difference to the bottom line of organizations it is critical that a new breed of worker is quickly matured.   Imagine a world where we have 4 key IT centric roles moving forward :-  * Consolidators : The people who provision the services and keep them running.  * Repository Keepers : The people who govern which services are available and how they can be used.  * Composers : The people who build the services into processes that can be deployed across the organizations.  * Disruptive Innovators : The people who think about new ways to combine services to drive new opportunities and business models   Now the really good news for SAP customers is that SAP is doing most of the leg work for the Consolidators, the Repository Keepers and the Composers.   * For the Consolidators the back-end platform is being service enabled in a way the will deliver enterprise class scalability.  * For the Repository Keepers the Enterprise Services and Process Components are being modeled and described in a searchable repository.  * For the Composers hundreds of xApps and ES Packages are being created which will form the building blocks for company specific composites.   So this leaves the role of Disruptive Innovator aka the Business Process eXpert (BPX). To enable this role SAP is helping to create the BPX community and providing tools that can help inspire the BPX to create new opportunities for their organizations.  It is therefore important that the BPX understands the SAP Tools and how they can be applied to different problems.  I have found it helpful to use the following matrix (without the SAP Tools shown) when running workshops with end-users, to find out exactly what their requirements would involve from a process perspective, are they trying to improve the usability of the systems via UI enhancement or are they trying to automate or control a complex business process….or both.  image   This can then be used to discuss the technical requirements with the IT team. Requirements at the bottom-left can be implemented quickly and usually represent good candidates for Enterprise SOA quick wins. Requirements in the top-right represent a more challenging set of requirements which will take longer to analyze and deploy – but usually deliver a large return to the business.  I hope that you find the matrix useful in both scoping your ideas and understanding how the SAP Tools could be applied to solve them.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Marilyn Pratt
      Marilyn Pratt
      Thanks, Owen.  Matrixes and Quadrants are something that Gartner does well and are useful.
      I would like to see a matrix enhanced with ROI-related visuals for a BPX. ie: cost of implementing or automating the process with a particular tool as compared to the value or quantifiable benefit derived from such an implementation.

      I think the business would be keen to see the revenue impacts of such usages and decisions.

      When you speak of disruptive innovation, do you infer that we may also experience positive results when a particular innovative use of a tool or a new tool, helps change the performance of the activity, or even allows us to derive revenue from performing an activity?

      I would love for others to share experiences of such cost benefits.  That would surely be some of the value that a BPX provides his/her organization.

      Author's profile photo Owen Pettiford
      Owen Pettiford
      Blog Post Author
      Marilyn, This is just one of many Matrices that I use. In the eSOA Roadmap service the Cost/Benefit/TCO is plotted in such as way to help identify the potential candidates.

      Regading disruptive innovation I do think that a new tools can be a great way to show people how things can be "done differently". Often the end result could be achieved before, but having a tool to enable it means more people have the "confidence" to pick it up and do it. Infact all of the tools above do something that can be done another way.

      However the more important role of the disruptive innovator is to path find the new things that could be done (from a business perspective) and give the organisation the confidence to achieve them. People are generally pack animals and need someone to let them know this new stuff is OK :-).

      This is why the SAP Discovery Server for eSOA is so great, it allows the BPX to create in a low risk environment...before asking the organisation to follow them.

      My key message to every BPX is to get their HANDS ON THE SOFTWARE - An ounce on action is worth a ton of theory

      Author's profile photo Former Member
      Former Member
      I was happy to see your "distruptive innovatitor" class for the BPx, but I must share my experience,opinions and thoughts on this whole BPX classification with SAP/IBM/MS/Oracle/Adobe (I just joined the SAP team) I have been with IBM, MS for a few years in a development/test/advisory role. Having said all this, I am a 5-time corporate president/CEO and reengineering-transformation leader, now on my 6th in my 25-year manufacturing/engineering industrial-defense career. I am a radical,inventive and revolutionary change maker, appling hands-on expertise at the master certified level in BPM,BPR,Six Sigma, Lean-Sigma, Lean Enterprise, Omega 8 and CMMI and cannot seem to get the IT communities to understand that they need to "learn, understand, practice" business, not simulation, run a business, get a mentor, gain more insight from operating executives, so you can approach ESOA Etc., in a more effective, value-add solutions approach. I think if we "fellow business process experts" really want to make an impact, form some joint teams, counsels, groups, this is exactly what IBM and Microsoft did, and the value we are providing to the direction, technology and solutions in R&D, testing, sounding boards etc., is evident in some of their new platforms and whats in development.


      Author's profile photo Former Member
      Former Member
      though we are late, SOA is logical development unfortunaltely we still do not have coomon standard to work with. We must keep in mind that most of the consultants in SAP are from eco-system and do not have technical background or knowledge, for them to understand development environment and service repository is going to be challenge.It is important to see how many functional consultants really have courage to get into NWDS and create their own business process, drawing same on ppt or visio is considered easy why? how we can uplift these functional consultant is going to be challenege.