Posted by Jim Haughwout on May 25, 2009 · Comments Off
In the Web 2.0 world, members of your community can upload media from any platform. This creates a literal nightmare managing CODECs across platforms. In this post, I discuss why YouTube is a greater technological achievement than Hulu–even though I enjoy Hulu much more…
Posted by Jim Haughwout on May 6, 2009 · Comments Off
I know this post is a little more promotional than my standard posts. However, the SIIA just validated (again) the business and technical design principles I often speak about at The Corner Office…
Posted by Jim Haughwout on February 15, 2009 · Comments Off
This week I had the pleasure of sharing information on my company’s approach to developing and delivering enterprise social networking services to three of Gartner’s experts on social media (Anthony Bradley, Nikos Drakos and Jeffery Mann). We had a chance to discuss in detail one of the main philosophies about technology I have followed since 1992…
Posted by Jim Haughwout on February 9, 2009 · 1 Comment
Many intermingle the terms “Application Service Provision (ASP)” and “Software-as-a-Service (SaaS).” However, these can be very different. It is important to confirm what your getting when you buy and ASP-based solution to ensure you avoid surprise costs…
Posted by Jim Haughwout on February 5, 2009 · 2 Comments
The launch of the enterprise application market was a great step forward for software. It significantly reduces the risk of using software to enhance enterprise operations and provided much-needed standardization that allowed CIOs and CTOs to acquire knowledgeable staff and adopt best practices. However, it takes a careful approach — and a lot of work — to achieve the desired internal rate of return (IRR) on these programs. Here are my thoughts based on experiences on $590 million dollars worth of off-the-shelf enterprise programs over the last decade…
Posted by Jim Haughwout on January 24, 2009 · 1 Comment
I could title this, “Confessions of a Serial In-house Build-over-buy Guy” as I was guilty of doing this many, many times. Regardless of how good your team is (I have been privileged to lead some of the best) and how unique your requirements are, it will ALWAYS be more expensive to build “it” in-house (vs. using a Software-as-a-Service model). To see why (and for my counter-arguement as to when it is wise to do this), keep reading…