<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Communication on Captaingolo.net</title>
    <link>https://captaingolo.net/tag/communication/</link>
    <description>Recent content in Communication on Captaingolo.net</description>
    <generator>Hugo -- 0.155.1</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 27 Oct 2024 08:00:00 +0000</lastBuildDate>
    <atom:link href="https://captaingolo.net/tag/communication/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to write messages so you are read</title>
      <link>https://captaingolo.net/blog/writing-messages/</link>
      <pubDate>Sun, 27 Oct 2024 08:00:00 +0000</pubDate>
      <guid>https://captaingolo.net/blog/writing-messages/</guid>
      <description>&lt;p&gt;You&amp;rsquo;ve probably experienced that situation where you send a message and get no response. In this article, we&amp;rsquo;ll go over several tips to help structure your messages in a way that encourages others to read and reply.&lt;/p&gt;
&lt;p&gt;There will always be people who don’t pay attention—whether because they&amp;rsquo;re juggling multiple things, you’re not their top priority, or they have attention deficits.&lt;/p&gt;
&lt;p&gt;One thing is clear: if we structure our messages so they’re easier to process, they’ll be better understood.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Offer and Receive Feedback (and Come Out Looking Good)</title>
      <link>https://captaingolo.net/blog/ideas-feedback/</link>
      <pubDate>Sun, 20 Oct 2024 08:00:00 +0000</pubDate>
      <guid>https://captaingolo.net/blog/ideas-feedback/</guid>
      <description>&lt;p&gt;Throughout the last five chapters, we’ve explored how to manage ideas from conception to overseeing implementation. One recurring theme in these articles has been that by sharing our idea, we open the door for others to offer their feedback.&lt;/p&gt;
&lt;p&gt;I’d like to end this series of articles with some advice on how to handle these contributions and criticism.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This article continues the series &lt;strong&gt;&lt;a href=&#34;https://captaingolo.net/blog/implement-ideas/&#34;&gt;How to Implement Ideas Without Killing Anyone&lt;/a&gt;&lt;/strong&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Speak Your Boss’s Language</title>
      <link>https://captaingolo.net/blog/ideas-boss-language/</link>
      <pubDate>Sun, 06 Oct 2024 08:00:00 +0000</pubDate>
      <guid>https://captaingolo.net/blog/ideas-boss-language/</guid>
      <description>&lt;p&gt;You’ve had a great idea, and after working on it and preparing it well, the moment has come where it&amp;rsquo;s ready to debut. Finally!&lt;/p&gt;
&lt;p&gt;Though it might seem counterintuitive, at this stage the most important thing is not convincing others that your idea is the best.&lt;/p&gt;
&lt;p&gt;The important thing is to &lt;strong&gt;communicate&lt;/strong&gt; three key points:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You’ve identified a problem or an opportunity.&lt;/li&gt;
&lt;li&gt;You’ve already done some groundwork considering options.&lt;/li&gt;
&lt;li&gt;You’d like to help coordinate the implementation of a solution.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;In this article, we’ll go over some tips to clearly communicate these three points.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
