veille et réponses aux courriels à firstname.lastname@example.org
Porteur(s) : Cédric
Juridiction : International
Statut : Adopté • 2016/01/12
A bun is born when someone asks you for something and you decide that “hey, this is a bun”. Typically through email, but sometimes a phone call or a conference mingle.
A bun always has an owner – the person who received the bun. Or more specifically, the person responsible for the communication channel through which the bun appeared. For example, you are of course responsible for any emails sent directly to you, while the office team is responsible for requests to email@example.com
When you have a bun, you are responsible for taking care of it before it gets too dry! Preferably within 1 working day, definitely within 2.
You have 3 options:
Eat it yourself. For example “Sure, I can come and do a TDD course at your company”. The bun is now consumed, i.e. it has found a home and will not be routed anywhere.
Give it to somebody else. For example to a colleague who is more suitable than you, or another company. If you don’t know exactly who should take it, email a broadcast to your colleagues or trusted partners: “Hi folks, does anybody want to take this bun?”. Note that the bun is still yours until someone else takes it! Allow a day so that your colleagues have time to react, but if that takes more than a couple of days you need to keep the bun warm (for example tell the customer that you are searching for someone who can help). So you can’t push the bun to someone, you can only offer it. The receiver has to pull the bun from you.
Throw it away. For example someone emails me “Can you come and teach a Cobol course?”. I answer “No”. Or I answer “No, we don’t do Cobol courses, but I recommend you speak to Mr CobolGeek”. That still counts as throwing away the bun, since I let it go and won’t follow it up. Someone else might take it out of my garbage, but I don’t need to know or care if that happens :o)
The one thing you should NOT do is just let the bun sit and dry. Better to explicitly throw it away in that case (i.e. tell the sender that we can’t help).
So initially a buns appears through a “push” protocol, i.e. the initial recipient gets the bun whether he wants to or not. After that, however, everything is “pull”-based.
As receiver of a bun you are responsible until it is eaten by you, taken by someone else, or thrown away. If several people are interested, sync with them.
A bun should not get more than 1-2 days old without being eaten by somebody, thrown away, or reheated (by talking to the customer/sender).
You can’t push a bun onto someone else, they have to pull. The bun is yours until someone else explicitly takes it (for example by saying “I’ll take the bun”). You can of course recommend (or even try to convince) someone else to take it from you. This goes both ways – if someone offers you a bun, you don’t have to respond if you aren’t interested.
When in doubt:
Broadcast an email to everybody or those who might be interested or involved in this bun. (dans slack idéalement)
When broadcasting to find interested bun-takers, give your colleagues one day to indicate interest in the bun. Don’t just let the first one that answers have the bun. There might be more interested. Letting the first one that answers having the bun leads to race conditions and might cause tension between colleagues.
We don’t always succeed in following these rules, especially the 1-2 day age limit. But we really try our best, and we’re at least aware of when we fail.
Bilan du nombre de messages vers firstname.lastname@example.org dans un mois et temps de réponse. Si la réponse est à l'intérieur de 48 heures nous sommes dans notre objectif.