Posted on 01-10-2014
The latest tech news to come out of IBM this week is a brand new business group to push innovation around the IBM Watson platform, with IBM committed to spending $1B on the new business group, with $100M set aside to fund startups who build on top of the Watson platform.
The introduction of the new business group may be in response to the media’s, and analyst’s chatter about less than impressive results so far with the Watson platform’s ability to generate revenue, with $100M revenue over the last three years, according to the Wall Street Journal.
There was a post on on ReadWrite today, called IBM's Watson Fails To Compute In A World Of Open-Source Hadoop, where Matt Assay nails the reason: Where Are The Watson Developers?
When you visit the "IBM Watson Ecosystem Program”, you get a lot of text, and then even more text contained in PDF’s telling how much you can innovate with the platform. Then when you are ready there is a pretty lengthy form to fill out, where you can tell them what you want to do with Watson, and hit submit and hope they will let you in. They also have a Twitter, Facebook and Youtube account, but really it doesn't smell of “ecosystem” where “innovation” is happening. I've looked at over 10K “ecosystems”, which about less than 500 are truly “innovating”, and after a while you start to be able to smell the signs of success.
I’m not saying the IBM Watson platform doesn’t offer value, I’m just saying the team doesn't know how to make "innovation" happen. They need to loosen up, stop being so enterprise, and open up a little bit. We know you got some APIs behind there, make them accessible to ANYONE, make registration self-service, and give us some dead simple, meaningful, powerful web API endpoints to play with that will stimulate our imaginations.
There are proven ways to limit the access new developers so they don’t get out of hand, and models for developing incentive ladders that incentivize developers to not just play, but actual develop solid apps that can deliver and will actually evolve into real world business models.
Analytics and feedback loops can be put in place that allow you to easily control the moochers and bad actors, while stimulating and listening to the true innovators, allowing the Watson team to iterate and evolve API endpoints that don’t just cater to one industry, but any business sector.
You can’t just develop an powerful resource like Watson, make it available in the cloud, label the platform an“ecosystem”, provide some case studies and innovation magically happens. You have to let go a little, and allow developers to come on board, play, imagine, fail, and push the boundaries of what is possible. This doesn’t happen when you have total control over everything that happens.
Bringing a true developer ecosystem to life around Watson will be more than just about the technology, you need to put in place the essential building blocks developers need to be successful, let a little oxygen into the mix, then I think you will find the innovation and ultimately the revenue you are looking for from Watson.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems
- APIs That Do One Thing And Do It Well Like ZipLocate
- Which API Do I Need?
- The Expanding API Conference Landscape
- Ocotoparts Open Source Google Spreadsheet