Click here to close now.


Microservices Expo Authors: Pat Romanski, Liz McMillan, Yeshim Deniz, Elizabeth White, Lori MacVittie

Related Topics: Microservices Expo, Agile Computing

Microservices Expo: Article

How to Wreck a Good Product in 90 Days or Less

Why settle for success when you can guarantee failure?

The purpose of this article is to tell you how to take a perfectly good (or even a great) product that you've potentially spent years and millions of dollars creating - and thoroughly and efficiently ruin it in the shortest amount of time possible.

"Why would I want to do that?," you might ask.  Honestly, I don't know why.  But there must be a good reason because I see it happen with shocking regularity.

For those of you who have read my article "Are You Your Own Worst Enemy?," that article was written to help products succeed in the marketplace.  I'd advise you to ignore that article, as it's advice runs contrary to the purpose of this article - achieving market failure.

So, You've Developed a Great Product....
My frame of reference tends to be software - but the principals apply just as well to hardware, any "high tech" product, even consumer packaged goods.  Perhaps you or your company has created the next great SaaS or Cloud software product.  Or maybe it's the most amazing Ketchup the world has ever tasted.  The concept remains the same.

No matter the industry, we're talking about scenarios where you've invested a lot of time and money to create a product, and now it's time to think about bringing it to market and hope that you sell a lot of it.

A Product Launch
Bringing a new product to market is a marketing and sales process (not an event) called a Product Launch.  It is one of the most critical parts of a go-to-market strategy.

Very few of them are successful - only 3% of them.  I didn't make that number up - it's in an April 2011 article in the Harvard Business Review.  And 3% is optimistic - it's based on Consumer Packaged Goods vendors like Proctor & Gamble - companies that do marketing better than any other industry "period."  If anyone can pull off a successful product launch, it's a company like P&G.

If these heavily marketing-driven companies only achieve product launch success 3% of the time, the track record for Software - with its notoriously incompetent, sloppy, shoot from the hip, metrics-free, measurement-free and methodology-free marketing approach is at best 1%. Most software succeeds despite marketing, not because of it.

Take a Moment and Reflect
You're an entrepreneur and you've spent a year or more developing a product.  Probably hundreds of thousands to millions of dollars.  You're betting your future and the future of a lot of people on this investment.

Or you're a bigwig executive at some corporation and you've spent millions and millions of dollars of shareholder money to develop a new product (or major enhancement to an existing product).  You've made serious commitments to the C-levels and the board.

I am officially telling you that your odds of success are approximately 1 in 100.  Perhaps a 1 in 10 chance of "just scraping by".

Your product will not live up to expectations.  You will lose a lot of money on the product.  You'll quite possibly lose your company or job, or suffer a significant career setback.  Other people in the organization will be impacted.

How to Succeed?
Now is where I shift the tone of this article and tell you how to succeed, right?  Umm, no.  My goal is to deliver on the promise I made in the title - how to pretty much eliminate any chance of success and how to reduce the odds of "just scraping by" from 10% to perhaps 1%.

In writing this article, I am reflecting back on 25 years of life in the software industry.  I'm digging up some memorable disasters, stripping out anything that was done right, and distilling all of that badness into a small number of actionable things that you can do to guarantee product failure.

Product Failure
Note that I didn't say "product launch failure" - I said "product failure."  If the product launch process is unsuccessful, the product will fail.  That's the way it works.

I'm not making that up.  Check around - Google the term "product launch definition."  Pragmatic Marketing - a champion of bringing real, grown-up, measurable and effective marketing to the software industry defines it as "the process of bringing a product to market in such a way that it generates sales velocity." No sales velocity = no success.

Note: Avoid browsing the Pragmatic Marketing website. It is chock-full of "best practices," and other such things that are focused on maximizing success.

What do I mean by "product failure" - the product doesn't sell. Sales of the product don't meet expectations. The commitments made to investors, the board, C-levels are broken.  Money that is spent on staffing up in anticipation of a successful product is wasted.

Predicting Failure
There are two major predictors of whether a product will be successful in the marketplace:

1) Does the product do something important?

2) Is there a strong plan to "bring the product to market"?

If the answer to either one of these answers is "NO," then you've succeeded in creating a plan for failure.

Six-Point Plan for Recovery
Congratulations. Rather than leaving failure to chance, you've planned for it - nearly guaranteed it.

That gives you extra time to plan for the "post-failure recovery plan," which is important.  Although I'm quite critical of the typical level of marketing maturity in the software industry, I can say without a doubt that software marketeers are some of the best "recovery planners" in the business.

From what I've observed, a six-point plan is optimal. These tasks should be followed in order - if done well, you may only need to go as far as item #2,#3 or #4.

Recovery Plan:

1) Start talking about external factors - the economy, the competition, etc.

2) If at all possible, get promoted ahead of the "crash and burn"

