The Time-Boxed First 90 Days
Build context 5x faster, leave a plan behind, and don't spend trust you haven't banked
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 93%
Zhang joined Webflow as head of product at the start of her third trimester — she had exactly 90 days before her son was born and a two-month absence. The constraint produced a compressed onboarding method: a deliberate cross-function, cross-level conversation calendar (40-50 people), a strategic plan and research assignments left in place before she went out, and public escalation of gaps to the full leadership team and board. Her own stated mistake — pushing for change before she'd banked the trust — is the framework's central warning.
Origin
Zhang's own onboarding as SVP Product at Webflow in 2020, joining while pregnant after choosing to put herself on WeWork's layoff list in place of an employee on a visa.
Core principles
- 01The single job of the first 90 days is to build context, and to build it well.
- 02Context comes from breadth across functions AND depth across levels — not just peers and direct reports.
- 03Trust is a piggy bank: you deposit before you withdraw, and change is a withdrawal.
- 04Everything is a trade-off; name what you are trading away, and know the cost.
- 05Creating awareness of a gap with the whole leadership team and board, and asking named executives to be accountable, is itself a deliverable.
How to run it
- 1
Design the conversation calendar before you start
Decide up front who you need to speak to: your direct team, the leadership team, then, for every other function, both the function's leader and someone close to the actual work. Pack the first couple of weeks with these.
Pro tip Zhang's rough shape: ~20-25 people across direct team and leadership, plus a couple of data points per function, totalling roughly 40-50 conversations.
- 2
Go down levels, not just across
Talk to the longest-tenured engineers, not only their managers. Ask what's hard about the tech stack and what's hard about their day-to-day. That's where the real constraints live.
- 3
Synthesize back-to-back
Run the conversations densely and synthesize as you go. Done back to back with active synthesis, 40-50 conversations produce a genuinely good picture of what's going on.
- 4
Deposit trust before you spend it
Treat trust as a bank balance. Build it, then use that social capital to push for change. Check how full the piggy bank is before every withdrawal.
Watch out This is where Zhang says she went wrong: 'I was pushing too hard for change' too early, driven by the time-boxed nature of her run.
- 5
Choose your trade-off consciously
Zhang traded away deep hands-on product context (Webflow is a complex product) to gain organizational and cross-functional context. That bought her a lot — and cost her trust on product fundamentals. Pick the trade knowingly.
Pro tip Without a hard time constraint, do both: go deep on the product AND run the conversation calendar.
Watch out The gap shows up later as the inability to say 'I know how this works because I've used it a bunch' — which is exactly the credibility a head of product needs.
- 6
Leave a plan, not just context
Before any absence or before the 90 days close, produce an explicit plan: what keeps executing, what doesn't make sense and stops, and what needs research — with named owners — so a real go/no-go decision is possible when you return.
Pro tip Take the gaps to the whole leadership team, all the founders, and the board — not just one founder — and ask named executives to step in and be accountable. Zhang did her board meeting the day before the checkup where she was told she was in labour.
In the wild
Having built context, Zhang concluded the company was not staffed to deliver the ambitious things it wanted to do. Rather than mention it to one founder, she communicated it explicitly to the whole leadership team, all the founders, and the board before going on leave, and asked other executives to own it.
→ The gap stayed visible and owned during her two-month absence instead of dying with her calendar.
Compressed into 90 days, Zhang pushed hard and fast for change. Because she had prioritized organizational conversations over hands-on product depth in a very complex product, she lacked the product-fundamentals credibility to back the changes she was pushing.
→ Her own stated first-90-days mistake: pushing for change before the trust was in the bank.
Common mistakes
Withdrawing trust you never deposited
Pushing for change before the organization trusts you means the change is resisted and the trust never accrues. Build the balance first.
Only meeting peers and your own team
Leadership-team and direct-report conversations give you the sanctioned story. The longest-tenured engineers give you the real one.
Is it for you?
Best for
A head of product or senior leader joining a new company, especially where the onboarding window is compressed by a hard deadline
Not ideal for
An individual-contributor PM joining a single squad, where the 40-50 conversation sweep is disproportionate and product depth should come first
From the transcript
“it's not just with your peers it's not even just with your team but to really think across all the different functions”
“so if you add that up that probably you know was like 45 40 to 50 like conversations”
“really thinking about your trust as like a bank right it's like you're putting money into your bank and then at some point you're gonna…”
“I was almost pushing too hard I was pushing too hard for change”
“getting all the Strategic pieces in place having a plan laid out and explicitly articulating in that plan keep moving these are things things that…”
From the episode
Building minimum lovable products, stories from WeWork and Airbnb, and thriving as a PM
Jiaona Zhang (Webflow, WeWork, Airbnb, Dropbox)