Posts Tagged ‘cost-benefit analysis’

Zynga is Hedging its Bet on Facebook

Sunday, May 9th, 2010

Recent reports are that the company that built its fortune putting games on the Facebook platform, Zynga, is moving to lay the groundwork to move away from its dependence on that platform.  Zynga is supposedly working to launch Zynga Live, a web-based platform that doesn’t require complete dependence on Facebook.

Word is that Facebook and Zynga are on the outs, as Facebook is trying to monetize its own platform.  As I wrote in a prior post, betting a business on the ability to access or leverage another company’s business carries risk.  Just how much risk is going to vary by the situation but the principals of any business that is dependent on another business must be cognizant of the risk factors, and should re-evaluate regularly.

If a company can execute crisply and take advantage of an opportunity built on another company’s platform, and is confident that the short term ROI is sufficient to go forward, then there is nothing wrong with building such a business.  The problem I see comes when the time frame for sufficient return on investment extends too far out into the future.  The longer a business is dependent on another’s, the higher the risk that a change in the relationship could bring the dependent business to an end before it gets the required return.

My take-away is that one must craft a solid plan that reflects an understanding of investment and expected returns, and that supports effective implementation.  Dithering will only decrease the likelihood of success.

Copyright 2010 Project Management Consulting

Betting Your Business on the Back of Another Company

Sunday, February 21st, 2010

The world is full of very successful businesses that have been built by tapping into a market created by a different business. What are the risks of building a business on the back of another company’s success?

Stepping outside technology for just a moment, consider that many baseball stadiums of lore were in urban neighborhoods. And many still are. Around those stadiums are bars, restaurants, parking lots, and other businesses that thrive largely because of the crowds (okay, some teams are too pathetic to draw large crowds but this is just an example) that attend 81 regular season home games. Now consider what happens when the team is moved to another city, or builds a new ballpark in another location. Ouch, there goes a micro-economy.

Now back to the tech sector. How many apps are being built to run on the iPhone? How many businesses are thriving because of Facebook? It seems to me there are few, if any, risk mitigation strategies open to companies totally reliant on either or both Facebook and the iPhone app store. (more…)

Don’t Be All Things To All Customers

Wednesday, April 15th, 2009

The shiny object distraction is only one form of dilution of focus that can undermine a company. Making the next sale, regardless of the cost of the sale is another risk. While I am focused on small companies, there is no doubt this form of dilution of focus can impact any size organization.

I worked for a small company, many years ago, that suffered the pain of such distraction. While the ultimate demise of the company was more likely the advent of a venture funded competitor with significantly more resources, the cost of chasing the next sale was a major problem. At the time, commercial, proprietary versions of Unix were numerous. A software product vendor with a Unix based product faced the prospect of developing, testing, and supporting a different version of the product for each version of Unix. Some Unix platforms were truly small fractions of the market.

For the company at which I worked, the prospect of the next sale, regardless of sale size, was the primary if not sole determinant. No consideration was given to the cost of the sale, including:
- Gaining access to a development and support environment for the specific flavor of Unix. In many cases, booking time with a local office of the Unix vendor and traveling to that office, was the only recourse to accessing such systems.
- The time needed to bring up that environment, understand the nuances as they would impact the product.
- The time needed to modify and test the modified product.
- The time needed to train customer support.
- The time needed to actually support the product including accessing the environment, reproducing problems, recoding, retesting, and redeploying the updated product.

In this particular company’s case, rarely did another sale on the Unix flavor of the month take place. The company was left with a highly fractured product line, and the limited development, test, and support resources were kept busy with the niche customizations instead of extending the product features and capabilities. Sadly, the company ceased to be able to make payroll.

The lesson I draw from this experience is that a sale is another form of shiny object. A sale should not only provide short term revenue but should, in aggregate, be of net benefit to the business. A new version, a variant on a product, a one-off instance … these are sales that may make sense but must be assessed not only from the benefit of short term revenues, but from the full life-cycle of the product. The costs include:
- creation of the variant.
- support of the variant.
- distraction of resources and impacts on other strategic initiatives.