Welcome!

Microservices Expo Authors: LeanTaaS Blog, Derek Weeks, Don MacVittie, Karthick Viswanathan, Gopala Krishna Behara

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
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).
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...
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 c...
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 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...
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
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...
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...
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.
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...
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 ...
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.
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...
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.