Oct 24 2009

Views and Experiences: Growth by Innovation or M&A?

Category: Leadership,Strategic Management,StrategySurendra Reddy @ 8:58 am   Comments (0)

John Furrier kicked-off an interesting conversational thread on twitter: Grow through innovation or M&A interesting discussion going on here; re: Cisco vs Juniper – two different visions on growth. Jake Kaldenbaugh, Susie Wee joined me in the discussion. I have summarized my thinking and position on M&A vs Innovation driven growth strategy. My argument is that success in Innovation and M&A driven strategies combined with optimal use of financial engineering is the best guarantee of thriving in good times and bad times. Companies decided to choose only innovation or M&A or financial engineering tend to destroy its value as opposed to creating value. Welcome your comments and wisdom to shape my thinking and practice.

Growth

Growth is a worthy goal. Not very long ago, earnings just more than the cost of the capital was the mantra to measure the growth of the companies. Many companies worked hard to make their assets sweat. But, changing times and changing market conditions drove investor’s thirst for ever higher returns. Then came the next generation technology companies and changed the market expectations. Now, same investors no longer happy with earnings at cost of capital. They are demanding unattainable growth targets. It is practically impossible to meet the rising expectations of shareholders unless companies innovate to create the wealth – that too in a way competition can’t follow you quickly. You can’t buy the innovation “off-the-shelf” through M&As.

In the continuing quest for business growth, many companies are turning to  three compelling sources of growth: Financial Engineering, Innovation and Integration (M&A). Growth through applying financial engineering practices by getting rid of bad companies, “toxic assets”, share buy backs, returning cash to shareholders, and downsizing only lasts for short term and are used for instant cure for slow growth syndrome. Where Innovation is not only about developing new generations of products, services, channels, and customer experience but also conceiving new business processes and models. M&A or Integration enables them increase capacity, improve performance, lower cost structure, and discover new business opportunities.

Susie Wee (@susiewee) wrote,

Organic growth reqs commitment to productization/M&A reqs commitment 2 integration. Each has a place & needs to be “done well”

Growth is no substitute for radical innovation. But “durable growth” is a derivative of radical innovation. Focusing on growth rather than on the challenge of innovation is more likely to destroy wealth. Don’t mistake financial engineering for radical innovation. At the end there will not be any more wealth to unlock. You don’t need leaders to unlock the wealth – instead you need leaders who has fire-in-the-belly to create lightening rods of radical innovation. Innovation and integration, together, allow an enterprise to acquire more customers and deliver more goods and services to market. My argument is that success in all three is the best guarantee of thriving in good times and bad times. If companies choose to go with either one of these strategies and stagnation can doom a business. Successful execution of either of these strategies is not an easy task. It needs discipline and senior management commitment. It strongly depends on companies’ ability to collaborate across organizational boundaries.

Companies that can grow their top-line by giving away value at close to zero profit are spinning their wheels without much of progress. How long they can survive?

Innovation Driven Strategy

Unless companies institutionalize the innovation activism, they are unlikely to meet the challenges: Reinvent itself and re-inventing its industry. Apple is such a great example of an innovation driven company. How many acquisitions Apple made recently? I guess close to none. Is apple creating wealth or unlocking wealth? Apple created huge wealth through radical innovation. My assessment is that Apple was able to re-imagine its deepest sense of what Apple is, what it does, and how it competes. That made them very unique company in the Valley. Customers love their products. They don’t even mind piercing their bodies with tattoos of Apple’s logo. What is driving such a stellar performance of Apple? I bet it is constant, restless, and relentless innovation with new products their customers love without damaging their price position and the brand.

Susie Wee (@susiewee) wrote,

@Furrier @Jakewk @sureddy Driving innovation to product in a company is an art. Requires strategy, opportunity, timing, and luck.

@sureddy Actually I prefer the word “fortune” over “luck”. You can have some impact on your fortune.How important?Very… @Furrier @Jakewk

@sureddy Moving innov to market in BigCo requires many functions-mktg,r&d,GTM,supply chain,ops-to execute in concert. @Furrier @Jakewk

@sureddy Fortune/Luck is when the innovation matches needs/strategic directions in multiple functions at the same time. @Furrier @Jakewk

