The U-Curve of Founder Involvement
Involve a product-minded founder heavily at the start and end of a project, but give the team space to run in the middle.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- 86%
When you report to a strongly product-minded founder-CEO, the failure mode is either the founder micromanaging every decision or the team disappearing and shipping something the founder rejects at the last minute. Weiss maps involvement over time as a U: high founder engagement early (strategic buy-in, goals and anti-goals), low in the middle (team explores freely), then high again at the end (the founder 'tastes the soup'). This gives teams creative agency while keeping the maniacally customer-focused founder co-invested in the outcome.
Origin
Developed by Noah Weiss from working directly with strongly product-minded founders Stewart Butterfield (Slack) and Dennis Crowley (Foursquare).
Core principles
- 01Align on the principles of what a great product looks like so reviews use shared language, not Goldilocks 'not quite right' feedback
- 02The founder always holds the company vision; individual teams own the creative exploration within it
- 03Refine in real working code at the end, not static design mocks, because using software feels different from looking at it
- 04Skipping the final co-creation step makes the post-launch period far more painful with a customer-obsessed founder
How to run it
- 1
Get strategic buy-in early
For any big new project, bring the founder in at the start to agree on the approach, the goals, and the anti-goals so they are strategically bought in.
Pro tip Nail down the anti-goals explicitly, not just the goals — knowing what you will NOT build is what lets the team run safely.
- 2
Give the team space to explore
Once alignment on vision and principles exists, pull the founder back and let the team do creative exploration and prototyping without constant check-ins.
Watch out This only works if step 1 produced genuine alignment on principles; without it, the middle becomes drift and the end becomes a rejection.
- 3
Bring the founder back to taste the soup
Near launch, get the whole team plus the founder into a room to do a collective bug-bash on the real software, doing the rapid refinement and polish together.
Pro tip Frame it as a group raising the craft bar together ('here's the gap to the bar our users deserve'), not the team wanting to ship versus the founder blocking.
Watch out Do this in working code. Reviewing static mocks hides the polish and flow problems that only surface when the software is actually used.
In the wild
For a launch, Slack would get the entire development team — engineers, design, product, user research — plus Stewart into a room and do a bug bash together, treating messy software-making as a mess everyone cleans up collectively. Sometimes they'd find a broken entry point needing a bigger change, but mostly it was the bits of polish and delight that raise the craft bar.
→ Refinement happened as collective co-creation rather than a team-versus-founder standoff, making the last mile the most rapid-refinement stage rather than the most painful.
Common mistakes
Treating the founder's function as a place to grab agency
Weiss warns that when the CEO's expertise overlaps your role, you'll feel you have less agency — fighting that instead of learning from a world-class operator wastes the highest-learning relationship you'll have.
Reviewing static mocks instead of live software
Because using software is so different from looking at it, refining on mocks means the founder's real reaction — and the missing polish — only appears after launch, when it's most expensive to fix.
Is it for you?
Best for
A first or early PM at a startup reporting to a strong, product-minded founder-CEO who wants heavy involvement.
Not ideal for
Companies whose CEO is not deeply product-involved, or low-stakes incremental features that don't warrant founder time at all.
From the transcript
“almost like a u curve where the x-axis is time and the y-axis's level of involvement I think you want to get the founders yo…”
“at the very end you want them to really be bought in that did you build something that's up to the Quality broader company is…”
“if you can get that alignment and you can get those principles as the common language of what create software looks like I think you…”
From the episode
The 10 traits of great PMs, how AI will impact your product, and Slack’s product development process
Noah Weiss (Slack, Foursquare, Google)