Scaling People with Claire Hughes Johnson

1. How to Find and Hire Sales Leaders 

Good Salespeople Are Not Always Good Builders

• There are people who are good salespeople and there are people who are good sales leaders. They are usually not the same people. The builder sets up the operations, metrics, learning loops, and infrastructure. The steady-state leader manages the pipeline, sets quotas, and keeps the team executing.
  
  • A player-coach who can sell and coach but cannot stand up the operational scaffolding is a common archetype at the Series A/B stage
• If you have a steady-state operator in a builder role, your options are:
  
  • Partner them with a product or technical person who can teach the operational loop-building - someone who will create the metrics framework and the review cadence alongside them. 
    
    • This sometimes works but sometimes just creates two people confused about their roles.
  • Accept that it is a talent issue and start the conversation. The earlier you have this conversation, the more options you have - the person can transition into a senior IC role, you can negotiate a graceful exit, or you can restructure around them. Waiting makes all of these harder.
  • In the meantime, dive in as the founder. Do not wait for the sales leader to build the operating cadence. Set it yourself: a weekly sales all-hands with a structured agenda, a deal review format, a metrics dashboard. Be unapologetic about the level of involvement. The more structure you create, the easier it is for a future leader to inherit and run.

Hire Smart Generalists First, Experienced Sellers Second

• If you are early and still figuring out your sales process, metrics, and value proposition, you need a different hire than a more established company would make. Start with smart generalists who can figure out the sales motion alongside you, then bring in experienced salespeople to run it.
  
  • Generally, recruiting firms are not the most helpful for early-stage sales leadership hires. The candidate profile is too specific in that you need someone who is part builder, part seller, and fully comfortable with ambiguity.
• Instead, find a company that is bigger, has scaled, and has had to solve a similar problem. Find who ran or built their sales org during their formative years - typically not the current VP of Sales but the second or third hire on the team who was there when it was zero to one. Mine their referral networks. These people are hard to find through standard channels because they are not looking and they are not on recruiting platforms.
  
  • Make the unusual deal velocity a feature, not a bug. If your product moves faster than traditional enterprise sales, set expectations upfront with data. Show candidates the average time to close, and if that timeline surprises them, they may not be the right fit.

Example: Stripe’s Biz Ops Model for Early Sales

• Stripe built its first sales function by hiring people with classic training in consulting, banking, or private equity who also had good professional skills, analytical ability, and entrepreneurial instincts.
• These generalists partnered directly with the founder to figure out what selling the product looked like. They became the initial sales team and account management team.
• Once the model was proven, Stripe hired experienced salespeople to scale it. The generalists moved on to other projects across the company.
• The ideal early sales profile combines three things:
  
  • Classic professional training (analytical rigor, structured thinking)
  • High learning aptitude and entrepreneurial instincts
  • Willingness to do the unscalable thing first, then teach it

2. Running Multiple Leadership Searches

The Founder Has to Do It - At This Stage, You Cannot Delegate

• At the Series A/B stage, the founder probably does not have anyone who can approximate their judgment in leadership hiring. It sounds like the right answer to delegate, but the reality is that no one else knows the company, culture, and context well enough yet.
• Sequencing is often necessary. Running two searches at once is doable; three to four gets genuinely hard. When the number rises, the alternative is to make recruiting your main job for a period - block hours daily, check your pipeline every day, send notes after every meeting.
  
  • It is normal and necessary at this stage to have even a third of one’s time go to recruiting in some periods
• Sequencing is often necessary. Two simultaneous searches is the practical maximum. Three to four in parallel means all of them slow down, the best candidates fall out of process because you cannot move fast enough, and you start making compromises on bar. If you have to run more than two, sequence them aggressively: finish one before starting the next.
  
  • Alternative: make recruiting your primary job for a defined period. Block two to three hours every day for recruiting. Treat it like a sales pipeline - stage the candidates, run a weekly review of where each search stands, set a cadence for outreach and follow-up. This is not glamorous, but it is the only way to close multiple searches without letting them drag.

 Involve Trusted Peers Who See Candidates Differently

