sábado, 9 de junio de 2012

What every executive needs to know about API technology

Posted 08 June 2012 18:15pm by David Chiu with 0 comments

Yes, it seems like a very technical subject best left in the hands of your IT department.

But just as the web and mobile jumped quickly from sideshow to center stage in sales and marketing, how good your APIs are will ultimately have a significant impact on your bottom line – and potentially, the future of your business.

Here's what you need to know about them.

What exactly am I trying to solve?

By now, you're probably well aware of the market forces and trends leading every industry into an era of disruptive digital selling. Emerging products and services are exerting tremendous pressure on companies to innovate, differentiate, and extend the reach of their offerings – whether functionally, demographically, or geographically. At the same time, aggressive competition is driving down margins, while rapidly changing consumer attitudes, preferences and behaviors create a moving target for marketers and product strategists.

To succeed in this environment, any digital selling that your enterprise undertakes must obviously be frictionless, relevant, and pervasive to consumers. But on your end, it must also be fast, scalable, and cheap. Cheap to try, cheap to deploy, and cheap to shut down if specific projects fail (and they will).

This is where API technology excels.

How do APIs solve these challenges?

In theory, a good set of APIs transforms your big, old-fashioned ecommerce platform into a sleek engine that delivers commerce-as-a-service. This means that all of the advanced capabilities you've come to rely on – promotions, personalization, offer management, shopping carts, and so on – are no longer locked away within a single platform, but instead are available for use by any application or developer.

In this perfect world, if you can imagine or build a customer experience, you can quickly loop it into your existing ecommerce, business intelligence, and CRM systems by calling on APIs instead of hacking away at the underlying software.

A great API allows you adapt quickly and cheaply to a shifting market, but in a scalable and sustainable way, rather than constantly making difficult and expensive changes to enterprise software. This magical ecosystem looks something like this:

The promise of APIs

Aren't my IT guys taking care of it?

Unfortunately, this is where the promise of APIs crashes headlong into their present reality.

If you put yourself in the shoes of most enterprise IT or commerce platform technologists, their number one priority is not to build out this magical ecosystem for your business, but simply to ensure that the underlying functionality they own is exposed for use by third parties. This may be a subtle distinction, but it's the difference between a good API that gets the job done, and a great one that works like a superpower.

Many existing APIs do a terrible job at making it easy for other applications to actually access business functions. Some are good. Almost none are great. When left in the hands of IT, the typical API ecosystem ends up looking something like this:

The reality of APIs

 

It's a bottom-up view of APIs from the perspective of the code, rather than a top-down one where the potential applications are king. Where underlying functionality is merely exposed, creating a viable customer experience out of those functional pieces requires serious time, money, skill, and deep, in-depth knowledge of the software that hosts those capabilities.

This defeats the purpose of having an API in the first place, and does little to alleviate the time, effort, or cost needed to conduct disruptive commerce.

Compare the promise with the reality. The only difference between the two is in the quality of the commerce API, and how easily independent developers can create products and services from your core capabilities. This is how API technology can either make or break your entire business strategy.   

How can I make this happen?

Independent API evangelist Kin Lane has seen first-hand how API programs at major companies have resulted in both spectacular successes and failures. He stresses that the creation of an API strategy must be a coordinated effort between business stakeholders and technologists, because API technology decisions have moved beyond the IT sphere to affect the very ability of an enterprise to respond effectively to the market. If you'd like to learn more about this, check out my recent conversation with him in Business Challenges Solved by APIs.

Just like with ecommerce and mobile that came before, business executives can no longer consider APIs to be a sideshow best left to IT. They must get involved in understanding, making decisions, and ultimately owning what will be the next big chapter in digital commerce and marketing. 

David Chiu is the digital commerce strategist at Elastic Path and a guest blogger for Econsultancy.

No hay comentarios:

Publicar un comentario