<?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>Presentation on theplaybook</title>
    <link>https://stannomarjones.com/tags/presentation/</link>
    <description>Recent content in Presentation on theplaybook</description>
    <generator>Hugo -- 0.147.2</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 27 Mar 2025 12:18:35 -0400</lastBuildDate>
    <atom:link href="https://stannomarjones.com/tags/presentation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Present a Dashboard in 20 Minutes (Without Losing Your Audience)</title>
      <link>https://stannomarjones.com/posts/how-to-present-a-dashboard-in-less-than-20-minutes/</link>
      <pubDate>Thu, 27 Mar 2025 12:18:35 -0400</pubDate>
      <guid>https://stannomarjones.com/posts/how-to-present-a-dashboard-in-less-than-20-minutes/</guid>
      <description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;
&lt;p&gt;Most dashboards don’t fail because of bad analysis; they fail because they’re presented poorly. I’ve seen presentations where every chart was explained in detail, and the audience still walked away without a clear takeaway.&lt;/p&gt;
&lt;p&gt;I took Andy Kriebel’s Makeover Monday challenge a step further by thinking about something I don’t see discussed often: how to actually &lt;em&gt;present&lt;/em&gt; a dashboard. Especially when it’s a one-page overview, the challenge isn’t building it—it’s walking someone through it in a way that lands.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