• Involve trusted external perspectives early. Bring in one or two people you trust - not recruiters, but operators who have hired for similar roles - to run early-stage interviews. They will see things you miss because you are too close to the problem. The goal is not to outsource judgment but to add a different lens before you have committed significant time to a candidate.
  
  • Watch out for internal resistance. Existing team members often resist a new senior hire not because they have good judgment about the candidate, but because they do not want a boss. This resistance will surface as concerns about culture fit or qualifications, but the underlying issue is political. Name it and manage it separately.

 How Recruiting Evolves and Who Eventually Owns the Function

• Early on, it is another leader in the company who learns your taste and acts as a proxy. Think of a COO or head of a function who shadows your process.
• Next, a senior experienced recruiter who helps coordinate the process and run some of the conversations. This should be someone you have deeply calibrated
• Eventually, a leadership recruiting team that either works with an outside firm or does it internally. But even then, the founder remains the hiring manager - the job just gets a little smaller and more specific.
  
  • Do not try to jump to the third stage before the second. The calibration has to exist before the delegation works.

3. Layering & Restructuring

Flipping a Reporting Structure 

• One of the most difficult organizational decisions a founder faces is when a VP hired below an existing leader performs well, and the right approach looks like flipping the reporting structure to have the existing leader report to the VP. 
  
  • This creates genuine personal and political complexity and requires a delicate sequence to execute without destroying the relationship.
• Test awareness before you act. The first conversation is diagnostic: do you bring it up with the current head of sales, or do you wait? Approach the conversation in two parts.
  
  • Part one: Talk to the current head of sales first - before talking to the VP. Give them the respect of being included in the process rather than learning about a structural change after it has already been decided. Ask how they are feeling about the dynamic. In most cases, the person already knows. They can feel that they are not performing at the level the moment requires. Naming it together is less brutal than surprising them with it.
  • Part two: Only after that conversation, bring in the VP and frame the new structure together.
• Frame the flip as a development opportunity, but only if it genuinely is. "You could learn a tremendous amount from this person" is a legitimate framing if you believe it. 
  
  • If you do not, do not say it - it will read as condescending. Be specific about what the development looks like and what the path is.
• Flipped structures can work, but only under two conditions:
  
  • The incoming leader (the VP) actively earns the trust of the person now reporting to them. This requires intentional relationship-building, not just assuming authority.
  • The person in the subordinate role has genuine daylight - a path to grow, visibility, and a role that is real rather than decorative.
• Reference culture matters. Stripe explicitly normalized role-switching and structural changes even at the executive level. Alluding to that - "this kind of restructuring is common in companies at our stage, including very successful ones" - does not fix the emotional reality but it reduces the stigma.

Tactic: Say The Thing You Think You Cannot Say

• The biggest mistake founders make in these conversations is softening the message to the point where it does not land. 
• The concept here comes from Fred Kofman's Conscious Business - the "left-hand column" exercise, where you write what you are actually thinking alongside what you are actually saying. The goal is to close the gap. 
  
  • If you think the current leader is not scaling with the company, say that directly, with care. People can handle hard truths; what damages trust is inconsistency between what is communicated and what is real.
    
    • You cannot say “I think this person is better caliber than you.” But you can detoxify that thought and say a version of the truth with care and directness.
  • Claire also applies this in group settings:
    
    • In contentious meetings: “Why is this meeting so contentious? I see two teams that seem to be arguing. Can someone explain to me why this is an argument versus a constructive discussion?”
• The act of naming the tension is often the breakthrough. People are surprised you noticed, and then willing to address it.

Example: How Claire Layered a Head of Recruiting at Stripe

• Claire had a woman on the recruiting team who had never managed people but had enormous potential. Claire made her a manager. But the company needed an experienced head of recruiting.
  
  • Claire was direct with her: “I think you could be the head of recruiting in the future. I’m going to bring someone in for you to learn from. I don’t want you to see this as me layering you; I want you to see this as me giving you someone to learn from so we can keep developing you.”
