<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>stakeholders on dfcubidesc</title><link>https://www.dfcubidesc.com/tags/stakeholders/</link><description>Recent content in stakeholders on dfcubidesc</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 05 Apr 2026 11:00:00 -0500</lastBuildDate><atom:link href="https://www.dfcubidesc.com/tags/stakeholders/index.xml" rel="self" type="application/rss+xml"/><item><title>What Stakeholders Really Want to Know — And Why Most Updates Miss It</title><link>https://www.dfcubidesc.com/posts/status-updates-what-stakeholders-want/</link><pubDate>Sun, 05 Apr 2026 11:00:00 -0500</pubDate><guid>https://www.dfcubidesc.com/posts/status-updates-what-stakeholders-want/</guid><description>What Stakeholders Really Want to Know — And Why Most Updates Miss It One format sent to everyone answers no one&amp;rsquo;s question well.
Here is a mistake I see engineering managers make constantly — and one I made myself for years.
They write one update. They send it to everyone.
Their VP gets the same message as their direct manager. Their peer team lead gets the same as their own engineers.</description></item></channel></rss>