3) Backpedal on goals and commitments and otherwise reset expectations that were "too aggressive and unrealistic" - get the board and the C-suite to own the mistake

4) Blame the sales department for lack of execution and get the head of sales sacked

5) Shift the focus to product development because the product isn't good enough (this rarely works, but it will buy you some time)

6)  Try to re-launch the product (truly a last-ditch "Hail Mary" maneuver)

Moving Forward
Hopefully I've convinced you that the path to destroying a perfectly good product lies in sabotaging the product launch. That way you maximize the damage to the company and to yourself.

Simply creating a bad product is an inferior option - there's a strong likelihood that the product will get canceled and thus the damage minimized. Or the product might be a sales success even though the product itself is weak (the first three releases of products for one particular software vendor are often cited).

My next article, scheduled for release tomorrow, will provide a detailed template on how to architect a "crash and burn" product launch - as well as a checklist for you to follow, so you can make sure you've gotten everything wrong.

More Stories By Hollis Tibbetts

Hollis Tibbetts, or @SoftwareHollis as his 50,000+ followers know him on Twitter, is listed on various “top 100 expert lists” for a variety of topics – ranging from Cloud to Technology Marketing, Hollis is by day Evangelist & Software Technology Director at Dell Software. By night and weekends he is a commentator, speaker and all-round communicator about Software, Data and Cloud in their myriad aspects. You can also reach Hollis on LinkedIn – His latest online venture is OnlineBackupNews - a free reference site to help organizations protect their data, applications and systems from threats. Every year IT Downtime Costs $26.5 Billion In Lost Revenue. Even with such high costs, 56% of enterprises in North America and 30% in Europe don’t have a good disaster recovery plan. Online Backup News aims to make sure you all have the news and tips needed to keep your IT Costs down and your information safe by providing best practices, technology insights, strategies, real-world examples and various tips and techniques from a variety of industry experts.

Hollis is a regularly featured blogger at ebizQ, a venue focused on enterprise technologies, with over 100,000 subscribers. He is also an author on Social Media Today "The World's Best Thinkers on Social Media", and maintains a blog focused on protecting data: Online Backup News.
He tweets actively as @SoftwareHollis

Additional information is available at

All opinions expressed in the author's articles are his own personal opinions vs. those of his employer.

@MicroservicesExpo Stories
Between the compelling mockups and specs produced by analysts, and resulting applications built by developers, there exists a gulf where projects fail, costs spiral, and applications disappoint. Methodologies like Agile attempt to address this with intensified communication, with partial success but many limitations. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, will present a revolutionary model enabled by new technologies. Learn how busine...
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
The APN DevOps Competency highlights APN Partners who demonstrate deep capabilities delivering continuous integration, continuous delivery, and configuration management. They help customers transform their business to be more efficient and agile by leveraging the AWS platform and DevOps principles.
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at @DevOpsSummit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
For it to be SOA – let alone SOA done right – we need to pin down just what "SOA done wrong" might be. First-generation SOA with Web Services and ESBs, perhaps? But then there's second-generation, REST-based SOA. More lightweight and cloud-friendly, but many REST-based SOA practices predate the microservices wave. Today, microservices and containers go hand in hand – only the details of "container-oriented architecture" are largely on the drawing board – and are not likely to look much like S...
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at, and Tomer Levy, co-founder and CEO of, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the archi...
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Our guest on the podcast this week is Jason Bloomberg, President at Intellyx. When we build services we want them to be lightweight, stateless and scalable while doing one thing really well. In today's cloud world, we're revisiting what to takes to make a good service in the first place. Listen in to learn why following "the book" doesn't necessarily mean that you're solving key business problems.
IT data is typically silo'd by the various tools in place. Unifying all the log, metric and event data in one analytics platform stops finger pointing and provides the end-to-end correlation. Logs, metrics and custom event data can be joined to tell the holistic story of your software and operations. For example, users can correlate code deploys to system performance to application error codes.
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Bradley Holt, Developer Advocate at IBM Cloud Data Services, will demonstrate techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, ...
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction....
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attende...
With containerization using Docker, the orchestration of containers using Kubernetes, the self-service model for provisioning your projects and applications and the workflows we built in OpenShift is the best in class Platform as a Service that enables introducing DevOps into your organization with ease. In his session at DevOps Summit, Veer Muchandi, PaaS evangelist with RedHat, will provide a deep dive overview of OpenShift v3 and demonstrate how it helps with DevOps.
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
In a report titled “Forecast Analysis: Enterprise Application Software, Worldwide, 2Q15 Update,” Gartner analysts highlighted the increasing trend of application modernization among enterprises. According to a recent survey, 45% of respondents stated that modernization of installed on-premises core enterprise applications is one of the top five priorities. Gartner also predicted that by 2020, 75% of