• The experienced hire came in, and within two weeks told Claire the internal person could run recruiting. His job became developing her.
  
  • He was late enough in his career that he did not need to stay long. The plan was: develop her, get a couple of wins, and transition.
• The framing to the internal person was critical - she felt invested in, not displaced.

4. Onboarding Leaders

The most dangerous assumption you can make about a new senior hire from a large company is that their experience means they can figure it out. They cannot. Not because they are not smart, but because the signals that tell an experienced leader what to do next - organizational context, established processes, peer relationships, institutional memory - do not exist yet. You have to replace all of that deliberately.

New Leaders Need Context

• Your instinct will be to give a senior hire space to operate. This is wrong in the first 30 to 60 days. They need more structured check-ins, not fewer. Be more hands-on than feels natural. 
  
  • Daily standups for the first 30 days. Patrick Collison ran 15-to-30-minute daily standups with Stripe's incoming CTO for the first month. The agenda for the meeting was simply asking the leader "What did you see today?" 
    
    • The purpose of these meetings was to build shared context fast and catch playbook behavior (importing assumptions from a previous company) before it takes root.
    • These standups also have a secondary function: they signal to the new leader that you are invested in their success and that you will be present, which dramatically reduces the anxiety that typically makes new senior hires overcorrect.
  • Nip playbook behavior early and explicitly. The moment you hear a new leader say "at my last company, we did X," that is a sign they aren’t thinking from first principles in their new role.
    
    • Experienced leaders from large companies often have deep unconscious assumptions about what good looks like - org structures, meeting formats, headcount ratios, budget processes. These assumptions will leak into their decisions unless you name the problem early.
  • Give them a buddy. Assign a peer - another senior leader or a respected early employee - who the new hire can ask operational questions without feeling like they are bothering you. 
    
    • "Where do I find X? Who do I talk to about Y? Is this how we normally do Z?" These questions feel trivial but they create enormous friction if there is no clear person to absorb them.
  • Manage them. Set explicit priorities, goals, and accountability mechanisms from week one. The instinct is to let an experienced person define their own agenda. The result is usually that the first 60 days are spent on the wrong things - things that feel productive but are not actually what the company needs. Define the 90-day outcomes in writing. Review them weekly.

5. Culture & Sharing Feedback

Old Guard vs. New Guard

• As a company scales, the operating context changes faster than the team does. Early employees (“old guard”) joined in a lower-pressure, exploratory phase where ambiguity was tolerated, roles were fluid, and culture was tightly interpersonal. 
• As the company finds product-market fit and shifts toward execution, it begins hiring for a different profile - people (“new guard”) who are calibrated to speed, structure, and higher performance expectations from day one. 
  
  • Over time, differences in pace, standards, and expectations compound into a visible cultural split.

Tactic: The Subway Speech

• When the company is going through a fundamental transformation the most important thing is to actually give the speech. Name the change. Explain where the company is going and why. Give people permission to decide whether they want to be part of it.
• Charles Phillips, who led major M&A integrations at Oracle, compared the approach to a New York subway announcement: “This train will be concluding at this station. There will be no more stops. We’re changing the route. You need to get off at this station and switch trains.”
  
  • He would give a speech about the change: here is the new route, here is where we are going, and if you want to get off the train, I completely respect you.
• The key elements of the speech:
  
  • Name specifically what is changing and why
  • Describe where the company is headed
  • Acknowledge that some people will not like it
  • Give people the choice to embrace it or leave with dignity

Use Whether You’d Hire These People Today As A Litmus Test

• Claire considers this a good litmus test for cultural and people-related decisions. If the answer is no, the question becomes about timing and courage, not about whether a change needs to happen.
  
  • Tony Xu used a version of this during DoorDash’s near-death experience. Someone told him to write down the minimum number of people he needed to keep the company alive. Out of 250 people, there were only 25 names. His job became talking to those 25 and retaining them. The other 225 were secondary.
    
    • Those 25 then became the culture carriers.

