software

...now browsing by tag

 
 

How Enterprise Software Companies are Getting “Blue Starred”

Saturday, July 24th, 2010

In the movie Wall Street Gordon Gekko attempt s to buy-out and liquidate Blue Star Airlines in order to extract $75M from their over-funded pension.   Gordon Gekko sings the turn-around tune to  union leaders yet his true intentions to liquidate become apparent to all and the showdown between Gordon and his naïve protégé Bud Fox (his father is a union leader at Blue Star) begins.  After having dinner with an old friend from the enterprise software world I realized a form of liquidation is now hitting the enterprise software business.  These companies are getting “Blue Starred.”   Buyout firms are extracting value from enterprise software leaving business users with systems that barely work.

First, lets begin with some context on the enterprise software business.  During the golden years (nineties) of enterprise software – companies like Siebel, Peoplesoft, ePhipany and many more brought software from the back-office (order processing and billing) into the hands of sales reps, customer service, marketing, and human resources (commonly referred to as the front-office).  The license based enterprise software revenue model works like this.  They sell $1M worth of software licenses and then charge companies annual maintenance fees (approximately 20% of the original license cost) for patches and incremental versions of the software.   So, a $1M license software deal actually translated into $2M over five years ($200K annual maintenance fees times five years plus the original license deal of $1M.)   Once a customer installs the software they are effectively locked in for many years.  These maintenance revenue streams are highly profitable as they not paying sales commissions and support costs are spread across thousands of customers.

With that context, it’s pretty clear what buyout firms are doing.  Acquire an enterprise software company with a significant customer base, cut new product development, move support to a low-cost labor market, and milk the maintenance revenue stream.

Yes, this is part of the natural product lifecycle – these are companies on their death-bed.   But the unfortunate part of this is that users (customer service agents, payroll admin, and hiring managers) are stuck with barely usable (try using Oracle Applications) and now largely unsupported tools.

Given the improvements in user experience (Apple) and collaboration tools (Facebook, LinkedIn, etc.) over the past five years these older software tools are a massive productivity drain for millions of users.  There needs to be a better and faster way to flush out mostly defunct enterprise systems and migrate users quickly to something usable.  There is hope, companies like Yammer cleverly bypasses traditional IT purchasers and first hooks the people that matter most — the users.

Four Ways to Clean Up Software Feature Bloat

Thursday, July 8th, 2010

software feature bloatNo matter how bad a product feature may be removing it is 3x harder than putting it in in the first place.  Here are four ways to remove unwanted product features.

  1. Bury It First: Reduces usage to the point where it will make it less painful to eliminate.  Netflix tried removing a feature and customers complained so loudly they brought it back and buried it — see here for full details
  2. Throttle It:  Limit the capabilities of the product.  Many years ago HotJobs had a job listing product that recruiters abused by refreshing the job daily to make it appear like the job was in fact new today boosting the relevancy of the job listing. Rather than completely eliminate this product we initially throttled the number of times the recruiter could perform the refresh action and made it transparent to the jobseeker that the job listing had only been refreshed.
  3. Take It On the Chin:  If a small percentage of users are holding you back from innovating on behalf of a much larger percentage of users, kill the feature, communicate it and move forward.  Some innovative sites like Digg fell prey to a very vocal set of users who demanded the product not evolve.
  4. Replace It With Something Else:  When Facebook App Notifications were eliminated, they provided other ways for App developers to connect with users.  Nowhere near the same level of distribution but some alternatives…I hear the moans from Facebook App Developers.

Adapted from my answer on Quora.  Follow me on Quora here.

Five Clues for Sniffing out Software Projects Bound for Failure

Thursday, May 13th, 2010

Spending eighteen months on a software project doomed to fail (either gets shut down or market irrelevance) is a waste of the important asset – your time. If you find yourself stuck on one of these you will pick up bad software development habits and find the innovation sucked out of you. Here are five clues to help you sniff out software project that should be avoided.

1.) Projects with Lots of Mass

My general rule of thumb is to avoid any project with significant amounts of mass in its early stages. By mass I mean lots of user research, lots of PowerPoint slides flying around, lots of executive attention, lots of developers. This chaos will generate even more chaos and usually failure. Some of the most successful projects at Yahoo! began as very small side projects: Yahoo! Answers and Yahoo! Sketch-a-Search. Find small projects with people (two three developers, a product manager, and designer) you respect with a track record of building good stuff.

2.) The Project with Three Names

If a project is not going well there is a trick to help it regain stature – rename it. It used to be called “Phoenix” now its “Marin” – problem solved! Before joining a project be sure to ask about the naming lineage.

3.) The Replacement Project

These are easy to detect. Somebody decides to follow a technical trend and in the name of flexibility, scalability, blah-blahbility decides to replace outdated an outdated technology platform with a new shiny platform (i.e the latest technology trend).

4.) The Project that Declares War

These are not hard to detect but hard to ignore, as their pitch inspires high emotional excitment. Declaring war on your archenemy naturally excites us humans. We like conflict. These projects are prone to failure because there is usually no clear angle of attack (see my post here). Rather, its lets build or sell a slightly better or cheaper version of the competitive offering. For example, if you are Monster.com trying to fend off Craigslist offering job listings for $50 is not going to do much other then erode your margins. The reason Monster is failing is because of poor applicant quality. Address that issue rather than chasing Craigslist.

5.) The Sacrificial Lamb Project

Projects that SVPs keep in their portfolio just in case somebody decides its time to start whacking some projects in the name of cost cutting. Because these are relatively rare they are also hard to detect.