Scaling a company: operational principles from Stripe's COO

Executive overview

Most founders focus on product market fit but neglect building the company itself — and that gap eventually kills momentum. Claire Hughes Johnson, former COO of Stripe, scaled the company from 160 to 7,000+ people and codified the playbook in her book Scaling People.

The core argument: operational structure and cultural fabric must be built earlier than feels necessary. If you don't lay the foundations, people invent their own systems — and you end up tearing them down later.

The company you build is as important as the product you build — and it needs to start sooner than you think.

Four personal operating principles

• Build self-awareness to build mutual awareness — understanding your own motivators, blind spots, and tendencies makes you a more effective leader and manager
• Say the thing you think you cannot say — frame it as a question, own the observation, avoid judgment; others are usually thinking it too
• Distinguish management from leadership — management is enabling people to do their best work; leadership is setting direction; conflating them creates problems early in careers
• Come back to the operating system — a stable, repeatable way of running things creates calm amid chaos, especially when context-switching across teams or functions

Crystallising your operating principles

• Start with a values exercise: from a list of 70–80 values, narrow to 10, then 5, then 3
• Find the story behind each value — formative experiences explain why a value is non-negotiable
• Plot yourself on two axes: introverted/extroverted and task/people oriented
• The combination of values + work-style tendencies forms your operating belief system

Saying the uncomfortable thing

• Ask a question instead of making a statement — questions are less threatening
• Own the observation: "I noticed..." or "I wonder if..." not "You did X wrong"
• The explorer mindset: approach difficult conversations with curiosity, not a verdict
• Hypothesis-based coaching: form a well-informed hypothesis from early signals, then explore it with the person rather than waiting for a mountain of data
• Hold up a mirror — many people have no idea how they're coming across physically or verbally

The house metaphor: three components of company infrastructure

• Founding documents (foundation): mission, long-term goals, operating principles/values
• Operating system (supporting beams): goals/OKRs, quarterly business reviews, planning processes, metrics dashboards
• Operating cadence (mechanicals): the rhythm — how often you review, plan, and communicate

Founding documents

• Mission: one line capturing what you're trying to accomplish; use it internally, not just for investors
• Long-term goals: the 3–5 themes that sit between the mission and annual targets (e.g. "advance the state of the art in developer tools"); these rarely change and make shorter-term goal-setting easier
• Operating principles: codified values that help candidates self-select and help employees make decisions without escalating

Operating system

• Set goals at the company level so they replicate down to teams and individuals — OKRs work because the structure is reusable at any scale
• QBRs (quarterly business reviews): review strategy and metrics together; if strategy gets discussed during metrics reviews, your strategy cadence is too infrequent
• Planning: no perfect process exists — commit to one and iterate annually; don't copy other companies' systems wholesale
• Look at live dashboards rather than pre-prepared decks — it forces real-time data hygiene and eliminates prep overhead

Cadence signals and adjustments

• Cadence is too fast: not enough meaningful progress between reviews
• Cadence is too slow: content feels stale, meetings repeat prior conversations
• Don't default to quarterly just because it's standard — Stripe ran six-week cycles for some product areas
• Fewer, consistent rituals beat a grab bag of frequently swapped processes

Titles and hierarchy

• Flat titling preserves optionality: don't make someone CMO when the team is two people
• Hierarchy-heavy titles signal authority over expertise — the wrong cultural message for a high-trust environment
• Sellers can describe scope creatively without inflating titles; it also helps in meetings with larger, more hierarchical buyers

When and whether to hire a COO

• Fewer than 20–30% of companies have a COO; it's not an automatic role
• Most useful when a founder is simultaneously building product, hiring leaders, and scaling operations
• Lower-risk alternative: hire a head of business operations and expand the scope if it works
• The right COO relationship has just the right amount of tension — mutual trust plus productive friction, not frictionless agreement

Decision-making

• Make the implicit explicit: state what decision is being made, who is making it, and the criteria
• Use a framework (RACI, SPADE, Bezos's Type 1/Type 2) — pick one and commit to it
• Type 1 decisions: high-impact, irreversible — slow down; Type 2: low-impact, reversible — just decide
• Default assumption: if you don't know who the decision maker is, it's probably you; act on it rather than stalling
• Being a force for positive momentum is a career differentiator

Hiring process

• Don't just hire people you know; define what capabilities you need even pre-PMF
• Interviewing is a skill — train people on it; use rubrics and structured questions
• Build levels and ladders earlier than feels necessary; waiting until 800+ people makes it far more painful
• Seek outside advice before implementing big structural changes (e.g. call two companies that have done it already)

Running effective meetings

• Calling a meeting is easy — the barrier should be higher
• State the objective explicitly: is this a decision, an information share, or a brainstorm?
• Name the decision maker and the decision criteria upfront
• Remove people who don't need to be there; send a summary instead
• Too many meetings are implicitly about something — make the implicit explicit

Keeping people aligned at scale

• One communication is never enough — repeat core messages across multiple channels
• Use different formats: email, video, Slack snippets, all-hands; think like a marketer
• Invest in an internal communication strategy early — it doesn't feel urgent until it's broken
• Smart sales leaders are a useful model: they keep distributed teams aligned on product and messaging constantly

Off-sites and team cohesion

• Off-sites work because they break routine and create shared memory
• Group formation of plans creates buy-in that top-down distribution does not
• The goal is not to present a plan — it's to build one together
• No good substitute found for genuine time outside the normal work rhythm