Challenge the Assumption About Why the Old Guard Is Demotivated

• The default assumption is that early employees are demotivated because their friends are leaving or the culture is changing. Claire challenges this: it is equally possible they are demotivated by low performers who are still around.
• People who are struggling performance-wise are noticed by everyone. The more senior and iconic the struggling person, the bigger the blast radius on morale.
  
  • For example, say you have a strong IC who was promoted to manager because they were excellent at their individual work, burned out or struggled in the management role, was stripped of management responsibility and returned to IC - and now seems to be on a gradual exit trajectory. This pattern is almost always terminal.
    
    • When someone has been through that cycle - promoted, failed, demoted - their relationship with the company is fundamentally changed. They are no longer growing into the institution; they are growing away from it.
    • The kindest thing you can do is have a direct conversation about what they are optimizing for and whether this is still the right place for that.
    • Retaining someone in this state costs you more than their salary: it costs you team morale, their own time, and the message it sends to everyone watching about what the bar is.
• Confront the social and community aspect head-on. It is tempting to let nostalgia run, but sometimes the leader has to say clearly: we are here to build this company and this product. 
  
  • If there is something that is burning people out, address it. But the direction is non-negotiable.
• Some burnout is temporary and situational (a customer crisis, a product launch, an end-of-quarter push). Other burnout is structural - understaffed teams, unsustainable cadence, unrealistic expectations.
  
  • The leader’s job is to distinguish between the two and give people perspective. Remind them of what is a sprint versus a sustained race. Identify which teams are understaffed and fix it.

Tactic: Handing Feedback Through a Three-Way Huddle

• When you're getting valuable feedback in 1:1s but struggling to close the loop quickly, Claire suggests experimenting with an immediate three-way huddle — bringing together the person who gave the feedback and their manager as soon as possible after the conversation. 
  
  • The goal is to facilitate the direct conversation yourself: "Jim had some observations I thought would be great for you to hear, Jen." It will feel awkward, but it can be a cultural breakthrough.
• The real objective is building a culture where people have honest conversations without you in the room. 
  
  • Max Levchin did this so consistently that his skip-level 1:1s eventually became redundant, because people started having the conversations directly, knowing that's what he'd do anyway.
• The risk is that people stop sharing feedback with you if they know you'll immediately surface it. Claire's counter is that if you want a culture of direct, honest communication, this is you putting your money where your mouth is. Try it manually first, see what happens, and then figure out how to scale it.

The Leader’s Job Is To Simplify and Frame

• The most important things a leader does, beyond setting strategy and vision, are simplify and frame. When people come with issues and complexity, do not add more complexity. Drag everyone up a level: “This is where we are. This is what matters. This is what we are doing.”
  
  • Give perspective. When the culture feels fragile, provide context on why the company exists and what winning looks like. Frame the change as inevitable and worth it, and acknowledge that not everyone will love it.

Founder Communication As The Company Grows

• There are two things Claire has learned about founder communication:
  
  • First, use whatever medium is most authentic to you - if you are a strong writer, write. If you are better in person, do fireside chats. Authenticity matters more than the channel.
  • Second, employees are like consumers - no single channel satisfies everyone. Some people read every email. Some never read anything but attend all-hands. Some prefer Slack. You will never get 100% reach through one medium.
• Accept this reality and adopt a multi-channel approach. Repeat yourself. Create artifacts, documents, recordings, slides, that people can reference. Be willing to say the same thing in different formats and not feel inefficient about it.
  
  • At this stage, the founder’s voice is powerful. Keep using it. But over time, as the company grows, reserve it for the most important moments so it maintains its weight.

6. Announcing Employee Departures 

Your People Practices Should Scale

