Scaling People: Claire Hughes Johnson on Building the Company Behind the Product

Hughes Johnson says writing Scaling People was pushed on her by Stripe co-founders Patrick and John Collison, and that it taught her how much work it is to build a company. She joined Google when it had about 1,800 people and left at roughly 60,000, then joined Stripe at around 160 people; it now has more than 7,000. The book is meant as a shortcut, but she insists that there really are none.

The idea came partly from founders who kept asking John Collison how Stripe scaled, and who came away saying they really wanted to talk to Claire. He joked that the company needed "Claire in a box." A chapter she wrote for Elad Gil's High Growth Handbook drew strong interest because it was so specific and tactical, which encouraged a longer version.

The biggest lesson she took from the Collisons is how much it pays to seek knowledge from others. Their reflex when facing any problem was to ask who she had talked to and what she had read. When Stripe needed levels and ladders, she called Square, Airbnb and a few other companies; one called it a blood bath, while another said they had waited too long and wished they had started earlier.

Stripe is known for its sparing use of titles, and Hughes Johnson says she and Patrick Collison agreed on it with little debate. Titles signal hierarchy and authority, while Stripe wanted a culture where the person with the knowledge is in the room and driving the decision, however senior they are. She admits the approach may have gone too far and that a bit more visible structure would now help.

The second reason is optionality. If you name someone head of marketing when the team is two people, you may have to layer someone above them when it reaches twenty, and taking a title away is worse than never giving one. She also finds it incongruous when a 25-person company has seven VPs.

Flexible titles even help in sales. A small Stripe team often sells to far bigger customers that try to match seniority one-to-one, and Hughes Johnson encourages people to describe their real scope creatively without inventing a title. She stresses that you should not lie about your role, only represent it honestly in a way that fits the situation.

Asked why operating and cultural structure deserves attention so early, Hughes Johnson says product-market fit is of course the most important thing, and her book is aimed at something like the half-step between zero-to-one and one-to-two. But she argues that product-market fit is only the product, which will not scale on its own. Companies that fall over often did so because the organization and culture were not built well enough, which then harmed the product and the mission.

She says the Collisons did not fully embrace that Stripe needed to scale until she arrived. Looking at inbound support demand and sales leads, she calculated the company should probably be twice its size, which alarmed people. Her house analogy follows: you need posts and beams, mechanicals such as wiring and plumbing, and a foundation, and if they are built to be replicable, like Google's OKRs from company level down to individuals, they work at every scale.

The risk of waiting is that people invent their own systems, leaving you with a house that was added on to seventeen times in two years and eventually needs a tear-down. For a pre-fit founder, her advice is to keep it simple: tell the investor story internally too, covering why you exist, what problem you solve and what early customers say. Then add a little hiring process early, because interviewing is a skill that does not come naturally, and document more as hiring speeds up.

The book opens with personal operating principles because Hughes Johnson believes management starts with the manager, not the team or the product. Her first principle is that self-awareness, which builds mutual awareness, is the most fundamental thing to crack. She recommends an exercise of picking ten values from a long list, then five, then three, ideally discussing why with a colleague, and then plotting your work-style tendencies, for example extroverted and task-oriented.

She illustrates the values exercise with a manager she calls Eli, whose commitment to transparency traces back to childhood when no one told him his mother was dying. The value was a real asset but sometimes problematic, since he shared unfinished plans with his whole team. Knowing the story behind a value helps you manage it.

Her second principle is to say the thing you think you cannot say. Borrowing Fred Kaufman's idea of the left-hand column, the harsh running commentary in your head, she suggests you detoxify it rather than suppress it. Two tricks: ask a question, even as simple as whether something is going unspoken, and own your observation as your perception rather than a judgment. Doing so often opens a door others were waiting to walk through.

Hughes Johnson says too many people think a manager's job is to be the expert who tells people what to do. In her view the job is to help people do their very best by providing context, information and coaching, and most coaching is exploration rather than instruction. She favors hypothesis-based coaching: a scientific hypothesis is just a well-informed intuition, so managers should not wait for a million data points before sharing an observation.

Her examples are small ones: asking how a presentation went and then noting the person seemed nervous, or pointing out to someone who pushed their chair away from the table whenever a topic became uncomfortable that they were doing it. The observation must be owned and offered as a mirror, and it should be mutual, with the other person free to give feedback back. She notes that Reid Hoffman told her he is more leader than manager, and shared a story of a hire who said he would not trust Reid to manage a McDonald's, which Reid took as proof of an open feedback culture.

