14 More Lessons from 14 Years at Google - Addy Osmani

2026-05-14 · source · source ↗ · raw capture · wiki page

Key Lessons

Problem Selection & Prioritization: "Every yes is an implicit no to something else."

Decision Clarity: Start meetings with explicit asks: "approve, choose, unblock, or inform.”

Specificity Over Intention: Not "we should improve onboarding" but "On Tuesday, Sarah will run three user sessions."

Decision Speed vs. Code Speed: Slow decisions are greater organizational risk than slow code. Fastest teams have clear authority, distributed context, psychological safety.

Reliability as Product Feature: Error budgets make reliability tradeoffs explicit. "You wouldn't ship a feature without product review. Don't ship a system without reliability discussion."

Team Interfaces: Cross-team dysfunction stems from unclear boundaries, not communication gaps. Undefined contracts require endless meetings.

Against Hero Culture: "If one person saving the day is a recurring pattern, that's a failure mode rather than a badge of honor."

Observability: Features without telemetry create hidden failures. Logs, metrics, dashboards are part of completion.

Code Review Standards: Small PRs reduce friction, ship faster, improve feedback cycles.

Coordination Costs: Every new hire adds edges to the organizational graph, not just nodes.

Migration Complexity: Successful migrations require sustained sponsorship, dedicated ownership, credible deprecation timelines.

AI and Curation: As code generation is commodified, taste and selection distinguish valuable engineers.

Trust as Infrastructure: Trust is a latency optimization for decisions.

Notable Quotes

"The fastest engineering team I ever worked with wasn't the one with the best programmers. It was the one where decisions happened in hours instead of weeks."

"The work is about making it easier for normal people to do extraordinary things on a normal day."