LLenny's Podcast
← All frameworks
Leadership

First PM Readiness and Insider Rule

Hire a PM only when a real coordination gap exists, then start with a trusted insider

Difficulty
Advanced
Time to result
~months to results
Steps
5
Confidence
97%

The First PM Readiness and Insider Rule begins with a gap, not a headcount milestone. Ask whether the product team can take a customer problem, propose alternatives, prioritize them, execute, and test the result. Then ask whether the founder still has enough time to supply problems, customer context, sequencing, and feedback to roughly five to ten engineers. If the system works, wait. If the expensive engineering team is under-supported, appoint a full-time PM. Rajaram's preferred first hire is an existing engineer, analyst, or designer trusted by both founders and engineers. Select for curiosity, customer centricity, communication, facilitation, and problem solving, then use mentoring and customer contact to help the person shed the habits of their previous function.

Origin

Rajaram observed that the first PM at every company where he had worked moved internally from engineering, design, or analytics. Lenny confirmed Airbnb's first PM had joined as an engineer, reinforcing the pattern.

Core principles

  • 01Hire to solve a current problem rather than an anticipated organizational fashion
  • 02Someone must perform product management, but that person need not carry the title
  • 03Trust with founders and engineers matters more than polished external process for the first PM
  • 04Customer curiosity and facilitation ability are stronger transition signals than prior function

How to run it

  1. 1

    Audit the current product system

    Test whether the team can receive a problem, generate options, choose by expected return, execute, and validate the result. If it can, a PM title may add little.

    Pro tip Review one recent project from problem statement through measured outcome.

    Watch out Do not infer a PM need from engineer count alone.

  2. 2

    Measure founder bandwidth

    Ask whether the founder can still talk to customers, frame problems, sequence work, and facilitate decisions for the engineering team. A persistent gap is evidence for a full-time PM.

    Pro tip Look at the founder's calendar and missed decisions rather than relying on intention.

  3. 3

    Search trusted insiders first

    Consider engineers, designers, and analysts who already understand the product and have trust on both sides. The first PM often acts as a bridge between founders and engineering.

    Pro tip Functional polish can be coached more easily than organizational trust can be imported.

    Watch out Do not select a random insider merely because they are available.

  4. 4

    Select for PM traits

    Evaluate curiosity, customer centricity, communication, facilitation, and problem solving. Confirm that the candidate wants to own problems rather than remain in the comfort zone of their former craft.

    Watch out A newly transitioned engineer or designer may keep dictating how the product should be built.

  5. 5

    Coach through the transition

    Pair the new PM with mentors and push them toward customers. Keep speaking with engineers and designers to learn whether the PM is adding value.

    Pro tip Use direct engineering-manager feedback as an early signal.

    Watch out Hiring a PM does not let the founder abdicate responsibility for team health.

In the wild

Airbnb's engineer-to-PM transition

When Rajaram asked whether Airbnb fit his pattern, Lenny confirmed that its first PM had joined as an engineer. The internal move preserved product and cultural context while introducing formal product ownership.

→ The example supported the insider-first rule for a startup's earliest PM appointment.

A team that can still wait

Rajaram described a team that can take an acquisition problem, produce several solutions, select the best return, execute, and test whether acquisition improved. Even without a titled PM, that team is already performing the function effectively.

→ The company avoids premature hiring while the existing system remains empowered and effective.

Common mistakes

Hiring for a future problem

Premature hiring makes the company larger before a real gap exists and can introduce unnecessary process.

Importing a foreign operating system

An external first PM with a completely different process may be rejected by founders and engineers before proving value.

Retreating into the old craft

A converted engineer or designer may over-focus on implementation instead of customers, problems, and facilitation.

Is it for you?

Best for

Startups approaching five to ten engineers where the founder may no longer have enough bandwidth to perform the PM role.

Not ideal for

Developer-facing teams whose engineers already understand users, prioritize problems, and validate solutions effectively.

From the episode

Gokul Rajaram on designing your product development process, when and how to hire your first PM, a playbook for hiring leaders, getting ahead in you career, how to get started angel investing, more

→