Every activity in the inception journey has the potential to be at least partly asynchronous. To be pragmatic about how much synchrony you need, you must recognise inceptions as a process and not an event.

Technical design docs are an efficient way to communicate about software architecture and technical solutions. These docs precede an architectural decision record. They benefit from detail, though brevity is an important consideration too.

Feature breakdown documents serve as a single resource to catalogue all information about a feature. As the team enhances the feature, this document becomes a single source of truth about it.

Idea papers allow you to nurture fresh ideas by articulating them clearly. People can use this as a reference to share feedback and enrich the idea. Decision making is also easier if everyone can understand the idea well.