Welcome!

Microservices Expo Authors: John Katrick, Elizabeth White, Liz McMillan, Derek Weeks, Pat Romanski

Related Topics: Agile Computing, Mobile IoT, Microservices Expo, CRM

Agile Computing: Article

Applying the Marketing Center of Excellence (MCOE)

A case for the MCOE: The HP TouchPad "Fail"

The HP TouchPad was launched July 1, 2011, and was discontinued August 18, 2011. The Marketing Center of Excellence (MCOE) may provide a framework for understanding (and preventing) the sorts of “black swan” marketing failure that HP experienced with its TouchPad launch. I think the key value provided by a MCOE for reducing the risk of a “black swan fail” is its enablement of a holistic, cross-disciplinary approach to marketing at enterprise level.

Leslie Ament, SVP at Hypatia Research Group, asked a great question that points towards the complexity underlying the situation, and the potential value of a MCOE: “Is this a failure of 1) product features, 2) timing of launch, 3) targeting of market segment and/or 4) demand generation, branding, and execution of campaigns?” In the framework of a MCOE, the operator here would be an “and,” rather than an “or.”

Hypothesis: Events and Issues
These events may have lead to HP’s decision to discontinue the TouchPad:

A number of poor reviews. 
Per Sean Portnoy at ZDNet, “The bottom line was the TouchPad was released with several crucial flaws that led to mediocre reviews…" Mediocre would be an understatement; here’s a small sample:

Walt Mossberg wrote, “[The HP TouchPad] suffers from poor battery life, a paucity of apps and other deficits.”

Said David Pogue, “In this 1.0 incarnation, the TouchPad doesn’t come close to being as complete or mature as the iPad or the best Android tablets; you’d be shortchanging yourself by buying one right now…”

Matt Buchanan on Gizmodo opens his review, “I am so goddamned tired of the iPad. Which is why I was so excited for the TouchPad. And that's why I feel so completely crushed right now.”

And from Eliane Fiolet on Ubergizmo: “Overall, the results speak for themselves: the touchpad is the slowest tablet that we have tried in 2011. … The HP TouchPad did not stand up to expectations, so much that it died before getting a chance to be improved.”

Underwhelming consumer demand at launch compared to projections. 
The poor reviews may have contributed to the serious gap between potential customer interest and inventory forecasting. Best Buy sold “less than 10 percent of the units in inventory” according to the “OuchPad” article in All Things D. Other retailers reported similar issues with inventory, per International Business Times.

Reading through an aggregated analysis of the HP TouchPad fail on The Week, some high-level themes emerge:
Poor price-to-performance compared to a market leader. The most serious concerns noted in reviews were slow performance; at a $599 launch list price, people just didn’t choose the TouchPad over the iPad unless they were “A.B.A.” (However, when HP dropped the price to $99 to clear out inventory, retailers sold out.)

Channel issues. As reported by Matt Rosoff in Business Insider SAI, "Best Buy doesn't want all that unsold inventory taking up shelf space, and is asking HP to take them back. Todd Bradley or another HP exec is reportedly going to fly to Minneapolis to try and persuade Best Buy otherwise." While no other channel issues surfaced in my research, Best Buy can’t have been the only retailer pushing back.

Launch issues. HP had a daunting task—to cut through WebOS being lumped into Android “me-too-ness” while grabbing market share from Apple’s iPad. Rather than launch later, which would have put its new product in the run-up to the 2011 holiday shopping season, HP chose to launch on the July 4 weekend.

Despite the July 4th timing, Google Trends shows an incredibly steep climb in search volume for “HP TouchPad”; there was a lot of buzz and interest. Unfortunately, the climb quickly dropped off into a cliff that seems to represent an abrupt collapse in interest and demand.

Using the MCOE evolutionary model to respond to Leslie Ament’s question, what Marketing Communities of Practice would have been involved?
The issues noted by reviewers related to performance would be R&D and Product Management’s domain. The price-to-performance issues would be Product Marketing (possibly compounded by issues on margins and the cost of Bill of Materials involving Product Management). Channel issues would rest with Product Marketing. If there were problems caused by the timing of the launch or pre-sales Demand Generation/AR/PR, they are not reflected in the spike of interest shown by Google Trends. (It’s hard to say what the actual comparative search volumes were in Google - at this moment, “HP TouchPad” shows about 75-100 searches per day, and “Apple iPad” shows roughly 900 per day.)

If we make the assumption (and I know it’s a whopper) that a company like HP would at least be at Levels 2 to 3 on the MCOE Maturity Model across the horizontal domains of People, Processes, Technology, and Data, how could a failure of this magnitude occur?

Using the MCOE framework may help clarify where things broke down:

People. Even if each disciplinary area was focused on “best practices,” were there shared goals to drive and support cross-disciplinary work by the Communities of Practice? Were there breakdowns in communication like this one, but among disciplinary areas? How was conflict (for example, possible conflict between the Hardware team and the WebOS team) managed?

Processes. How were risks (for example, press/reviews) identified and weighted among and by the Communities of Practice? Was some form of cost/benefit analysis applied to risk, so executive management could be advised?

Technology. What inventory and sales forecasting systems were used, how accessible were they to the Communities of Practice, and could they provision for fast (near real-time) corrections?

Data. Were there issues with the data used in planning/reporting that affected accuracy?

In my opinion, the biggest risk to an organization from enterprise-scale marketing comes from silos that inhibit business agility and useful communication.The key value provided by a MCOE - not just for reducing the risk of a “black swan fail,” but also for enabling innovation, effectiveness, and efficiency—is its enablement of a holistic, cross-disciplinary approach to marketing in the enterprise.

More Stories By Lori Witzel

Lori Witzel has provided marketing leadership for software and technology services organizations. Her new approaches to strategy and execution, with a focus on demand generation and operational excellence across all marketing disciplines has created positive response, results and success.

By applying lessons learned from the business analysis and software engineering communities, marketing operational excellence can be transformed, yielding a faster Return on Marketing Investment (ROMI).

@MicroservicesExpo Stories
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Many IT organizations have come to learn that leveraging cloud infrastructure is not just unavoidable, it’s one of the most effective paths for IT organizations to become more responsive to business needs. Yet with the cloud comes new challenges, including minimizing downtime, decreasing the cost of operations, and preventing employee burnout to name a few. As companies migrate their processes and procedures to their new reality of a cloud-based infrastructure, an incident management solution...
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things ...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?
Every few years, a disruptive force comes along that prompts us to reframe our understanding of what something means, or how it works. For years, the notion of what a computer is and how you make one went pretty much unchallenged. Then virtualization came along, followed by cloud computing, and most recently containers. Suddenly the old rules no longer seemed to apply, or at least they didn’t always apply. These disruptors made us reconsider our IT worldview.