Kicking off Madrona Engineering Community Meetups with a Side of DevOps

If there is one topic that is on every engineering leader’s mind, regardless of the size of the company, it is how to ship more code more often and how to run that code reliably and efficiently. So, it was a no-brainer that we chose to kick off the first of our Madrona Engineering Community (MEC) meetups with an event on DevOps and Agile practices.

MEC meetups foster ongoing knowledge sharing and networking among engineering leaders across the Madrona portfolio. Our members are VPs of Engineering and CTOs across our portfolio companies.

As far as first events go, we started off with a bang! We had a packed house with over fifty of our engineering leaders attending as our panel of experienced speakers dove into the current and future for DevOps. Our panel was:

  • Tom Casey, SVP Engineering at DocuSign
  • John Ludeman, SVP Engineering at Skytap
  • Adam Johnson, Founder/CEO of IOPipe
  • Moderator, Joe Duffy (Founder/CEO of Pulumi

The make up of the panel was by design — to cover companies at different scale. DocuSign, for example, serves hundreds of millions of users and more than 1.5 million documents per day. Skytap is a mid-stage company that has seen its usage quadruple over the last two years, deploying up to 45,000 VMs and serving up to 2 petabytes of storage a day. IOPipe, in contrast, is in the early days of building its product with a distributed team churning out multiple releases every day! The DevOps goals and plans of each of these companies are different, which led to an interesting discussion under the expert probing of our masterful moderator Joe Duffy.

DevOps = ownership + accountability

While Joe did his best to instigate the speakers in taking opposing positions, he had no luck when it came to how they thought of DevOps. To each, DevOps was about aligning engineering teams with creating customer value and achieving business goals. The key, as each speaker emphasized, was to give developers end-to-end ownership (and the accountability that comes with it). Developers must be able to see the value they are delivering to the customers, or not. And, they must be provided with all the tools and processes, and more importantly, the organization and cultural support needed to succeed.

DevOps ≠ shipping more features

In the fog of war, there is often a tendency to add every feature request to the scrum. Shipping, however, is not a good measure of success. Adoption, utilization, learning, and direct revenue are much better measures of value creation. When it comes to DevOps, reemphasizing value creation and not just features shipped is important. DocuSign, for instance, made driving adoption (of their product) a company wide priority because, direct revenue is typically a trailing indicator of feature value. To keep everyone focused, they evaluated every shipped feature in light of adoption. It mostly worked for them.

DevOps is always a work in progress

No matter how small or big the company is, DevOps is never done. John from Skytap, for example, shared how, after operating for a few years, they realized that their organizational structure was getting in the way of shipping code quickly and efficiently. So, they reorganized and refocused the engineering teams to make sure that they stayed agile as the business scaled rapidly. Tom from DocuSign shared a similar experience, done at a greater scale in a more gradual manner. And, they both fully expect to redo their DevOps process and organization multiple times as their businesses continue to grow quickly.

No “no-ops” unless you also believe in unicorns

In this day and age of serverless, the topic of “no-ops” inevitably came up. To much of Joe’s delight, it elicited some strong reaction from the speakers. Long story short, the verdict was that no-ops does not work at scale. Every SaaS company, once it reaches a certain scale, needs specialized ops to ensure it can deliver the best user experience without blowing up its cost budget. DocuSign has “devs who op,” and every company could do with more of them. Similarly, the topic of SRE did not find a lot of love from the panel. The view was that, for most SaaS applications, it is impossible — or, at least not advisable — to insulate the developers from running the application.

Telemetry trumps testing

The other interesting insight that emerged from the discussion was that, no matter how much one invests in testing, telemetry is indispensable and if anything, more important. Skytap, for example, believes investing more in application telemetry than in running exhaustive regression tests. Similarly, DocuSign puts some of its best devs on telemetry. The emphasis on telemetry helps to speed up release cadence and detect unforeseen bugs.

Looking forward …

While most modern companies have adopted DevOps to a certain degree, most also struggle with several issues. First, balancing agile development with predictability (a must to run a business) is always hard. Hence, every engineering leader clamors for effective planning tools. The other issue is how to measure engineering productivity. Lines of code written or number of bugs fixed could be great vanity metrics, but they do not serve the real purpose. Finally, as we get ready for applications running on multiple clouds, we do not yet fully know the new challenges that will bring to DevOps.

Maybe, that’s where we will pick up at the next MEC meetup!

Every company is a technology company, but most don’t behave like one

In 2011, Marc Andreesen famously wrote a Wall Street Journal essay declaring that “software is eating the world.” Five years later, the five largest companies in the world by market capitalization are all software companies.

largestcosbymarketcap

However, in today’s information economy, Apple, Alphabet, Microsoft, Amazon, and Facebook are not the only important large technology companies. As technology becomes more and more pervasive across industries and functions, companies like Exxon, GE, Citi, and Walmart are all racing to become technology companies as well.

Today, we are less interested in the distinction between technology and non-technology companies (because there are very few successful companies that are not technology companies). Instead, it’s more interesting to ask questions like – Tesla is a technology company rapidly learning to become an automobile company, and Ford is an automobile company rapidly learning to become a technology company – which one is going to get there first?

In short, software is eating the world, but software companies aren’t the only ones taking a bite.

How do companies in real estate, finance, healthcare, manufacturing, or other industries that have traditionally not been recognized as technology industries become technology companies? What are some of the key learnings that we see from startups and companies that are successfully making this transition?

1. It starts at the highest level of leadership
Leading a transformation to become a successful technology company is not a job that can simply be tasked to the CTO or CIO. The level of engagement and investment to lead a successful transformation requires the CEO and board of directors to not only be fully bought in but to be the main drivers of the change.

Goldman Sachs has known for many years that technology is a key competitive advantage in financial services. In one recent WSJ article, a top Goldman executive valued a license for their risk measurement system at well over $1 billion, and possibly even up to $5 billion. They have since open-sourced the system in a move to attempt to drum up new business. More importantly, however, Goldman Sachs’ Chairman and CEO Lloyd Blankfein has repeatedly stated that “Goldman Sachs is a technology firm” and highlights the fact that Goldman Sachs actually employs more engineers than companies like Facebook, Twitter, or LinkedIn and often competes for talent and wins against top internet companies.

2. Talent is the most important asset of a technology company
One of the key drivers for the rapid growth of new technology companies is the low capital requirement to build a company today. New companies no longer need to buy hundreds of thousands of dollars of servers and equipment; instead, they can pay for servers on demand from cloud providers when needed.

This dynamic makes it more important than ever for companies to hire great people. In fact, a recent survey Madrona conducted in conjunction with its annual CIO Summit found that 89% of Fortune 500 CIOs say hiring top talent is their number one concern today.

geyoutube
GE Youtube Channel.

GE has likely made the largest investment in this space to change the story that young engineers and college graduates hear about the company with a series of Youtube videos and television ads. Though it remains to be seen whether these videos work, GE has recognized that filling its talent pipeline with young engineers and technologists is critical and is investing accordingly.

3. Technology needs to be at the core of company culture, not an afterthought
At a company like Microsoft or Facebook, engineering positions are the most prestigious, highest status roles at the company. The founders and CEOs of technology companies are often engineers and may have even built early version of the products themselves.

For companies to successfully make the transition to become a technology company, cultures need to change to take into account the unique way that software development works and to highlight the importance of technology and the people who manage and build it.

One example of a move towards a developer friendly culture is happening at Walmart. WalmartLabs recently open sourced Electrode, the application platform that powers Walmart.com. Electrode is a modular platform that helps improve application performance, and Walmart is open sourcing the software to give back to the open source world and benefit from additional contributions from the community.

It is important to keep in mind that building a technology-driven culture is not just about free lunches and massages. As Joel Spolsky CEO of Stack Overflow said in a recent interview, “If you want to attract and keep developers, don’t emphasize ping-pong tables, lounges, fire pits and chocolate fountains. Give them private offices or let them work from home, because uninterrupted time to concentrate is the most important and scarcest commodity.”

4. Companies need to move fast and adopt agile practices
The pace of technology adoption is getting faster and faster every year. For example, it took decades for electricity and telephones to reach 50% of US households, but today it takes only years for new technologies like smartphones and tablets to reach a majority of the population. This underscores the importance for companies to continuously adopt new technologies that can enhance productivity and also to continuously experiment with new technologies that have the potential to be disruptive to the business.blackrock

An interesting anecdote from The Lean Startup, one of the manifestos for startup founders, is that Intuit holds themselves accountable to being innovative and agile by using two key metrics: (1) the number of customers using products that didn’t exist three years ago and (2) the percentage of revenue coming from offerings that did not exist three years ago. Historically for Intuit, it took a new product an average of 5.5 years to reach $50 million in revenue; at the time the book was written, they had multiple products generating $50 million in revenue that were less than a year old.

Particularly, as the world is moving towards cloud computing, continuous development and continuous updates are the name of the game. Agile development practices enable you to continuously deliver better experiences for your customers and waterfall development methodology is a relic of the past.

5. Companies need to look forward and avoid getting caught in the innovator’s dilemma
The classic case for why legacy competitors can do everything “right” and fail is the force of disruptive innovation described in Clayton Christensen’s The Innovator’s Dilemma. Businesses can reject innovations based on customers’ current needs while innovative upstarts develop products in a way that meets customers’ future needs.

Stratchery
Stratchery

Recently, we have seen automakers take very innovative approaches to automotive technology as autonomous vehicles move to the front and center of the startup world with the acquisitions of companies like Otto and Cruise and public pilots of new technologies like Uber’s self-driving cars in Pittsburgh or Tesla’s Autopilot feature.

Ford, in particular, has been very vocal about the autonomous future and the importance of working differently in the context of today’s technology-driven world. Ford’s CEO, Mark Fields, has written that “As little as four years ago, our approach was aligned with the thinking of most automakers today, which is taking incremental steps to achieve full autonomy by advancing driver assist technology. This is not how we look at it today. We learned that to achieve full autonomy, we’d have to take a completely different pathway.”

Conclusion
The race to become the market leader across a variety of sectors and geographies is speeding up amongst older incumbents and promising, young startups. Startups have a lot to learn from the established management and financial practices of incumbents, but incumbents have a lot to learn from startups as well. The companies, young or old, that use technology to best create competitive advantages for themselves will win.

Technology needs to be a fundamental fabric of the company’s DNA and culture as companies truly internalize that “Every company is a technology company”.