But you still need to write, not necessary a speciation or tech document but all kind of notes and summaries for yourself. So that the you in two month can go back to a decision dinner two month before and reevaluate it with your new knowledge.
Also depending on the company they might give you the task of writing a less technical describing if the system for e.g. investors.
Lastly in my (little) experience asynchronous communication interleaved with small amounts of synchronous information discussions is king when it comes to the doing complex technical decisions (like which database or architecture to use for the next project).
But then I don't have too much experience in this area so take it with a grain of salt.
But you still need to write, not necessary a speciation or tech document but all kind of notes and summaries for yourself. So that the you in two month can go back to a decision dinner two month before and reevaluate it with your new knowledge.
Also depending on the company they might give you the task of writing a less technical describing if the system for e.g. investors.
Lastly in my (little) experience asynchronous communication interleaved with small amounts of synchronous information discussions is king when it comes to the doing complex technical decisions (like which database or architecture to use for the next project).
But then I don't have too much experience in this area so take it with a grain of salt.