3 ms·
I'm the 'engineer' side of the equation. But often I need async interaction with various others. So I just combine it all in one message: Hey, Jo! I just have
by jagged-chisel 5y ago
I'm the 'engineer' side of the equation. But often I need async interaction with various others. So I just combine it all in one message:
Hey, Jo! I just have a quick question for when you have a moment: <question for Jo>
And leave it. I'll ping Jo again at a time interval depending on urgency - sometime this sprint? I'll remind about the message in a couple days. Need it today? I indicate that when I ask, and about 4hrs later I'll poke a bit to see where we are.
- mkr-hn 5y agoThis is 100% it. Expectation setting is the missing key in a lot of these conversations. Asking to ask is about not being rude. There are better ways to do this in an asynchronous conversation. It's right up there with "we need to talk" in texts. The anxiety it causes is completely unnecessary, and easily avoided with a little detail and priority. There are countless socially defined, implicit hammers looking for nails. Most can be improved upon or swapped out for different tools.
- atuladhar 5y ago+1 to this. That example message is very close to how I phrase questions in chats as well.
- JoeAltmaier 5y agoThis is my pet peeve. You don't have a quick question. If you did, you'd just ask it. By asking to ask, you've doubled my required response effort. Please just ask questions. Pinging someone about a mysterious question that you'll reveal later is annoying. It certainly doesn't go on my list of things to do re: "Sometime later this sprint be sure to get back to that person who won't tell me what they want from me". It goes on the list "Ignore this person"
- bluefirebrand 5y agoI read GP's comment as saying "Hey I have a quick question for you: INSERT QUESTION HERE", so it sounds like you are in agreement actually.