Many companies fail to create the future not because they fail to predict it but because they fail to imagine it. Companies stuck more often with their heritage and failed to distinguish between the heritage and destiny. As Jake Kaldenbaugh pointed out, in many companies the premium placed on being right is so high that there is virtually no room for imagination or looking for the unconventional wisdom. These days strategies of many companies looks alike or hardly any difference. Outsourcing was another powerful force for the strategy convergence. As companies outsourced more and more made their strategic differentiation narrower and narrower. They are focused for short term and compromising their long term vision.

Jake Kaldenbaugh tweeted his interesting view on Innovation Strategy:

@sureddy @susiewee @furrier Organic is still a funky art in cos. Have hard time doing both product & GTM development.

@sureddy @furrier Successful internal R&D growth strats tend to run in cycles for cos which tells me they may be based on leader ie S. Jobs

@sureddy @furrier @susiewee I think corp incentive systems interfere w/ internal innovation. Y so much reliance on VC & M&A in SV.

Without a radical innovation, companies are devoting a mountain of resources to molehill of differentiation. Unless companies become more adept at innovation, more imaginative minds will capture tomorrow’s wealth. We see this all the time. Companies started in garages tend to break the records of all time. What is driving these small companies to achieve such an outstanding performance or results? Their ability to de-construct and re-construct their business models at the speed of light. When its most effective, radical innovation makes their competition irrelevant. It isn’t about competitive strategy. It is not positioning against competition. But making competition irrelevant. If it is not different, it is not strategic any more.

Cisco and M&A Driven Strategy

Companies like Cisco realized that much of the innovation that will shape the future of their industry is occurring outside of their organization. Cisco viewed hundreds of startups that created every year as potential sources of innovation to be exploited. They adopted totally different strategy. They co-opted the insurgents. They are innovators in one sense realizing that the ultimate value of their acquisitions is not the integration of technology or products but unlocking the huge wealth in the contribution it makes to Cisco’s entrepreneurial energy. In my view, Cisco enabled different level of Innovation through a perfect blend of serendipity, genius, invest commitment, and sheer execution focus. I tend argue that Cisco legitimized, fostered, celebrated, and rewarded the nonlinear innovation. I may be wrong. But, my strong sense is that they created an ecosystem where virtuous mice(startups with great ideas) and wealthy elephant(Cisco with ton of money and passion to harvest these startup ideas) lived happily ever after!

@Jakewk Cisco’s competitive strategy is at odd with engineering and product strategy has been for years – they fill holes not advance tec

Cisco has worked to make acquisitions a routine process, as route as the product development. Kind of open their eyes and ears to look for new innovations part of their strategy. This strategy worked well for Cisco for reasonable amount of time.

Jake Kaldenbaugh replied to Cisco’s M&A vs Innovation strategy:

@Furrier Re: Cisco filling holes v. adv tech: Sometimes systemic integration can be innovation IMHO.

Does this strategy work for long run? Is it sustainable? In my view, I think they also reached the point of inflection. For every strategy there is a decay unless it is constantly refined and reinforced. And I am sure Cisco started to experience this too. It is rather very difficult to scale this strategy for ever. The complexity of trying to manage these different business units soon will overwhelm the advantage of integration. Though M&A helps eliminating the competition vs making their competition irrelevant. Companies that focus on this strategy, soon end up with an unsustainable or strategy decay. What do they do next? Then they go and spin-off or de-mergers or break them into small companies. Or get rid of the bad apples. All these would lead to the circus of financial engineering to unlock the shareholder wealth. Never forget that good companies gone bad are simply companies that for too long denied the strategy decay or trying to over reach their growth without any strategic differentiation.

Conclusion

Don’t mistake financial engineering for radical innovation. At the end there will not be any more wealth to unlock. Companies need radical innovation to create more wealth. Successful innovation needs discipline of innovation, senior management commitment, and depends on companies’ ability to collaborate across organizational boundaries. Innovation and integration, together, allow an enterprise to acquire more customers and deliver more goods and services to market more rapidly making competition irrelevant. My argument is that success in both combined with optimal use of financial engineering is the best guarantee of thriving in good times and bad times. Companies decided to choose only innovation or M&A or financial engineering tend to destroy its value as opposed to creating value.

TAGS: , ,


Oct 12 2009

Cloud: Interoperability & Portability

Category: Cloud ComputingSurendra Reddy @ 12:34 am   Comments (1)

