We scan new podcasts and send you the top 5 insights daily.
Lawson distinguishes culture, the daily feeling, from values, the words that let you steer it. He says writing values too early is a mistake because you don't yet know who you are. Inertia is doing it now that it has crossed about 50 people, which he sees as roughly the right time.
Don't ask "what should our values be?" Instead, identify the 5-10 things that are the reason you are succeeding. Codify those real, existing behaviors—like "speed above everything"—into your company's operating principles. This makes them authentic and effective.
Create short, memorable phrases or "isms" that articulate your core values (e.g., "Constant Gentle Pressure"). This provides your team with a shared language and metasignal, reinforcing cultural priorities and making them easily scalable across the organization.
Create a public document detailing your company's operating principles—from Slack usage to coding standards. This "operating system" makes cultural norms explicit, prevents recurring debates, and allows potential hires to self-select based on alignment, saving time and reducing friction as you scale.
To ensure cultural consistency while scaling, A16Z codifies its values in a document that every new hire must sign. This is followed by a personal one-hour briefing from a co-founder, making the culture explicit and non-negotiable from day one.
Static company values risk reinforcing behaviors that were vital early on but become detrimental as an organization scales. At Stripe, leadership deliberately re-examined and revised company values roughly every 18 months. By evaluating which values to keep, which were beginning to rate-limit growth—such as early extreme leanness—and which emerging negative behaviors required cultural corrections, they ensured cultural principles matched each operational phase.
Instead of setting values on day one, Workshop's founders waited 12 months. This allowed the values to emerge organically from their early struggles and successes. The resulting principles were more authentic and meaningful because they reflected the team's actual lived experience and became actionable guides.
Instead of defining values on day one, Roblox operated for years with its first 10-12 employees and then codified the principles that were already working. This observational approach is like paving paths where people already walk, ensuring values are authentic and adopted.
Setting values on day one often leads to inauthentic principles. A more effective approach is to operate the business, observe which behaviors are genuinely rewarded and cherished, and then name those emergent qualities as your official values, ensuring they reflect reality rather than aspiration.
Culture isn't about office perks; it's the unobserved behavior of your team. To shape it, a leader must explicitly communicate their operating principles and non-negotiables from day one. This sets the standard for how the team functions autonomously.
Ben Horowitz argues that culture isn't defined by platitudes like 'we love entrepreneurs.' It's defined by tangible actions: Are you on time? Do you respond to emails? Your culture is what you *do* and what behaviors you tolerate, not what you write on a wall.