Be DRY when communicating
Programmers will recognise the DRY principle from Andy Hunt and Dave Thomas’ book The Pragmatic Programmer. It stands for “don’t repeat yourself”. Simply put, you shouldn’t repeat software patterns. Avoid this redundancy using a higher level of code abstraction. In Hunt and Thomas’ words, "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system."
If you as a leader have to say the same thing several times, then you’re probably violating the DRY principle. Write it down. When you implement DRY, you can then respond with a link and protect your time for more meaningful interactions. This behaviour also lays the foundation for a handbook first culture.