As a senior-level IC, I find it challenging to determine the appropriate amount of context to include in my reports. When communicating upwards, I tend to write in a concise, bullet-point style to provide information. However, when communicating with peers or subordinates, I prioritize providing more detailed context to better facilitate understanding.
I often received feedback that my reports were too long, causing colleagues to skip them. However, if they were too short, my documents were flooded with comments asking for more context.
I’ve begun writing TLDRs at the beginning of my reports and create slide decks to provide the complete story in a shorter and more reader-friendly format.
It’s been more work for me, but it allows my colleagues, up and down, to receive my message in a format that best suits them and their situation.
Very helpful!
As a senior-level IC, I find it challenging to determine the appropriate amount of context to include in my reports. When communicating upwards, I tend to write in a concise, bullet-point style to provide information. However, when communicating with peers or subordinates, I prioritize providing more detailed context to better facilitate understanding.
I often received feedback that my reports were too long, causing colleagues to skip them. However, if they were too short, my documents were flooded with comments asking for more context.
I’ve begun writing TLDRs at the beginning of my reports and create slide decks to provide the complete story in a shorter and more reader-friendly format.
It’s been more work for me, but it allows my colleagues, up and down, to receive my message in a format that best suits them and their situation.