Culture is a company’s operating system, and documentation is the code that keeps it performant. As I lead product teams, I’ve learned that great cultures don’t just happen—they’re intentionally designed, scaled, and maintained. When founders and operators ask me which organizations model this best, Stripe reliably tops the list.
I recently sat down with Brie Wolfson to compare notes on how documentation, rituals, and communication norms shape high-velocity teams.
Brie spent nearly 5 years at Stripe, where she worked on bizops and launched Stripe Press, followed by a stint at Figma where she worked on education. She then started her consultancy, named The Kool-Aid Factory, to share her lessons on building team cultures. And now she’s operating as a first-time founder building Constellate, a new productivity and communications tool for teams.
In our conversation, we zeroed in on company culture—what it looks like when it’s working, how to codify it early, and how to scale it without diluting what makes it special. A decade ago, many teams tried to emulate the playbooks of companies like Google and Amazon. Today, a newer guard has emerged, and Stripe is often the culture benchmark that startups aim to emulate.
Brie peels back the layers into not just the cultural pillars that drove Stripe’s meteoric rise, but also how these showed up in day-to-day work.
We also zoom out beyond Stripe to talk about her work teaming up with companies with The Kool-Aid Factory, seeing culture and company-building up close. Brie shares advice on codifying your operating principles, establishing meaningful rituals, and growing this kernel of culture as the company scales.
Here’s what resonated most for me—and what I’ve seen pay dividends in product management leadership. First, treat kickoffs as the contract between intent and execution. A strong kickoff doc aligns on the problem statement, the “why now,” the DRI and decision log, risks and non-goals, and success measures tied to outcomes vs output OKRs. This single artifact becomes the source of truth for product discovery, scope decisions, and stakeholder communication.
Second, close the loop with retros that are structured and searchable. Think of retro docs as compounding assets: what worked, what didn’t, what we’ll change, and where decisions deviated from the kickoff. Over time, these narratives accelerate onboarding, reduce repeated mistakes, and strengthen operating principles.
Third, make Slack channels work like living documentation. Clarify a channel’s purpose, pin an index post, standardize naming conventions, and link to the latest kickoff and retro. When Slack is curated—not chaotic—it becomes a lightweight knowledge system that complements your docs rather than competing with them.
Finally, remember that rituals are the scaffolding for culture. Whether it’s weekly written updates, decision memos, or quarterly operating principle reviews, the goal is to make writing a team sport. Writing sharpens thinking, scales context, and reduces the cost of coordination as headcount grows.
Read the full essay Brie recommended during the interview: Reality has a surprising amount of detail and the article she penned for First Round Review: Ditch Your To-Do List and Use These Docs to Make More Impact.
You can follow Brie on Twitter @zebriez
If you’re building a product organization—or evolving from IC to manager—this playbook helps you replace ambiguity with clarity, reactive busyness with intentional outcomes, and scattered updates with a coherent, documented operating rhythm. Start with one ritual, write it down, and let the practice compound.
Leave a Reply