Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Thanks, yep, those are all legitimate concerns about whether this would scale.

It's occurred to me that Stripe's email transparency[1] could help (although they discovered limitations with that approach too, and have been good about publishing those).

We're lucky (in some ways) not to have a large inbound feedback load, which is surely also a factor. Thanks for the external-request rotation suggestion; that's a good idea to provide a refresher from focus work when the burden starts to affect the team.

Honestly though, I have to re-state that it's been so refreshing and enabling to work this way that I wonder whether there'd be ways to scale up and solve the consensus, conflict and opinion problems you mention.

Despite that, I'd add another problem to the pile: not everyone is going to be able to contribute at equal pace at all times (for various completely valid reasons) in a large enough team - and there needs to be genuine cultural understanding and acceptance of that which I believe is frequently absent from high-intensity startup environments.

[1] - https://stripe.com/blog/email-transparency



Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: