3 ms·
I think about (and struggle to value) point C often. The disruption can be very annoying but the knowledge transfer often has a huge multiplier attached to it
by dan_quixote 6y ago
I think about (and struggle to value) point C often. The disruption can be very annoying but the knowledge transfer often has a huge multiplier attached to it. One person's small piece of knowledge can give an entire team major traction. This model also promotes tribal knowledge and weak documentation...which is acceptable for a small company, not so much for larger companies where people are spread out across geographies.
I wonder, is this a proxy for remote teams? Will large companies have an outsized advantage in this space? Or does the lower overhead favor small companies?
- alexbanks 6y agoI think that it's just a fundamentally different way of thinking. Having a distributed team means you have to remove the "I'll just walk over and ask" mentality from everyone involved. You must resist the temptation to use slack as an alternative to in-person communication. Communication must be frequent, documented and public - someone else needs to be able to see the decisions you made.