Maybe this is not the place to ask. Please point me to the correct site if that's the case.
This happens often: I have a slack conversation with my manager and my PM, and at the end of the conversation I like to do a summary. Example:
OK for release on 20 we need to:
- write script to handle (common name for feature X)
- write script to handle (common name for feature Y)
Is everyone OK with this ?
Both my manager and the PM acknowledge this summary. After 5 minutes, in the same slack channel my manager starts discussing with the PM:
PM, we need to manually handle (another common name for feature Y). Can the support team manually change the data?
Both (common name for feature Y) and (another common name for feature Y) are used interchangeable both by me and them so that shouldn't be an issue.
How do I ensure that they don't just skim over the summary but actually read and understand what I've written?
(Bear in mind that one of them is my superior and he was extremely annoyed when I pointed out that we just discussed that and there is no need for manually handling it.)
Edit: The example above has people looking in the wrong direction, so I will give another that just happen.
End of May we had a consolidation release, in which my team did some cleanup and several optimizations. One of the changes involved consolidating 3 microservices into a single one (they were practically identical with only a few lines of code difference - very hard to maintain the common code). The change was presented every where, several emails and slack conversations.
Apparently that wasn't enough, yesterday the PM saw that those old micro services were not running and started them up, creating a world of trouble. All of them had a comment stating "backup, do not start" visible in the cloud interface used start them up.