spakhm.com
- on day 1 start a spreadsheet with tasks, owners, and status of each task (even if there are like two rows in it at first) - pick a target date to get the core thing done - for the first two weeks, daily standup - have someone PM the standup and go through the sheet. Push everyone toward the core thing/deadline only. Relentlessly push everyone away from anything that’s not the core thing (this is very important). - these four bullets ^ are non-negotiable - after two weeks can relax standup frequency a little - that’s it, no need to make it more complicated than that. Without this everyone will always be confused and will waste weeks or months. Tons of empirical evidence for this. 35 View on X
how to run v-teams Jul 29, 2026 For v-team projects with cross-team engineers to succeed: - on day 1 start a spreadsheet with tasks, owners, and status of each task (even if there are like two rows in it at first) - pick a target date to get the core thing done - for the first two weeks, daily standup - have someone PM the standup and go through the sheet. Push everyone toward the core thing/deadline only. Relentlessly push everyone away from anything that’s not the core thing (this is very important). - these four bullets ^ are non-negotiable - after two weeks can relax standup…
saved by
related reading
- How I've run major projects | benkuhn.netbenkuhn.net
- How To Do Lessalexturek.com
- Running 1:1s for Engineersjustoffbyone.com
- How to have executive functionjeremykintana.bearblog.dev
- Notes on Managing ADHDborretti.me
- My Approach to Building Large Technical Projects – Mitchell Hashimotomitchellh.com
- How I ship projects at big tech companiesseangoedecke.com
- A Career Cold Start Algorithmboz.com
- My weekly review habit | benkuhn.netbenkuhn.net
- How Ramp builds product - by Lenny Rachitskylennysnewsletter.com
- An Expandable Explanation into Hackathon Organizinghackclub.com
- spakhm.comspakhm.com