The discussion about the difference between interoperability and portability isn’t new by any means. In the context of Cloud, Portability is the ability to move an application or service from one cloud to another cloud, usually with minimal overhead, or no overhead. Interoperability is the ability of services to seamlessly communicate with each other.

If Mime is a portable format for exchanging the mail attachments in consistent and decipherable format, then the SMTP is an interoperable communication mechanism to transport these messages from one place to the other. Similarly, SNMP is the transport and MIBs are the message codification scheme for portable understanding of these messages. That’s good. We solved this problem number of times. We learned lot from these evolutions. So, combining all these rich experiences and wisdom, I am sure we all can come up with simple but powerful mechanisms for enabling the another level of technological disruptions and innovations.

Christofer Hoff wrote on his incomplete thought on “Cloud Portability or Interoperability?”:

There is a lot effort being spent now on attempts to craft standards and definitions in order to provide interfaces which allow discrete cloud elements and providers to interoperate. Should we not first focus our efforts on ensuring portability between clouds of our atomic instances (however you wish to define them) and the metastructure that enables them

Cloud services are composed from connecting one or more services and combinations of message patterns that takes places between or among these services. This implies that Interoperability (dealing with how to communicate among these services) and Portability (how to move these services and associated data sets from one cloud service provider to the other) are more critical than ever before for Cloud.
Lori MacVittie argued that:

I don’t think there is a difference between portability and interoperability. If you have one, you have the other. We can certainly move forward on an attempt to define a standard that allows portability across environments of atomic components as long as we do so in a way that bears in mind we’ll need to extend it to support metastructure in the future.

Allen Baranov has a different point of view:

In other words… they(portability and interoperability) need to come at the same time.

I do agree with @Allen that the Portability and Interoperability are two inseparable and conjugate concepts that need to go hand in hand. Though how that can be done is different issue. But, both of them are necessary and required conditions to give the customers required confidence that they can move their services and data freely. I am sure @Lori is also meant that Interoperability and Portability are not two separate things and they need to go together. Good news is that as network speeds approach computer bus speeds, the network becomes the computer, Portability starts embracing Interoperability issues and Interoperability can start gleaning the benefits of Portability. So, the distinction or difference between these two started to blur and portability meets interoperability.
Dan Philpott has expressed his interesting view and concern on innovation and standardization:

Building in a requirement for portability at the outset would tend to retard development of new technologies. If a technology is portable it becomes a commodity. Commodities mean you have no market incentive to beat the competition on anything but price as all products are otherwise equal. Companies who innovate want to lock in a larger market share by producing something unique and market differentiated. So building in portability means that they would not be rewarded for the innovation.

Yes, Agreed. But, that is true for specialization. I am not sure if APIs or protocols are their sustainable competitive advantage. The interoperability that results from using standards makes it easier for consumers to mix and match products and it increases competition. In case of Cloud, standards clearly needed because we’re talking about some kind of platform on which other applications and services are going to be built. In my view, the biggest economic contribution will in fact come from the platform or the applications on top of this standardized platform. If you are building a specialized service on top of this platform, then competition make sense. Though the competition is definitely a key component in driving innovation, but it’s important to question where that competition should be occurring, and where it’s mutually beneficial to have a standard. Internet shouldn’t have been successful without TCP/IP or portable data formats. XML, MIME, EDI are all standards but innovation thrived around these standards. So, i strongly argue that vendors/cloud service providers need to be more innovative than locking up access protocols or methods.

Finally, we need to make sure we clearly define what we mean by interoperability and portability and try not to gloss over the differences. Interoperability is extremely important as far as Cloud services are concerned.

Then Rich Miller asked three challenging questions to help complete Hoff’s incomplete thought:

  • Within the context of infrastructure as a service, what does an interoperability means? Does it mean anything other than I can package up a workload on one of the IaaS environment and reinstate it on the other side? Doesn’t that sound like portability?
  • Within the context of PaaS, what does interoperability means? Does it mean that I can do a database “merge” operation between collections residing on the two services without an export and import? Have we just reinvented federated database operation? Or does it mean successful export-import aka data portability?
  • In Cloud environment, what’s the difference between interoperability and portability exactly? What cloud go to do with it?

