More Disruption Coming from Software-First Responsive Organizations
Oct 16, 2016 by DROdio
One of the foundational changes affecting Global 2000 enterprises is the shift from “Businesses solving technology problems” to “Technology solving business problems,” meaning that software has become a deep competitive advantage for a new generation of responsive organizations, enabling them to play by entirely different rules and disrupting entire industries.
In the old model, a hospitality company dominated its industry by out-executing on things like service, property location and logistical efficiency. But a software platform like Airbnb doesn’t have any rooms to manage. It has no cleaning staff to hire, train and pay. Its competitive advantage comes from building a world-class software platform that connects guests to hosts, and also utilizes software to manage the booking, resolution and ranking processes. It’s all software-first.
These trends are playing out across multiple industries. Netflix uses its software dominance to win, while Blockbuster missed the memo. In our household, we still shop at Whole Foods and Costco, but we do it via software platforms like Instacart, Google Shopping Express and Amazon. These software platforms are using their software expertise to wrestle the customer relationship away from the traditional stores and re-focus it on the phones in our pockets — and what’s more intimate than these companies having a direct channel literally to millions of consumers’ pockets and indeed their very digital identities.
These trends are the reason we are starting Armory. We solved the engineering velocity problem at our last company, helping it go from 5 to over 2,000 deployments per month. Here’s a graph of the growth:
We saw first-hand how much happier the product and engineering teams became when they could commit code to master and have it immediately out in front of users, at scale. We saw how much faster the organization could execute. And the data bears these observations out. High-performing companies release code over 200x as often as low performing companies — Netflix, for example, deploys 4,000 times per day:
As an engineer, there’s nothing more de-motivating than working at a company that’s so scared of its software deployment process that it releases less often and puts more layers of human approvals on the release process in an effort to stem the fire drill that software deployments often are for these companies.
The irony of this cycle is that holding more features back to deploy in larger batches less frequently impacts the business in two devastating ways: 1) Larger deployments with more features introduce more risk into the deployment process, which makes the business even more scared to release code — a destructive cycle, and 2) releasing less often means many fewer opportunities to put code in front of customers and learn from them.
In this new software-first world, a company is only as agile as its ability to get its code in front of its users, which is why companies need to prioritize tooling that allows them to trust their deployments and deploy with more speed and confidence. Armory is here to help, with an enterprise-grade version of Spinnaker, the open-source industry-leading Continuous Delivery platform open sourced by Netflix in late 2015. Learn more about our solution here.
Recently Published Posts
Welcoming 2022: Reflecting and looking forward
Nearly all cultures globally have some form of celebration marking the Winter Solstice. Common threads found in most observances of the annual event are celebration of family and friends (living and past), reflection of the past year, and some form of giving thanks for continued health and sustenance. Exiting 2021, said celebrations would seem especially […]
Read more →
Resiliency and Load distribution
Introduction When scaling a network service, there are always two concerns: resiliency and load distribution, to understand these concepts let us first understand the broader term “Redundancy”. Redundancy is the duplication of a component to increase reliability of the system, usually in the form of a backup, fail-safe, or to improve actual system performance. Resiliency […]
Read more →
CVE-2021-44228 – log4j (Log4Shell) – an analysis
Today marked a 0-day disclosure of a rather nasty vulnerability in one of the most commonly used frameworks for logging – log4j. This one is nasty on multiple levels. Note that Armory Enterprise is NOT affected by this vulnerability. The impact on this vulnerability is likely huge and is already being exploited. Additionally it can […]
Read more →