Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

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
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
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 next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
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 ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.