The consumerization of IT is not just about bringing your own devices. I like to think it’s about a lot more – it’s about bringing your own expectations on how to best use technology to get your job done. In the future, that means that those so inclined will be able to write their own software to solve their own problems at work, just like people today create Excel formula or Word templates.
As I briefed a writer about this idea for a paper I’m working on I used the example of people not only wanting to bring their iPhones to their banks to do their banking, they’re going to want to bring their personal finance software application too. This is an example of using API’s to separate out the user experience… customers are not tied to the bank’s narrow definition of their banking platform’s interface, they can create or use their own. What these customers want is programmatic access to their banking information and the services they use to take better advantage of what the bank has to offer.
A Business Benefit: Creating More Prosumers
There’s good research that credit card prosumers, people who know how to make the most of their credit card benefits, are more loyal-to and have a higher satisfaction-with their banks.
It’s not just about the API technology that gives people digital access to their bank, it’s about creating more prosumers to drive brand satisfaction.
Of course, bringing your own software is about more than just bank-consumer interactions. It’s about bank-partner interactions like we saw last week with Amazon & Samsung, and it’s about bank-employee interactions so that companies can do more with less.
Bringing Your Own Software is Boring Unless the Software They Bring Connects to Enterprise Data & Processes
After sharing this example with the writer, he forwarded me an article on the trend to “bring your own software” as a way to improve employee efficiency.
Frankly, I think this article completely misses the point. It’s not about bringing your own software as much as it is connecting your own software into the “digital assets” of the company you work-for, partner-with, or are a customer-of.
The article talks about Asana as a great example of an innovative tool for reducing email that employees who are overwhelmed by email are choosing as a way to get out from under the email deluge. Boring.
What if using secure API’s any employee that chose to could tie an Asana project plan into a project cost structure to do their job better? That’s the real power of bringing your own software.
It’s about the data and the processes that make an organization tick, not the silly tools that we use to keep track of our to-do-list and how we work with others. When the software we bring can interact securely & easily with the organization’s data and processes, then we’ll really be doing something interesting.