Landing

First 90 Days

The offer is signed. The search is over. Now the actual work begins — and the instincts that made you effective before (clear hierarchy, mission clarity, known evaluation criteria) are largely absent. The first 90 days are disproportionately important for establishing the trajectory of everything that follows.

The research basis

Watkins (The First 90 Days, HBS Press) found that new hires who invest deliberately in onboarding reach their “breakeven point” — where they contribute more than they consume — significantly faster. The first 90 days also establish informal authority and social capital that is extremely hard to recover if mishandled early. You don't get a second first impression.

Universal Principles (All Paths)

Week 1–2

Listen more than you speak

Your instinct is to contribute immediately. Resist it. In the first two weeks, your job is to understand the system you've entered — the formal org, the informal power structure, the cultural norms. Ask more questions than you answer.

Week 3–4

Map the informal org

The org chart is a legal document, not an accurate map of how decisions are actually made. Find the people whose opinion matters on the decisions that affect your work. These are not always the people with the most senior titles.

Week 5–8

Deliver one concrete win

Identify one problem you can solve or one deliverable you can complete well. Execute it. Make sure the right people see it. Not bragging — visibility of contribution is how organizational trust is built.

Week 9–12

Establish relationships outside your team

Cross-functional relationships compound. The people in adjacent teams who see your work quality become the informal references for your next promotion. Start building them early, before you need them.

Path-Specific Landing

Investor Path

  • ›Your sourcing is being evaluated from Day 1 — even if no one says so. Start keeping a deal log immediately.
  • ›Understand the fund's existing portfolio deeply before you start proposing new investments. The partners will test you on their own companies.
  • ›Your first 90 days of source-to-meeting conversion rate will establish whether you're a strong sourcer. Prioritize this above all other work in your first month.
  • ›Build a personal CRM for your deal flow. The fund probably has one — use it. But also have your own version.

Founder Path

  • ›You are not fully 'landed' — you're building. The first 90 days post-launch are: talk to 30 customers (not pitch them — ask what's hard), stay alive (cash management), and resist premature productization.
  • ›The hardest discipline is not building features before you've validated the problem. Talk before you code.
  • ›Your team culture is set in the first 90 days whether you intend it or not. Be deliberate about the norms you establish early.

Operator Path

  • ›You are not the flight lead on Day 1. You are the new person. The instinct to assert expertise quickly is the most common first-90-days mistake for high performers.
  • ›Understand the product deeply before proposing changes to it. Every suggestion you make before you understand the product will be wrong in ways you can't anticipate.
  • ›Find your version of an 'early win' — something you can own end to end in the first 60 days that is clearly better because you were there.
  • ›Ask your manager explicitly what success looks like in 90 days. Write it down. Review it.

Enterprise Path

  • ›Understand the grade and performance review system on Day 1. It determines your promotion timeline. Your manager can explain it — ask.
  • ›Internal mobility at large corporates is real and often faster than external hiring. Identify where you want to go in 2 years and start building relationships in that direction now.
  • ›The informal hierarchy in large companies is heavily seniority-weighted. Build relationships with senior colleagues deliberately — they are your references for the next opportunity.

Watkins' Five Conversations with Your Manager

Have these five conversations with your direct manager in the first 30 days. Most new hires have one or two of them accidentally. Having all five intentionally dramatically reduces ambiguity about what success looks like.

Situation

“What does the organization most need from me right now? What are the most critical problems I need to understand?”

Expectations

“What does success look like at 30, 60, and 90 days? What would make you say this hire was excellent?”

Resources

“What do I have access to — budget, team, tools? Where will I face resource constraints?”

Style

“How do you prefer to communicate — written or verbal? Frequent check-ins or autonomous operation? How do you like to receive bad news?”

Development

“What are the one or two things I should focus on developing in this role? Are there things I should be doing differently?”