Uber repeatedly tried and failed to mandate the adoption of distributed tracing across all services. Despite years of emails and deadlines, the initiative never got done. This serves as a prime example that in a strong engineering culture, top-down directives without true buy-in will be ignored.
Related Insights
Building a culture of 100% team empowerment is dangerous. Commercial realities mean top-down directives are inevitable. If the organization isn't culturally prepared for this, it will grind to a halt when that moment arrives, causing widespread dissatisfaction.
A cultural shift towards top-down management, where engineers were no longer part of key decisions like moving to the cloud, led to a mass exodus of senior talent. When senior ICs cannot stand behind leadership's decisions, they lose the motivation to stay, even if the pay is good.
While empowering employees to experiment with AI is crucial, Snowflake found it's ineffective without an executive mandate. If the CEO doesn't frame AI as a top strategic initiative, employees will treat it as optional, hindering real adoption. Success requires combining top-down leadership with bottom-up innovation.
When Mozilla leadership pushed to adopt the WebRender engine based on "vibes" and momentum, they ignored valid concerns from the expert graphics team. This dismissal of deep technical expertise in favor of top-down enthusiasm proved toxic and led to the departure of key senior engineers.
Forcing innovations to "scale" via top-down mandates often fails by robbing local teams of ownership. A better approach is to let good ideas "spread." If a solution is truly valuable, other teams will naturally adopt it. This pull-based model ensures change sticks and evolves.
Amplitude's CEO notes that unlike previous tech waves, AI adoption was pushed by executives, not engineers. Engineers were initially skeptical, viewing the hype as "grifting," which created internal friction and required a deliberate internal education campaign to overcome.
Employees hesitate to use new AI tools for fear of looking foolish or getting fired for misuse. Successful adoption depends less on training courses and more on creating a safe environment with clear guardrails that encourages experimentation without penalty.
A project's success equals its technical quality multiplied by team acceptance. Technologists often fail by engineering perfect solutions that nobody buys into or owns. An 80%-correct solution fiercely defended by the team will always outperform a "perfect" one that is ignored.
The primary obstacle to adopting a shared platform model is cultural resistance. Teams accustomed to controlling their full stack view shared platforms as a loss of autonomy and a forced dependency. Overcoming this requires building a culture of trust and shared goals, not just proving the technological superiority of the platform.
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.