Skip to main content

Sign in to participate


The postings on this site solely reflect the personal views of each author and do not necessarily represent the views,positions,strategies or opinions of IBM or IBM management. IBM reserves the right to remove content deemed inappropriate.

Sort by:

    Most recent     Most recommendations     Most comments     Most visits

Edit Quarantine this Entry


1 Michel Caussanel commented   Permalink No RatingsRatings 0

Just to tell you that the link "" doesn't work.

2 Benjamin Chodroff commented   Permalink No RatingsRatings 0

Great work on Service Engage and congratulations as well on the baby :)

3 Kristof Kloeckner commented   Permalink No RatingsRatings 0

Great story!

4 Andrew Freed commented   Permalink No RatingsRatings 0

Thanks for sharing this story!

5 Kartik Kanakasabesan commented   Permalink No RatingsRatings 0

Great Post Bill, but your article captures just one element of a startup which is the development experience. Working in a startup is like being a trapeze artist but without a safety net. The cost of failure in startups is a lot higher than it is in a big company and the risk exposure is significantly higher (the benefits of being in a big company is that risk exposure is limited). Being in a Startup, company you are just hungry more because one bad quarter could mean the end of the company no matter how great the development experience is and I am sure that is not the case in the projects you have been part of (Thankfully)

6 Bill Higgins commented   Permalink No RatingsRatings 0

Kartik: Great point.
I actually wish it *could* be more life or death, but in a different sense. I like what I've read about the Apple approach where they'll start up a project and then quickly kill it if it doesn't have legs. E.g. they started an iPhone based on the iPod Classic and then killed it after 6 months when it was clear that the iPod Classic was too limiting as a platform. So it's not "going out of business" but it would certainly be "justify your startup project's survival".

7 Kartik Kanakasabesan commented   Permalink No RatingsRatings 0

The iPod example is great and the reason for killing it as well and yes the platform was limited. The reason for this being is that Apple had the resources to do and go ahead kill the project and start over again. In most cases some start ups do not have the diverse portfolio of products to go ahead and kill an effort. In the case of a lean startup you are trying to get feedback on early revision and capture how clients behave with the product. The reason why things like Analytics have taken hold is because startups do not generally have human resource to monitor the user behavior and decided to leverage the web and other means to capture behavior to help improve the feedback cycle into business design (not just development, but design of the overall business).
Going back to you iPod, Apple realized early enough that they would need a new platform and a new business model around the iPhone instead of persisting with iPhone business model which was more geared around consumption of content versus with the iPhone you can now great and commercialize your creation on the Apple platform. Like I said this is a good post if looked at strictly from a development perspective

8 li wei commented   Permalink No RatingsRatings 0

Great experiences that be implemented by any teams in IBM, especially during this transformation age.

Add a Comment Add a Comment


A tag is a keyword you assign to make a blog or blog content easier to find. Click a tag to find content that has been assigned that keyword. Click another tag to refine the search further. Click Find a tag to search for a tag that is not displayed in the collection.