Her third and fourth principles are to distinguish management from leadership and to come back to the operating system. In chaotic, high-growth environments, shared rituals such as quarterly goals or a standard launch process give stability because everyone has something to hold onto. As her responsibilities grew across product, design, operations and business development at Google, running every team on the same bare-bones structure let her context-switch without losing her footing.

The core of the book, Hughes Johnson says, is the house metaphor: founding documents are the foundation, supporting structures such as planning, OKRs and quarterly business reviews are the beams, and the operating cadence is the mechanicals. She notes that Stripe's annual customer event, Sessions, forces internal rhythm, and that an internal demo event roughly six months earlier pushes teams to build ambitious things first. Where leadership teams go wrong is trying many vehicles and abandoning them quickly, so she recommends doing very few things consistently and revising once a year.

Lenny adds that no perfect process exists, and Hughes Johnson agrees: there is no perfect org structure or performance system, but committing to one beats not having one. She also says every company is chaotic inside, recalling swapping tales of broken things with a founder friend on airplane aisles. Consistent ways of running things make a company feel well run even when the reality is messy.

The founding documents she recommends are a mission, long-term goals and operating principles or values. Stripe's mission, to increase the GDP of the internet, came from what customers and candidates kept repeating back, and a long-term goal such as advancing the state of the art in developer tools explains Stripe's investment in APIs and docs. Long-term goals also make short-term goals easier, because every annual goal tends to fit into three to five buckets such as international expansion or new products.

Her operating system comprises goals such as OKRs, a form and rhythm for quarterly business reviews, metrics and dashboards, a planning process, and a cadence for all of it. She admits every COO groans about planning because everyone hates it, but says you still need to fight your way to something. Cadence does not have to be a quarter: Stripe ran six-month processes for a while and moved some new product areas to business reviews every six weeks.

To tell whether a cadence is off, she says the review is too slow when its content feels stale and people say they already discussed it, and too fast when little progress happens between reviews. She also warns that if metrics are reviewed often and strategy rarely, the metrics review quietly becomes the strategy review. Extra check-ins create overhead and can slow velocity rather than increase it.

One Stripe habit she likes is looking at a team's live dashboard instead of building a special presentation, which forces dashboards to be real time and saves prep time. Even so, the company ended up with versions of the overhead problem, including a metrics review where a randomly spun wheel picked who presented.

Hughes Johnson notes that fewer than 20 to 30 percent of companies have a COO, and the role is most common at high-growth companies or those with a deeply operational element such as manufacturing, as with Apple or self-driving cars. It adds leverage when a founder is building the product, the company and the leadership team all at once. She worries about a mythical silver-bullet COO hire and suggests a lower-risk path of hiring a head of business operations or a more operational CFO, then seeing if they scale into more.

A friend once told her that the right amount of tension in her relationship with Patrick Collison was how you knew it was working. She reads that as mutual trust that she will deliver at the quality he wants, plus the freedom to push back on priorities or give hard feedback. A fantastic COO is not all hunky-dory, but the right friction with forward momentum.

She also cautions against hiring a COO to take away everything a founder dislikes doing, which she saw in recruiting conversations. Long lists of tasks to hand off suggested founders were not confronting parts of their own work that needed to evolve. At Stripe, she says, she worked collaboratively with the Collisons and others rather than lifting work off their plates.

In a rapid-fire round, Hughes Johnson says keeping alignment while scaling relies on codified documents plus smart communication; no single email or all-hands reaches everyone, so leaders should repeat themselves like marketers across channels. Offsites work because pulling people out of routine creates space and imprints memory, and a plan formed together by a group in a room is more effective than one handed down. For company-wide updates she recommends investing early in an intranet homepage, newsletters and short founder videos, ideally run by someone focused on internal marketing.

On meetings, she says calling one is too easy, so the bar should be higher: people should know why they are meeting, whether the aim is a decision or information, and who needs to attend. Her phrase is to make the implicit explicit, and to ask whether anyone can skip and read a note afterwards.

For product managers who have accountability but little authority, she recommends making decisions explicit by naming the decision, who makes it, the criteria and who is informed, using a model such as SPADE, RACI or RADAR. She also cites Bezos's type one and type two framing of irreversible versus reversible decisions. If you do not know who decides, it is probably you; and if worried, just ask rather than get stuck, because progress, impact and momentum are what everyone cares about.