<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[FDE Communication Playbook - Emails Standups and Escalations]]></title><description><![CDATA[<h2>Communication Determines FDE Success</h2>
<h3>Weekly Client Update (Every Friday)</h3>
<ul>
<li><strong>This week:</strong> 3-5 bullets of accomplishments</li>
<li><strong>Blockers:</strong> What you need from the client</li>
<li><strong>Next week:</strong> Planned work</li>
<li><strong>Decisions needed:</strong> Choices they must make</li>
</ul>
<p dir="auto">Keep it under 10 lines.</p>
<h3>Client Standups</h3>
<ul>
<li>15 minutes max</li>
<li>Lead with outcomes not activities</li>
<li>Surface blockers early</li>
<li>End with owners and deadlines</li>
</ul>
<h3>Escalation Framework</h3>
<p dir="auto"><strong>Level 1:</strong> I want to flag X might delay Y. I have a plan.<br />
<strong>Level 2:</strong> We hit an issue. Two options. I recommend A.<br />
<strong>Level 3:</strong> X is down. Here is what I know and need.</p>
<h3>Saying No</h3>
<ul>
<li>We can do that. Let me scope where it fits in the timeline.</li>
<li>Great idea. Should we swap it for X or add to next phase?</li>
</ul>
<h3>Tech to Business Translation</h3>
<ul>
<li>Bad: Migrate REST to GraphQL to reduce over-fetching</li>
<li>Good: Dashboard loads 3x faster with a backend change. One week.</li>
</ul>
<p dir="auto"><strong>What communication strategies work for you?</strong></p>
]]></description><link>https://fde.today/topic/20/fde-communication-playbook-emails-standups-and-escalations</link><generator>RSS for Node</generator><lastBuildDate>Sat, 25 Apr 2026 04:22:18 GMT</lastBuildDate><atom:link href="https://fde.today/topic/20.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 23 Feb 2026 22:44:14 GMT</pubDate><ttl>60</ttl></channel></rss>