IFTT

Press Once for Process

/ peterwhibley / Leave a comment

It looks like our homes could soon be invaded by a swarm of buttons. Earlier this year (2015) we had the launch of Amazon dash and now we have flic. Flic takes dash a step further and is a wireless smart button that can be quickly programmed to let you play music, make calls or even order a pizza, all at the press of a button. What dash and flick have in common is that with the press of a button the user is triggering or starting a process. With dash it is the process of placing and executing an order for a consumable product from the Amazon store or in the case of flic trigger a food delivery process.

Press Once for Process

There are other companies out there such as IFTTT looking to simplify how we execute day to day processes and optimize how we interact with mobile applications. In fact it is possible to connect Flic to IFTTT and at the press of a flic button post a Facebook or twitter update. Both dash and flic are obviously Internet of Things (IoT) devices. What they begin to illustrate is the critical relationship between the IoT and process. There is no point in smart devices collecting data and monitoring your environment if we cannot rapidly take action on insights obtained.

Yet dash and flic don’t have a long term future. Why do we need buttons to place orders or trigger processes when we could use our voice? Today, three of largest global IT organizations — Apple, Google and Microsoft — offer voice recognition software. Apple was the first mover with Siri. Google followed with its own natural language user interface, Google Now, and finally Microsoft came to market with Cortana. Why do we have this sudden interest in voice recognition? The answer is the IoT.

With the iOS 8 operating system, Siri became completely hands free, with the “Hey Siri” command replacing initiation of Siri via the home button. In addition, Siri began to integrate with the Apple IoT HomeKit features. At iOS 9 Apple have taken Siri capabilities further putting new functionality into the HomeKit, including smarter Siri controls and support for new device types. Siri and thus voice recognition is a key part of the Apple IoT strategy with voice commands being used to trigger simple processes such as dimming the lights or adjusting the thermostat. It does not take a great leap of the imagination to expect that we will soon be able to ask Siri to book a flight, a meal at a restaurant or to transfer money into a bank account, all hands free and without accessing an app or pressing a button.

So while flic and the Amazon Dash button may have a limited shelf life they do point towards emerging methods of process initiation that will eventually coalesce around voice. In fact Amazon, as well as having the Dash Button, also offer a Wand device that uses voice recognition to place order requests. With so many potential IoT devices, sensors and services, voice control provides a simpler, quicker and more convenient method of interaction with the IoT rather than an app, a UI or a button.

If This Then What is the Future of Workflow and BPM?

/ peterwhibley / 1 Comment

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

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

IFTTT Channels