@Rich, you answered your own questions. Interoperability and Portability are not a new topics for any of us. We have dealt with these issues for ORBs, SQL, EDI etc. Posix has been around for awhile giving us mechanism to provide interoperable and portable access to systems all along. In my view, we all need to seriously start thinking about collaboration and standardization to address these portability and interoperability issues. I don’t think, protecting APIs or access methods gives any one vendor a sustainable competitive advantage. Any comments?

What do we need to standardize?

It would be very difficult to fully anticipate the needs of the Cloud service consumers. There is a growing need to distribute the application/service globally to be able to meet the demands of growing business needs. When services are distributed or deployed across clouds, latencies and performance guarantees of each other is critical. Ability to switch over to the other service providers who can fulfill these goal is also equally important. User applications or services should be able to balance their requirements like cost, geography, throughput and other efficiencies. As Cloud is all about dynamicity, it is essential to provide a common interface to negotiate, allocate or de-allocate any additional cloud services or resources completely driven by the business needs. All these lead to having a common interfaces or standards to facilitate addressing some of these challenges:

Some of the key standards required for the futuristic cloud services (metastructure) are:

  • Cloud Resources:Cloud service provider independent mechanism to access metastructure (including the common semantics for cloud resources like Nodes, Load Balancers, Switches, Routers, Firewalls, Network ACLS, Data Access(both structured and unstructured etc)
  • Cloud Services Directory:Cloud service directory services for service configuration, identification, location, and routes etc. Same interfaces or services should be accessible from other cloud service providers too.
  • Audit, Assurance, and Compliance Data:Given the growing policy and compliance needs, Cloud service consumers needs some common mechanisms to extract this information from the underlying cloud resources or services.
  • Accounting and Metering: Cost of resources is a very important factor for any application. Of Course, primary goal of every business is to create value for their shareholders. Traditionally, IT departments have been operating with huge capital expenditure budgets (depreciation curse) or operating leases (off-balance sheet magic). Cloud introduces pay-as-you-go model making it very difficult to predict the cost of these services during the budgeting process. IT leaders need to figure out how these services are budgeted. However, what is very critical in that direction is having an uniform interface and/or semantics for metering and monitoring resources consumed in the Cloud. In addition, these mechanisms also help them to put some governance and financial controls.
  • Resource Life Cycle Management: Cloud moves the resource ownership to centralized service providers. As consumers started to use Cloud resources, they need better control on negotiating, acquiring, pricing and activation of these resources. So, it is very important to define common mechanism and interfaces to address these needs in the cloud with some common interfaces to negotiate, execute and monitor these contracts or commitments.
  • Cloud Security Services: Security is becoming increasingly important concern in the cloud. It is not that current applications addressed this problem very well and cloud is not thinking about. Enterprise applications are hosted inside the bricked walls to protect themselves. That gives the users the confidence and assurance required. The moment they move these applications into the cloud, onus will be on the applications themselves protect from any security breaches. Applications need to sense and respond to any threats. It starts with defining the common interface to provide the security protocols required. Again, how this mechanism implemented are left to the Cloud infrastructure providers to innovate and come up with new technologies and innovations. Some cases, we should be able to leverage all TLS, HTTP/S, IPSEC and other technologies innovations already in place. At the minimum, it is important to think of how cloud applications and security aspects needs to be provisioned, monitored, and controlled. So, this leads to my requirement for defining protocol or common mechanisms for provisioning security identities in the cloud.
  • Cloud Performance Data: Performance monitoring and tuning is going to be another Interesting challenge that InterCloud need to address to provide an ability to predict an application’s performance across different clouds. Unless the Clouds can provide some signals of performance(like what we have today for OSs), it would be hard for service brokers to negotiate these contracts dynamically. To facilitate the service bursting into Cloud having a well defined interfaces to the Cloud resource is very essential. Though initial phases of cloud adoption, application can take care of these initially(that may open some more new challenges though) but we should start thinking at higher level i.e. Cloud infrastructure level.

TAGS: , ,


Oct 10 2009

Cloud – Enabling Rich User Experiences

Category: Cloud ComputingSurendra Reddy @ 3:00 am   Comments (0)

Most successful brands create breakthrough ideas or innovations that are inspired by a deep understanding of consumers’ lives. Customers are no longer tolerating the rushed and mediocre service offerings. Instead, they are demanding satisfying and rich experiences. Companies that provide it will evoke emotional bonding with the brand and win their loyalty.

It’s fashionable today to talk of becoming “customer oriented.” Customer centricity is not just a slogan. It’s a pre-requisite for substantial profitable growth. Customer driven innovation isn’t just a strategy. It is a rigorous process and helps companies to understand who their customers are and what they care about. Customer centric thinking focuses on developing better ways of communicating value propositions and delivering complete, satisfying experiences to customers. It takes more than good intentions or grand visions to innovate in a customer-centric way. With the emergence of information rich societies and wide range of options for interactivity, customers are demanding more than ever before. It is going to be more challenging to keep your customers engaged with your brand unless you put them into your innovation process.

Padmasree Warrior, Cisco CTO, wrote on her blog:

Much of the discussion regarding apps today focuses on the debate between pure cloud (SaaS) delivery vs. the traditional on-premise approach to apps. Our view is that we need to move beyond this conversation and focus on the user experience. Here’s what we mean by that: As users we all want an experience that’s consistent and seamless, with the ability to stay connected and have instant access to the services and functionality we need, regardless of our location or what device we happen to be using. To deliver that seamless experience we’re going to need a combination of different types of applications—some that are on-premise and others that are on-demand.

Yes, we have been spending too much time debating on SaaS vs on-premise hosting of our applications. Instead, our focus should have been on creating rich and memorable user experiences. A disciplined process of Customer innovation will turn customer wishes into an enduring competitive edge – and a growing marketing cap. How do we enable this? How flexible and agile our systems and processes are to drive this level of interactivity with our customers. Limitations and rigidity in our systems and services are being pushed onto customers as “best practices” and cost of customization of these “rigid” systems far exceeds the value it offers. So, we need a radical shift in our thinking. We need to bring customer into the innovation process. This is only possible by shifting our conversation from systems view to customer view.

However, to fulfill this ambitious goal, we need agile, stable, and scalable service delivery platform. In spite of the all trends and developments in the technology, like SOA and Web 2.0 serving, we are still mired with IT infrastructure complexities and deeply fire-walled applications. So, the next frontier of innovation will require the customer focused, lean and optimized, utility based, and demand driven (CLOUD) computing infrastructure.

Though some argue that Cloud is the new business model or outsourced IT model, my view is that it is both an architectural paradigm shift and an economic model enabling optimal pricing and rapid innovation of new services without a huge capital outlays. Cloud is an architectural paradigm shift because we need to think differently the way we build, deploy and manage services in the Cloud. With the Cloud, we can focus on innovating to fulfill this new user centric view instead of spending all our time and resources to keep the lights on. Current applications were designed with different assumptions. Designers and developers glued their applications tightly to an operating environment and network. Hard-wired whole bunch of localized configurations into their applications. They fused-in specialized ACLs into network switches. Built rings of firewalls and VLANs of hell around their applications. May holes were punched and many controls were enforced around these applications. Moving these applications into Cloud is a huge undertaking.

Last 3 years, I have studied number of applications including massively complex Supply Chain Management processes to stateless web serving applications. Moving them into Cloud involves either complete re-write or re-engineering of data extractions, transformation, and loading in addition to re-wiring their business processes. Many of these applications assumed local optimizations, caching, connection pooling. It is even shockingly surprising that many application secrets were buried and firewalled on those servers. Moving them off the localized fire-walled environments to Cloud needs architectural re-thinking.

Though many enterprises are curious to move to the Cloud, my view is that they are not ready to embrace Cloud unless they look at their architecture and infrastructure more holistically. Virtualization is necessary but not sufficient. Extreme automation is the key. Today 76% of the production outages are caused by errors in configuration or change management. So, Continuation Integration combined with an automated deployment should be integrated into the services. Cloud is a promise. Service is the fulfillment. End-to-End Service is what it matters to consumers/customers.

With that said, majority of Cloud (Public Cloud) adoptions will be driven by emerging companies, services, and consumer facing web companies. Meanwhile, enterprises will start to adopt the private cloud model for their enterprise applications. That will give them fairly good opportunity to look at their applications, networking, security, and integration infrastructure more holistically. Once these applications are rewired into services with infrastructure 2.0 thinking, then they can burst their capacity needs into the public clouds. I see this as a multi-year journey.

TAGS: , ,