<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>communication on gabi cavalcante</title><link>https://gabicavalcante.dev/tags/communication/</link><description>Recent content in communication on gabi cavalcante</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://gabicavalcante.dev/tags/communication/index.xml" rel="self" type="application/rss+xml"/><item><title>Communication frameworks for being understood</title><link>https://gabicavalcante.dev/posts/communication-frameworks-for-being-understood/</link><pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate><guid>https://gabicavalcante.dev/posts/communication-frameworks-for-being-understood/</guid><description>&lt;p&gt;I lead a team, and the thing we come back to most often is not a technical problem. People know their work. What they usually do not know is how to communicate it: an idea nobody buys into, a question that does not get answered, a piece of work nobody realizes was hard, an opinion that never quite lands as an opinion, and feedback that was never given.&lt;/p&gt;</description></item></channel></rss>