In this lesson we discuss how Boris scoped projects for an org that grew from about 150 to 200 people to 600 to 800. We also look at his unusual “design competition” and his tips for scoping quickly.
- When leadership gave headcount to the “communities” push, he wrote scoping docs with three technical options for each project, and in hindsight he would have put far fewer people on it, scaling up only as product-market fit appeared.
- To resolve a stuck data-model decision, he split the tech leads into two teams for three hours of whiteboarding, and the two designs ended up about 80% the same, making the path and the risks obvious.
- His scoping advice is to time-box it to 30 minutes or a couple of hours, use Claude Code to map unfamiliar systems, list the experts, and bring them a strawman design instead of asking open questions.
Original podcast link: https://www.youtube.com/watch?v=AmdLVWMdjOk