• Before setting a practice around departures, ask: what would make sense if we had 500 people? 1,000? 10,000? Use that to set the practice now, even if it feels premature. Some practices that make sense at 50 people become unworkable at 500.
  
  • Example: throwing company-wide parties for departing employees does not scale. At 100 people, it is already awkward. Individual teams can celebrate on their own, but it is not the company’s job to organize farewell events.

Let Departing Employees Own Their Goodbye

• Claire’s philosophy is to preserve ego and dignity. In the vast majority of cases let the departing person own their communication. They write their own goodbye message, send it to whomever they want, and control the narrative.
  
  • This is a philosophical and cultural decision with no single right answer. But Claire believes it makes parting ways easier when people feel they have agency over how their departure is communicated.
• In about 5–10% of cases, when a departure involves someone who was publicly problematic — a leader whose behavior was widely known to be bad — the manager sends the email. The brevity and source of the email is the signal.
  
  • The message is simple: “I want to let everyone know that [person] is leaving the company. Their last day is Friday.” The fact that it comes from the manager, not the departing person, communicates everything that needs to be communicated.
• If the company has had several departures close together, especially post-performance reviews, address it at all-hands with general framing. Acknowledge the noise, remind people that not every departure is the same, and offer to provide context without getting into individual details.

Discussing Departures At All-Hands

• At Stripe, the company started sharing a roll-up of departures: the percentage of regretted vs. non-regretted attrition. It started annually and eventually moved to quarterly. The data also appeared in board slides.
  
  • When there is noise about a specific departure, Claire recommends a standard framing: “People leave for different reasons. Some leave because we agreed it was not a good fit. Some leave because the work they want to do is not the work we are doing. Sometimes they are not performing well. We believe in preserving privacy and dignity — we do not advertise which is which.”

7. Allocating The “Fun” Work

Set Expectations in Hiring and Onboarding

• Everybody wants to work on the new shiny thing. Everybody wants to build the product. This is a fundamental tension at every company. Claire consistently sees earlier hires revert to the mean over time, saying they were told they would get to do the exciting work.
• Be explicit during hiring and onboarding about what the role actually entails. Expect some reversion from peer chatter (people hear what others are doing and want a piece of it). 
  
  • The more recent hires tend to be clearer on expectations; earlier hires often feel the shift more acutely.

Build Values That Get Used In Decisions

• A value or operating principle only works if it is actually used in operation. You cannot just put it on the wall. 
  
  • Claire cites Google’s early “Don’t Be Evil” as an example: it was a catchphrase that people actually invoked in real decisions.
    
    • When Google received one of its first government requests for personal Gmail data, the team had a heated debate about how to respond. The principle gave them a framework to work through it: What does evil mean here? What is the law? What is the minimum we are willing to do?
• Think about a value that addresses the specific tension you are contending with. Turn it into a headline you say at onboarding, repeat at all-hands, and use to remind people of the expectation. 
  
  • The content: we do not know exactly how much of this work there will be. It will be variable. Some of us will do more of it than others. That is how you build a company

 Keep the Non-Shiny Teams Motivated

• The teams that are not working on the new product know they are not the center of the universe. Recognition and acknowledgment go a long way, especially from the founder. Even 30 seconds at a monthly meeting is meaningful.
  
  • Sprinkle recognition into company goals. When a company goal hits that is specifically about what a non-central team does, call it out. Hype it up a little more than you normally would.

Tactic: The 70/20/10 Resource Allocation Framework

• Eric Schmidt used a version of this at Google: 70% of resources go to the core product (the most important thing happening), 20% go to emerging products getting traction, and 10% go to entirely new bets.
  
  • Tell the people working on the core: this is the most important thing we are doing. Do not talk about it as if it is not new. It is the foundation. But do not ever let people forget it.
    
    • Stripe used a version of this with goal categories:
      
      • Product and engineering goals (the visible, exciting work)
      • Foundation goals (security, reliability - the work that engineers who felt neglected actually cared about)
      • People and company-building goals (development, hiring, culture)
• Google kept search feeling important even while launching new products. The core team felt valued because leadership consistently reinforced that search was the company.