<?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>The FDE Communication Playbook</h2>
<p dir="auto">Technical skill gets you the job. Communication skill determines your success.</p>
<h3>The Weekly Client Update Email</h3>
<p dir="auto">Send this every Friday. It is the single most impactful habit for FDEs:</p>
<p dir="auto"><strong>Template:</strong></p>
<ul>
<li><strong>This week:</strong> 3-5 bullet points of what was accomplished</li>
<li><strong>Blockers:</strong> Anything you need from the client</li>
<li><strong>Next week:</strong> What you plan to work on</li>
<li><strong>Decisions needed:</strong> Any choices the client must make</li>
</ul>
<p dir="auto">Keep it under 10 lines. Executives skim.</p>
<h3>Running Client Standups</h3>
<ul>
<li><strong>Keep it to 15 minutes</strong> - Respect their time</li>
<li><strong>Lead with outcomes, not activities</strong> - "Users can now export reports" not "I refactored the export module"</li>
<li><strong>Surface blockers early</strong> - Do not wait until they become crises</li>
<li><strong>End with next steps and owners</strong> - Who does what by when</li>
</ul>
<h3>Escalation Framework</h3>
<p dir="auto">When something goes wrong (and it will):</p>
<p dir="auto"><strong>Level 1 - Informational</strong><br />
"I want to flag that X might delay Y by a few days. I have a plan to address it."</p>
<p dir="auto"><strong>Level 2 - Need input</strong><br />
"We have hit an issue with X. I see two options: A or B. I recommend A because of Z. Can we discuss?"</p>
<p dir="auto"><strong>Level 3 - Crisis</strong><br />
"X is down/blocked/failing. Here is what I know, what I have tried, and what I need from you right now."</p>
<p dir="auto">Never surprise your client or your manager with bad news they should have heard earlier.</p>
<h3>Saying No Without Saying No</h3>
<p dir="auto">FDEs get asked to do everything. Here is how to redirect:</p>
<ul>
<li>"We can absolutely do that. Let me scope it and show you where it fits in the timeline."</li>
<li>"That is a great idea. Given our current priorities, should we swap it in for X or add it to the next phase?"</li>
<li>"I can do a quick spike on that - give me 2 hours to assess feasibility before we commit."</li>
</ul>
<h3>Translating Tech to Business</h3>
<p dir="auto">The skill that separates good FDEs from great ones:</p>
<ul>
<li><strong>Bad</strong>: "We need to migrate from REST to GraphQL to reduce over-fetching"</li>
<li><strong>Good</strong>: "We can make the dashboard load 3x faster with a backend change. It will take about a week."</li>
</ul>
<p dir="auto">Always frame technical work in terms of outcomes the client cares about: speed, cost, reliability, user experience.</p>
<p dir="auto"><strong>What communication strategies have worked for you? Any templates or frameworks? Share below.</strong></p>
]]></description><link>https://fde.today/topic/32/fde-communication-playbook-emails-standups-and-escalations</link><generator>RSS for Node</generator><lastBuildDate>Sat, 25 Apr 2026 05:59:48 GMT</lastBuildDate><atom:link href="https://fde.today/topic/32.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 23 Feb 2026 22:45:55 GMT</pubDate><ttl>60</ttl></channel></rss>