Differences

This shows you the differences between two versions of the page.

--- vikings:communication_robustness_principle [2026/04/12 09:02] – ↷ Page moved from internal:communication_robustness_principle to vikings:communication_robustness_principle thum
+++ vikings:communication_robustness_principle [2026/04/13 07:48] (current) – [Branding] removed thum
@@ Line 12: / Line 12: @@
   * [[https://www.rfc-editor.org/rfc/rfc760|RFC 760: DoD standard Internet Protocol]]
   * [[https://en.wikipedia.org/wiki/Robustness_principle|Robustness principle]]
+guidelines.  We invite everyone, especially those associated with us, to contribute comments to help improve these guidelines.
+======= Choosing the right medium =======
+Choose the right medium for the message: use phone for urgent conversations, IRC/chat for quick coordination, and email for decisions, documentation, and external communication.
 ====== Email ======
@@ Line 40: / Line 48: @@
 You don't want your emails to have bad breath, do you?
-  * Write a clear subject line when initiating a conversation
+  * Make sure you write a clear subject line when starting a conversation.
-  * Use proper spelling and grammar
+  * Use proper spelling and grammar.
-  * Say more with less: be efficient, brief and result-oriented //without sounding like a robot//
+  * Use the local spelling of the recipient (e.g. UK vs. US, AT vs DE spelling/use of vocabulary) if this is well within your capabilities.
-  * Be polite and courteous
+  * Say more with less: be efficient, brief and results-oriented without sounding robotic.
-  * Avoid sarcasm and emotional load in written communication at all times
+  * Be polite and courteous.
-  * Avoid technical jargon unless you are having a technical conversation with someone you are sure understands it
+  * Avoid sarcasm and emotional language in written business communication. Use them only in informal exchanges with well-known colleagues, and never in external communication.
-  * Stick to the facts, when in doubt mention it clearly
+  * Avoid technical jargon unless you are in a clearly technical conversation with someone who has demonstrated knowledge of the subject.
-  * Avoid politics unless they represent the association's official position mentioned here (**TODO**).
+  * Stick to the facts, when in doubt mention it clearly.
-  * Use the local spelling of the recipient (e.g. UK vs. US or AT vs DE spelling/use of vocabulary) if this is well within your capabilities
+  * Avoid expressing personal political opinions. If the topic is relevant, refer to the association's official position.
-  * You applied proper spelling and grammar, now please proof-read again before hitting "send" :-)
+  * Before sending, proofread for spelling, grammar, and tone.
-//TL;DR: use common-sense.//
@@ Line 94: / Line 100: @@
 ====== IRC & other text-based chat systems ======
-//ToDo// FIXME
+  * Assume messages are persistent and public: Treat IRC messages like written records, not casual speech.
+  * Use threads or context: Don't drop short messages without context – make clear what you're referring to.
+  * Respect response times: IRC is not always real-time; don't expect immediate answers.
+  * Keep the same tone standards as in email: the sarcasm and jargon rules apply here too.
+  * Use the right channel: Stay on topic per channel; off-topic discussions belong elsewhere.
 ====== Phone ======
-//ToDo// FIXME
+  * Identify yourself immediately: Start the call with your name and organisation (e.g. "This is [Firstname] [Lastname] from [Association]").
+  * Ask if it's a good time: Before diving in, confirm the other person can talk.
+  * Give your full attention: No multitasking – distracted listening is more obvious on the phone than you think.
+  * Summarise at the end: Confirm what was discussed and what the next steps are.
+  * Follow up in writing: For decisions or action items, send a brief written summary after the call.
+  * Consider time zones and availability before calling.
-======= Branding =======
-//ToDo// FIXME