We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.
Start a Discussion

What are your BPM predictions for 2013?

Vote 0 Votes
What are your BPM predictions for 2013?

11 Replies

| Add a Reply
  • I predict, in 2013:

    1. Further integration of BPM into packaged applications.

    2. A new emphasis on business process as a service (BPaaS) as a replacement in many cases for on-premise BPM or BPM SaaS solutions.

    3. Either (a) I will post more often to my ebizQ blog, Ground Floor BPM, or (b) ebizQ will kick me off the site. Stay tuned!

    Happy holidays to all!

  • "Work" is a four letter word. "Rework", which means doing the same thing over again, is 50% more effort to write.

    My prediction for 2013 is that the dark secret of IT will finally be revealed. IT is the last bastion that has escaped the spotlight of process automation and it is the worst line of business when it comes to rework.

    In my own research I have seen numbers as high as 30% of all IT effort is rework. I've heard from learned sources it might be as high as 80% of all effort in some IT shops.

    There is an often quoted, but unnamed CIO, who sees rework as his personal "slush fund". When his department has to tighten the belt and do-more-with-less he automates something and show improved productivity with the same resources.

    So if the business wants more value from IT; business needs to start demanding that IT get it's own processes in order.

    IT has to learn what business already knows: you have to fix the root cause of problems and not try to compensate downstream. IT departments have to be taught to say "no" when tasks are handed over that are incomplete, inaccurate or incomprehensible.

    And business process automation is the key in IT as it is in the lines of business.

    Time to write my automated Thank You Note workflow. Happy hols!

  • user-pic

    1. BPM will definitely move permanently to the Cloud.
    Processes are cloud by name i.e. processes span cross departments, cross organizations, cross countries, cross continents. These scenarios are naturally solved by BPM solutions that are on the Cloud.

    2. The Cloud SaaS BPM & Workflow solutions will get bigger, faster and cheaper and more and more organizations will adopt and implement workflow & business process automation solutions.

    3. I believe packaged BPM solutions will find it hard to survive. Business processes are not cookie cutters and cannot be packaged and sold to all organizations alike. Take CRM for example. SalesForce comes up with one way to handle CRM and tries to sell it to the World, however CRM differ from one organization to another. A CRM at a bank is very different from a CRM at a Hospital. Selling one solution to the world is not the answer. What people need is a open BPM & workflow solution that can easily be customized to their specific process.

    Overall 2013 will be a great year for BPM.

  • I decided to wait till today with a response, because what is the use of a prediction for a world that doesn't exist anymore?

    But it seems the Maya used process mining for their predictions and had some non-saying management information.

    So if the Maya's, who were a million times smarter then I am even can't predict the end of the world right, how could I predict for BPM in 2013.

    So I think I will take the ACM approach next year. If Gartner say ISocialCaseCustomerExperience is hot, I will create a workshop for that.

    If Forrester says Dynamic Mobile Process Execution in the Cloud is the Bomb, I will port my BPMN modeller to Mobile devices.

    If my girlfriend says I must spend more time with her instead of being busy with process.....I think I will tell that that role is not assigned to me.

    Merry Processmas!

  • The rise of "adaptive" software where build is deskilled and change the norm, supporting ACM, will bring "BPM" thinking into the enterprise market. As inflexible packaged BPMS slide into the abyss so ERP will be what it is a record of history as an (expensive) accounting system. It will happen someday - I hope in 2013.

  • I predict BPM and those of us focused on it will continue to do well in 2013.

    Also: the demise of BPM will be predicted again, by many.

    Also: growth of firms focused on BPM will not deter those who think it is dying from saying it is dying.

    2014 predictions will likely be a recap of the above... :)

  • As I said so many times in other places: Predictions are useless. Either they are obvious extrapolations of the obvious trends or it is no more than a roulette game. Some win, some loose.

    In regards to BPM I suggest that it will continue to assimilate more and more features of the case management, social and collaboration functionality to stay afloat. Once we consider a PROCESS as a definition of an outcome (defined as such and monitored in the BPMS) rather than a flow-diagram, and business performers can both create and improve them without an BPM expert, then BPMS may actually deserve that name. Today most approaches and products should be called PMA or Process Managed Applications.

    So no matter how much current BPM 'experts' dislike it, the real future BPM will much more look like what is done with ACM today then what most BPMS offer in current software versions.

    And as I said before too, I do not really care what it is called. It was the ACM-interested community who decided on the name and it did what it was supposed to do: It created interest and a valuable debate. It succeeded in changing the way BPM is being seen.

  • Happy new year to you all! As the new year crystal ball is already falling down, the future is just too close to predict,

    I would say, the process will continue to get "SMAC'ked, so does enterprise mindset, social BPM, mobile BPM, process is the Cloud --Process as a Service (BpAAS), and Big Data feedback loop into process., etc. will continue to instill new energy in BPM, and organizations will reap what it sow,the mature processes will underpin business's digital capabilities.

  • I would like to put other way: sensing.

    In the last couple of years I'm sensing what before it could be impossible to believe but it's coming to be true: self-organization.

    This will change the way operations are designed and executed. People will have the power to do it by themselves if the have technology that let them do it seamlessly. If this can be bad news for some some software providers, it can be also bad news for the implementers. Business model will need to be changed because companies slowly will not buy anymore professional services for process design purposes. People that work in the companies will step by step master it and don't need someone from the outside to teach them how to it. The focus will be teach us how to use a system, to be independent and let us design, implement, change and redesign out business process. Solo.

  • user-pic

    Competitive pressures, the convergence of business rules, processes events, and cloud computing are going to fuel further BPM market consolidation. We saw the first wave of consolidation some years ago when BPM technology really started to mature, and I think we’ll see another wave that will be driven by the shift toward cloud services and convergence.

    A shift is underway from traditional business process management, to intelligent business process automation that builds on and extends BPM to include the ability to deal with business rules and events in the same development and run-time platform (adding the "intelligence"). It may be difficult to "retrofit" previous generation BPM systems to easily and elegantly include these constructs, hence the beginnings of a shift from one type of platform to another.

    Users are becoming more and more comfortable with the notion of deploying applications and services in the cloud, particularly where business processes have “spiky” workloads or may be related to a temporary phenomenon such as a seasonal or one-time event.

    To-date, the cloud hasn’t really played a big role at the BPM level in the stack beyond some experimental and early adopter activity. Yes, people are collaborating and leveraging cloud assets for various projects now, but generally the scenario is that BPM development environments are being hosted in the cloud and then the run-time is deployed on premises. I expect that to change and see the cloud as fertile ground for BPM.

    A key issue, however, is that hefty license fees will no longer be relevant or viable in a cloud-enabled world. The cloud model has the potential to disembowel large BPM / middleware vendor businesses that are based on these old licensing models. The next few years could be very painful for some of these companies, but ultimately I think it’s all going to lead to better choices, better architecture, greater affordability and a more open approach by vendors.

    Pierre Fricke
    Red Hat

Add a Reply

Recently Commented On

Monthly Archives