Blogs

Are you ready for a psychology change?

When you make the decision to expose your data via API access to developers, you are going to have to be ready for a change in your thinking and psychology.

You have to realize that, for a lack of a better phrase, "developers want to mess with your stuff". They want to take your data and do things that you may never have thought of with it.

In order to make your relationship with these developers, you need to embrace a psychology of openness and accepting new ideas.

You also have to embrace a new audience...developers.

An effective API strategy encompasses knowing your customers (developers) and what they want to see and making yourself open to their feedback.

API Management Strategy--Real Life customer struggles

We just engaged with a large customer about their API usage, implementation, and strategy and there were some fascinating takeaways. This company saw the same issues that other smaller and medium sized businesses see with their API management.  It isn't the technological expertise or time needed to create their API content.

The issue is 2 fold:

1. "Once we have content out there, how do I explain to someone how we will monetize this?"

  • A monitization strategy is key to not only keep momentum going but acquire future resources in your company to develop future API's and innovate the ones you have now.
    • The key is to establish clear metrics on what your API will deliver and what it will not and measure against that. Are you measuring audience, # of developers, API traffic, community traffic, etc?
  • Also, you need to be able to fully communicate what your plan is for maintaining a successsful API community and tap into your external developers using your API's.
    • The best innovation for your overall product can come from a larger network of developers taking your data and using it in ways you never thought of. You are essentially receiving free innovation.

2. "How do we manage handling our API strategy moving forward?"

Watching Clouds

Monitoring cloud performance is different from on premise application servers. For starters, you can’t put a SNMP agent up there; can’t monitor WMI classes either. Shoot, you may not even have an IP address. So how would you monitor cloud applications? Here are three ways:

Understand your customers’ needs before you understand their wallets

In an article entitled,  Software for Business: When Not to Buy,  Businessweek lays out a common scenario from the point of view of a software seller being completely honest. This salesperson has sold a CRM system to a small company without accessing this company’s actual needs.

The future of SaaS may be VAR's

Recently I read a blog post of Chet Kapoor titled The future of the indirect channel in a Cloud enabled world. In the article, the new role of VAR's is positioned as Systems Integrator (SI). Why? Because the indirect channel knows your environment. We see past the marketing messages of Cloud proponents and look at your specific business needs. One of the key needs is that clouds somehow talk to one another.

Syndicate content