The Facilitator-First Ramp for Product Leaders Under a Product Founder
Joining a founder with strong product sense? Spend your first months translating, not deciding.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 88%
When a head of product joins a company whose founder has been the de facto product mind for years, the instinct to start making decisions destroys trust. Monga's approach was to act as a facilitator rather than a decision maker: close the information gap in both directions until the founder knows what every team is doing and every team can model the founder's vision themselves. Decision rights are then earned through accumulated reps, not claimed on arrival.
Origin
Sachin Monga's account of his first year as Head of Product at Substack under co-founder and CEO Chris Best, who had been carrying the product vision for five-plus years.
Core principles
- 01You are years behind the founder on this problem — assume it and go catch up.
- 02The scaling failure mode is not disagreement, it is that the founder no longer knows what teams are doing and teams no longer know what the founder wants.
- 03The goal is not to relay the founder's decisions but to make the teams able to model the founder's vision without him in the room.
- 04Trust is built by reps, not by mandate.
- 05New perspectives from other companies only earn a hearing after the founder's original reasoning is understood.
How to run it
- 1
Diagnose the moment the weekly room stopped working
Identify the scaling break: the point where the company outgrew the single weekly meeting in which the founder could be present and decide what happens next. That break, not disagreement, is the actual problem you were hired into.
Watch out Hiring is usually accelerating at exactly this moment, adding people who never sat in the room and have none of the accumulated context.
- 2
Define your first-months job as facilitation only
For the first couple of months, aim at one outcome: the founder has a genuinely good sense of what every team is doing, and every team understands where the founder is coming from. Nothing else.
Pro tip Say this out loud to the founder. Explicitly deferring decision rights early is what makes them transferable later.
- 3
Go archaeological on the founder's vision
Deliberately catch up the years you are behind. Substack pulled up the 60-second Y Combinator demo day pitch from ~2017 at an all-hands and found the company was now shipping exactly what the founder had described years earlier — podcasting, network effects between writers.
Pro tip Old pitch decks, demo day videos and early writing are the cheapest way to reconstruct the founder's original reasoning. Watch them with the whole team, not alone.
- 4
Install a weekly open-communication cadence
Sit down with the founder for an hour at the start of the week on what the big problems and worries are, and check in again at the end of the week. Keep the loop tight and continuous rather than gated on planning cycles.
- 5
Let teams build their own model of the founder
Success is teams that can predict what the founder would want without asking. At that point you stop being a relay and can start layering in outside perspective and data-driven arguments.
Pro tip Bringing people from other companies is valuable — but their perspective lands only once they can articulate the founder's original reasoning first.
Watch out If you start overriding the founder before the teams can model him, every disagreement becomes a referendum on your authority.
In the wild
When Monga joined, Substack had just outgrown the single weekly meeting where CEO Chris Best could see everything and decide the next two weeks of work. Suddenly Chris did not know what all the teams were doing and the teams did not know what Chris had in mind — while the company was hiring fast. Monga made closing that two-way gap his entire job for his first couple of months.
→ After reps on both sides, trust formed; Monga and Best now run a start-of-week hour on the big problems and worries and an end-of-week check-in, with teams able to model the founder's vision independently.
At an all-hands, Substack replayed Chris Best's 60-second Y Combinator demo day pitch from roughly six years earlier, in which he described podcasting and a writer-to-writer network effect. The company was, at that moment, actually building those things.
→ The team collectively caught up on the founder's original vision and understood the order of operations — that Substack had to earn its place at the table before it could do the things in the pitch.
Common mistakes
Arriving as the decision maker
A head of product who claims product authority on day one at a founder-led company is competing with someone who has been thinking about the problem five times longer. Facilitation first is not deference — it is how the reps that earn decision rights get accumulated.
Applying outside playbooks before understanding the vision
Experience from other companies is genuinely useful, but deployed before the founder's reasoning is understood it reads as a rejection of the vision rather than a contribution to it.
Is it for you?
Best for
A first head of product or first PM joining a small, fast-growing company whose founder has strong, long-held product convictions.
Not ideal for
Turnaround situations or companies where the founder has explicitly stepped back from product and the mandate is to replace their judgment.
From the transcript
“I think the first thing was really treating my role in the beginning more as a facilitator than a decision maker when it comes to…”
“if Chris could have a really good sense of what all the teams are doing and if the teams knew where he was coming from…”
“Chris has been thinking about this problem for me five times as long as I have.”
“We start the week Chris and I we sit down for an hour we go through what we feel like are the big problems to…”
From the episode
Building Substack
Sachin Monga (Substack, Facebook)