We scan new podcasts and send you the top 5 insights daily.
Heroku's pitch was to replace your ops team, which created resistance. Kubernetes, while more complex, succeeded because its pitch was to empower the existing ops team, making them superheroes. This highlights a key product adoption principle: augment and empower users, don't threaten their roles.
Conventional wisdom suggests attacking an incumbent's weak points. Serval did the opposite with ServiceNow, targeting its core strength: configurability. By using AI to make customization drastically faster and easier, they offered a superior version of the feature that locks customers in, creating a compelling reason to switch.
To overcome fears of open-sourcing Google's internal Borg system, the Kubernetes team argued that an open-source alternative was inevitable, partly due to knowledge leaving with ex-employees. The real choice wasn't between proprietary or open, but whether Google would build and influence the dominant open solution or cede that ground to a competitor.
Users will switch from an incumbent if a competitor makes the experience feel effortless. The key is to shift the user's feeling from maneuvering a complex 'tractor' to seamlessly riding a 'bicycle,' creating a level of delight that overcomes the high costs of switching.
The business case for Kubernetes was articulated by framing it as a way for Google to maintain technological influence, unlike what happened when Hadoop was created from their MapReduce whitepaper without Google's involvement. This shifted the focus from direct revenue to long-term strategic influence and thought leadership.
Enterprise products must solve the complex, day-to-day problems of the implementers, not just the C-suite buyers. Slack built a dedicated admin dashboard separate from executive-level metrics to serve the critical but often ignored IT admin, whose job is facilitating work for thousands.
When rolling out the Odin platform at Uber, the team intentionally avoided a big-bang launch. They started with their own systems, then expanded to friendly teams, using an incremental approach to build momentum and prove value before approaching more resistant groups.
When trying to convince teams to adopt a new technology, the most effective strategy is to implement the solution for them. Presenting a finished, working migration is a much easier conversation than asking them to take on a large, uncertain task themselves.
Kubernetes was deliberately open-sourced because, as an underdog to AWS, a Google-exclusive product would be ignored by the market majority. Open sourcing allowed them to engage the entire developer community, build an ecosystem, and establish thought leadership, which is a more effective strategy than locking down tech when you aren't the market leader.
The "Odin" platform, which eventually managed all of Uber's stateful workloads, began as a project to containerize sharded MySQL for a single team. This bottom-up approach allowed them to prove the concept and build a working system before seeking wider, more political adoption.
When implementing a new productivity system, success depends more on team comfort than on the tool's advanced features. Forcing a complex platform can lead to frustration. It's better to compromise on a simpler, universally accepted tool than to create friction and alienate team members.