One Message Per Message
Which of your four questions will they answer?
The idea
When a message carries several asks, the reader answers the easiest and the rest are lost.
In the real world
An email with four questions comes back with a reply to the second.
Going deeper
Requests bundled into one message compete with each other, and the reader's sense of having responded is satisfied by completing the cheapest one.
An email asking for a budget approval, a date, a document review and an introduction reliably comes back with the introduction done. A reply was sent, the thread reads as handled, and the expensive asks are now buried in a message marked as answered. Splitting them into separate messages with separate subjects costs thirty seconds and removes the competition entirely.
Where it stops applying
Fragmenting genuinely related items across many messages is its own burden and can look disorganised. The rule applies to independent asks, not to one request with supporting detail.
Why it matters
It explains why things you definitely raised are treated as though you never mentioned them.
Try this today
Split your next multi-ask email into separate messages with separate subjects.
Test yourself
An email asks for a budget approval, a date confirmation, a document review and an introduction. Only the introduction is done. Why?
Show the answer
It was the cheapest, and a reply had been sent, so the thread reads as handled. Bundled requests compete with each other, and the reader's sense of having responded is satisfied by the smallest one.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.