Welcome!

Microservices Expo Authors: AppNeta Blog, Elizabeth White, Gopala Krishna Behara, Sridhar Chalasani, Tirumala Khandrika

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 – linkedin.com/in/SoftwareHollis. 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 HollisTibbetts.com

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

@MicroservicesExpo Stories
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In his Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, will explore t...
The IT industry is undergoing a significant evolution to keep up with cloud application demand. We see this happening as a mindset shift, from traditional IT teams to more well-rounded, cloud-focused job roles. The IT industry has become so cloud-minded that Gartner predicts that by 2020, this cloud shift will impact more than $1 trillion of global IT spending. This shift, however, has left some IT professionals feeling a little anxious about what lies ahead. The good news is that cloud computin...
As Enterprise business moves from Monoliths to Microservices, adoption and successful implementations of Microservices become more evident. The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Documenting hurdles and problems for the use of Microservices will help consultants, architects and specialists to avoid repeating the same mistakes and learn how and when to use (or not use) Microservices at the enterprise level. The circumstance w...
SYS-CON Events announced today that Auditwerx will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Auditwerx specializes in SOC 1, SOC 2, and SOC 3 attestation services throughout the U.S. and Canada. As a division of Carr, Riggs & Ingram (CRI), one of the top 20 largest CPA firms nationally, you can expect the resources, skills, and experience of a much larger firm combined with the accessibility and attent...
SYS-CON Events announced today that HTBase will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. HTBase (Gartner 2016 Cool Vendor) delivers a Composable IT infrastructure solution architected for agility and increased efficiency. It turns compute, storage, and fabric into fluid pools of resources that are easily composed and re-composed to meet each application’s needs. With HTBase, companies can quickly prov...
Everyone wants to use containers, but monitoring containers is hard. New ephemeral architecture introduces new challenges in how monitoring tools need to monitor and visualize containers, so your team can make sense of everything. In his session at @DevOpsSummit, David Gildeh, co-founder and CEO of Outlyer, will go through the challenges and show there is light at the end of the tunnel if you use the right tools and understand what you need to be monitoring to successfully use containers in your...
What if you could build a web application that could support true web-scale traffic without having to ever provision or manage a single server? Sounds magical, and it is! In his session at 20th Cloud Expo, Chris Munns, Senior Developer Advocate for Serverless Applications at Amazon Web Services, will show how to build a serverless website that scales automatically using services like AWS Lambda, Amazon API Gateway, and Amazon S3. We will review several frameworks that can help you build serverle...
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud enviro...
@DevOpsSummit has been named the ‘Top DevOps Influencer' by iTrend. iTrend processes millions of conversations, tweets, interactions, news articles, press releases, blog posts - and extract meaning form them and analyzes mobile and desktop software platforms used to communicate, various metadata (such as geo location), and automation tools. In overall placement, @DevOpsSummit ranked as the number one ‘DevOps Influencer' followed by @CloudExpo at third, and @MicroservicesE at 24th.
By now, every company in the world is on the lookout for the digital disruption that will threaten their existence. In study after study, executives believe that technology has either already disrupted their industry, is in the process of disrupting it or will disrupt it in the near future. As a result, every organization is taking steps to prepare for or mitigate unforeseen disruptions. Yet in almost every industry, the disruption trend continues unabated.
In his General Session at 16th Cloud Expo, David Shacochis, host of The Hybrid IT Files podcast and Vice President at CenturyLink, investigated three key trends of the “gigabit economy" though the story of a Fortune 500 communications company in transformation. Narrating how multi-modal hybrid IT, service automation, and agile delivery all intersect, he will cover the role of storytelling and empathy in achieving strategic alignment between the enterprise and its information technology.
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations might...
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" ...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, will discuss how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He will discuss how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
The essence of cloud computing is that all consumable IT resources are delivered as services. In his session at 15th Cloud Expo, Yung Chou, Technology Evangelist at Microsoft, demonstrated the concepts and implementations of two important cloud computing deliveries: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). He discussed from business and technical viewpoints what exactly they are, why we care, how they are different and in what ways, and the strategies for IT to transi...
Thanks to Docker and the DevOps revolution, microservices have emerged as the new way to build and deploy applications — and there are plenty of great reasons to embrace the microservices trend. If you are going to adopt microservices, you also have to understand that microservice architectures have many moving parts. When it comes to incident management, this presents an important difference between microservices and monolithic architectures. More moving parts mean more complexity to monitor an...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound e...
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm.
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.