Video chat sessions that are recorded and shared with everyone. This includes things like pair programming, but also just normal conversations on topics that ar

Video chat sessions that are recorded and shared with everyone. This includes things like pair programming, but also just normal conversations on topics that are too green for any kind of formal documentation. Then as you build consensus it makes sense to start putting things in writing to reference in future discussions. When putting things in writing, put as much of this in your code as possible, and don't be afraid to repeat yourself in many places. Be deliberate about how you name things. You should choose names that align with names used across disciplines/teams in verbal communication. Cross reference things by these identifiers, even if you're not using any formal documentation generator. Rely on new employees to write high level documentation, with seniors around to answer their questions. A new hire will have the ideal perspective, and will become an expert in the process. Pay them accordingly ;) Don't worry about docs getting out of date. Again, rely on new hires to find issues with docs. Be relentless about reducing "API surface area" of your subsystems.