IFTTT (If This Then That) is a service that lets users connect multiple different mobile apps based on a simple rule. “This” is the process trigger, “That” is the process action. Today the tool lets users rapidly create connections between 71 applications or what IFTTT calls “channels”. The simple workflows created between channels using the IFTTT rule are called recipes and can be shared within an IFTTT community.

If This Then That

So what’s the big deal?

In the BPMS suite we’ve been executing simple and complex business rules like If This Then That for years. The emergence of IFTTT is important because it does two things that BPMS does not do well; integration and simplicity.

Many business processes cut horizontally across organizations and as a result touch multiple business applications. There is thus an ongoing drive among BPM and Case Management vendors to continuously enhance their integration capabilities. This is however a continuously moving target and integration remains one of the greatest obstacles for the successful deployment of both cloud and on premise BPM solutions, often adding considerable cost and time to projects.

When it comes to the integration of cloud and mobile applications into business processes the difficulty multiplies. We are only just seeing the emergence of smart process applications and on demand business processes. Mobile BPM applications have emerged with integration to back end systems but is any BPM vendor doing mobile app to mobile app integration?

Mobile and cloud app integration is a key IT battleground. As business software users we regularly use mobile apps and on demand software to address business problems. This consumerization of the business IT landscape however sits uncomfortably with IT heavy BPM projects.

IFTTT radically simplifies the process of stitching together and automating web services and as such throws down the gauntlet to other business applications that are heavily reliant on application integration.

Consistent with consumerization IFTTT empowers users to integrate and develop their own workflows. It doesn’t take a huge leap of faith to expect this simple IFTTT rule to be extended to support more complex rules and events and ultimately encroach into the market for workflow and BPM applications.

IFTTT Channels

Peter Whibley
14.00

Intelligent Process Applications

This blog will be about the future of business process, what I refer to as Intelligent Process Applications.

Both Gartner and Forrester have different opinions about the future of BPM and Case Management. Gartner have proposed iBPMS (intelligent Business Process Management Suites) while Forrester have proposed Smart Process Applications. So who’s right? Well in my opinion both are half right. It’s obviously true, as Gartner propose that future business processes will be deployed with more intelligence built-in. It’s also true however that as a consequence of mobility and the consumerization of IT we are moving businesses to an era of on demand business process applications as envisaged by Forrester.

However, as you would expect, both Gartner and Forrester have played a bit to their customer base and in my opinion have given emphasis to features and functionality that while important are really only a subset of greater industry themes. Rather than iBPMS or Smart Process Applications I think the term Intelligent Process Applications is a better description of where the business process management and case management market is headed.

Future Intelligent Process Applications will have four key components (I’ll discuss these in more detail in future posts):

1.    BPM and Case Management

They’ll be underpinned by a BPM and Case Management applications that act as the engine for process automation and employee empowerment. While some business process apps will be rigid and inflexible others will exhibit flexibility with more case management like characteristics and empower participants to adjust processes rapidly in response to changing business and market demands.

2.    Intelligence and Awareness

They’ll possess intelligence. By intelligence however we are really talking about awareness.  Using business intelligence, data, content, social and predictive analytics as well as integration with smart devices intelligence and awareness functionality will be used to alert businesses and employees to key changes in their environment.

3.     Customer Experience

Yes mobility is a crucial capability but it is only a subset of a more important theme, customer experience.  Our personal technology experience has changed our business IT expectations. The app. internet model we have become familiar with in our personal lives is starting to take hold in business, changing not only how enterprises acquire business applications but also how they design and execute their business processes. Mobile capabilities will be crucial to the success of future process apps but only if they are designed with customer experience in mind.

4.    Cloud

The delivery vehicle for intelligent process applications will be via a multi-tenant cloud architecture. The greatest challenge for process app vendors will be to bring the speed and simplicity of the app experience to multi-application process solutions. 

Is this too simplistic? Have I missed something? Will social play a bigger role? I’d love to get your opinion.

]]> https://intelligentprocessapps.com/2013/08/12/intelligent-process-applications/feed/ 0 peterwhibley Intelligent Process Applications