<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BI Tools &#8211; Sarah Schlott</title>
	<atom:link href="https://sarahgschlott.com/tag/bi-tools/feed/" rel="self" type="application/rss+xml" />
	<link>https://sarahgschlott.com</link>
	<description>FP&#38;A Insights</description>
	<lastBuildDate>Thu, 14 Aug 2025 04:47:52 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://sarahgschlott.com/wp-content/uploads/2025/05/cropped-ChatGPT-Image-May-13-2025-07_00_01-PM-1-1-1-32x32.png</url>
	<title>BI Tools &#8211; Sarah Schlott</title>
	<link>https://sarahgschlott.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Excel Is Dead: FP&#038;A Team Now Builds Models in PowerPoint</title>
		<link>https://sarahgschlott.com/excel-is-dead-fpa-team-now-builds-models-in-powerpoint/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=excel-is-dead-fpa-team-now-builds-models-in-powerpoint</link>
		
		<dc:creator><![CDATA[Sarah Schlott]]></dc:creator>
		<pubDate>Thu, 05 Jun 2025 03:45:22 +0000</pubDate>
				<category><![CDATA[Excel]]></category>
		<category><![CDATA[BI Tools]]></category>
		<category><![CDATA[Decision-making]]></category>
		<category><![CDATA[Finance Leadership]]></category>
		<category><![CDATA[Forecasting]]></category>
		<category><![CDATA[FP&A team]]></category>
		<category><![CDATA[Modeling]]></category>
		<category><![CDATA[Modernization]]></category>
		<category><![CDATA[PowerPoint]]></category>
		<category><![CDATA[Scenario modeling]]></category>
		<guid isPermaLink="false">https://sarahgschlott.com/?p=4637</guid>

					<description><![CDATA[It started, as most modern corporate absurdities do, with a single sentence in a leadership Slack thread: &#8220;Do we really need Excel for this?&#8221; Cue the floodgates. Someone (from Marketing, naturally) posted a Medium think piece on how &#8220;spreadsheets are a relic of the past.&#8221; Someone else chimed in about their nephew using Notion for [&#8230;]]]></description>
										<content:encoded><![CDATA[<p data-pm-slice="1 1 []">It started, as most modern corporate absurdities do, with a single sentence in a leadership Slack thread: &#8220;Do we really need <a href="https://sarahgschlott.com/top-10-principles-for-transforming-fpa-towards-long-term-value-creation/">Excel</a> for this?&#8221;</p>
<p>Cue the floodgates.</p>
<p>Someone (from Marketing, naturally) posted a Medium think piece on how &#8220;spreadsheets are a relic of the past.&#8221; Someone else chimed in about their nephew using Notion for budgets. The COO asked if Tableau could just &#8220;handle the modeling.&#8221;</p>
<p>By the end of the week, the company’s FP&amp;A team was politely asked to &#8220;explore modernizing their toolset.&#8221;</p>
<p>The punchline? Within three weeks, the team was building their models—<em>in <a href="https://sarahgschlott.com/top-10-principles-for-transforming-fpa-towards-long-term-value-creation/">PowerPoint</a></em>.</p>
<p>And as ridiculous as that sounds, the story holds a mirror up to what I see happening across a lot of <a href="https://sarahgschlott.com/mastering-ai-in-finance-building-expertise-for-a-data-driven-future/">finance</a> teams today.</p>
<p>So let’s break it down.</p>
<h2>The Setup: Death by a Thousand &#8220;Modernization&#8221; Initiatives</h2>
<p>The company? A well-funded Series D SaaS unicorn.</p>
<p>The FP&amp;A team? Smart. Experienced. Strong modeling chops.</p>
<p>The problem? Leadership had developed a collective allergy to anything that looked “old school.&#8221;</p>
<p>It started innocently enough:</p>
<ul data-spread="false">
<li>The CFO wanted more &#8220;visually engaging&#8221; outputs for board decks.</li>
<li>The CRO complained that Excel models &#8220;weren’t collaborative enough.&#8221;</li>
<li>The CEO’s chief of staff suggested that &#8220;modern finance teams use dynamic dashboards.&#8221;</li>
</ul>
<p>Pretty soon, Excel was on life support.</p>
<h2>The Shift: From Models to Slides</h2>
<p>Here’s how it actually played out:</p>
<table>
<tbody>
<tr>
<th>Stage</th>
<th>What Happened</th>
</tr>
<tr>
<td>&#8220;Modernization&#8221; kickoff</td>
<td>FP&amp;A told to explore tools</td>
</tr>
<tr>
<td>Tool evaluation</td>
<td>BI tools couldn’t handle modeling complexity</td>
</tr>
<tr>
<td>Quick workaround</td>
<td>Started building simplified <a href="https://sarahgschlott.com/the-5-most-common-mistakes-i-see-in-financial-models-and-how-to-fix-them/">assumptions</a> in PowerPoint tables</td>
</tr>
<tr>
<td>Full collapse</td>
<td>Finance leadership started requesting &#8220;final&#8221; models directly in slide format</td>
</tr>
</tbody>
</table>
<p>By month three? Entire operating models were being built in <em>PowerPoint tables</em>. Yes, with manual calculations. Yes, copy-pasted. Yes, with version control managed via email chains.</p>
<p>And yes, it was a disaster.</p>
<h2>The Warning Signs: How to Know You’re on This Path</h2>
<p>I’ve seen this happen more than once. Here are the telltale signs:</p>
<h3>1. Leadership starts optimizing for presentation over accuracy</h3>
<p>When the primary feedback on your <a href="https://sarahgschlott.com/how-to-make-your-fpa-function-a-strategic-partner-not-a-reporting-machine/">model</a> is &#8220;Can we make this chart more on-brand?&#8221;</p>
<h3>2. Decision-makers stop engaging with model drivers</h3>
<p>If you hear &#8220;Just show me the summary slide,&#8221; you’re already in the danger zone.</p>
<h3>3. BI tools are treated as replacements for modeling</h3>
<p>Dashboards are great. But they’re not <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">scenario</a> engines.</p>
<h3>4. Finance gets pushed to deliver in &#8220;collaborative formats&#8221;</h3>
<p>Translation: Formats that are easy to screenshot, not formats that are built for <a href="https://sarahgschlott.com/how-to-make-your-fpa-function-a-strategic-partner-not-a-reporting-machine/">decision-making</a>.</p>
<h3>5. Operators start bypassing Finance for modeling</h3>
<p>Because the Finance outputs are now too sanitized to be useful.</p>
<h2>Why This Happens: The Seduction of the Pretty Deck</h2>
<p>The truth? A gorgeous slide deck is seductive. It makes the numbers feel polished. Digestible. Safe.</p>
<p>But the second you lose visibility into what’s driving those numbers, you’re flying blind.</p>
<p>As one FP&amp;A lead put it to me: &#8220;We went from pilots to flight attendants. Smiling, serving up pre-packaged metrics, but not flying the plane anymore.&#8221;</p>
<h2>What’s Lost: The Real Cost of Killing Excel</h2>
<p>Here’s what the company actually lost in this shift:</p>
<table>
<tbody>
<tr>
<td>Capability</td>
<td>Lost Outcome</td>
</tr>
<tr>
<td>Dynamic scenario modeling</td>
<td>No fast pivoting on new assumptions</td>
</tr>
<tr>
<td>Driver-based <a href="https://sarahgschlott.com/the-hidden-edge-why-growing-companies-need-fpa-before-they-think-they-do/">forecasting</a></td>
<td>Static, high-level projections</td>
</tr>
<tr>
<td>Sensitivity analysis</td>
<td>Gut-feel decision-making</td>
</tr>
<tr>
<td>Version control with audit trail</td>
<td>Conflicting slide decks</td>
</tr>
<tr>
<td>Operator engagement in modeling</td>
<td><a href="https://sarahgschlott.com/how-to-make-your-fpa-function-a-strategic-partner-not-a-reporting-machine/">Operators</a> building their own side models</td>
</tr>
</tbody>
</table>
<p>In short? Finance ceded its seat at the strategy table.</p>
<h2>The Underlying Issue: Misunderstanding What Modeling Is <em>For</em></h2>
<p>Too many leadership teams think modeling is about producing a pretty number.</p>
<p>It’s not. It’s about:</p>
<ul data-spread="false">
<li>Testing assumptions</li>
<li>Understanding sensitivities</li>
<li>Driving tradeoff decisions</li>
<li>Preparing for uncertainty</li>
</ul>
<p>And guess what? You can’t do that in PowerPoint.</p>
<h2>A Better Way: Modernize <em>How</em> You Use Excel, Not <em>Whether</em></h2>
<p>I’m not anti-modernization. I teach teams how to do this the right way.</p>
<p>Here’s how:</p>
<h3>1. Clean up your models</h3>
<ul data-spread="false">
<li>Use Power Query to automate <a href="https://sarahgschlott.com/mastering-ai-in-finance-building-expertise-for-a-data-driven-future/">data</a> pulls</li>
<li>Structure models for transparency and flexibility</li>
<li>Build scenario engines, not static forecasts</li>
</ul>
<h3>2. Separate calculation layer from presentation layer</h3>
<ul data-spread="false">
<li>Do the modeling in Excel (or your modeling tool of choice)</li>
<li>Drive the outputs into dashboards or board decks</li>
</ul>
<h3>3. Train leadership on how to engage with models</h3>
<ul data-spread="false">
<li>Teach them to ask: &#8220;What’s driving this? What are the assumptions? What’s the sensitivity?&#8221;</li>
</ul>
<h3>4. Protect core modeling time</h3>
<ul data-spread="false">
<li>Don’t let Finance become a slide factory</li>
<li>Guard time for actual analysis and decision prep</li>
</ul>
<h2>Why This Matters: In Uncertainty, Speed of Insight Wins</h2>
<p>Here’s the punchline:</p>
<p>The company I’m talking about? When the market turned six months later, they were caught flat-footed.</p>
<p>They couldn’t run new scenarios fast enough. They didn’t know which levers to pull. Operators stopped trusting the Finance numbers.</p>
<p>Eventually? They quietly rebuilt the Excel models. But by then, the credibility damage was done.</p>
<h2>Don’t Throw Out the Toolbox</h2>
<p>This article took real time to write because I want more CFOs and operators to see through the &#8220;modernization theater&#8221; that’s infecting too many Finance teams.</p>
<p>If you found value in it, please share.</p>
<p>And if you want to go deeper—whether it’s modernizing your modeling stack, building faster scenario engines, or up-leveling your team’s strategic impact—I offer 1:1 consulting for Finance pros ready to level up. DM me if you want to talk.</p>
<p>And I’ll leave you with this question:</p>
<p><strong>If your board asked for three new downside scenarios today—could your team deliver by end of week?</strong></p>
<p>If that makes you sweat—it’s time to fix it.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why Smart Finance Teams Build Dashboards in Excel First: 4 Tactical Wins</title>
		<link>https://sarahgschlott.com/why-smart-finance-teams-build-dashboards-in-excel-first-4-tactical-wins/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=why-smart-finance-teams-build-dashboards-in-excel-first-4-tactical-wins</link>
		
		<dc:creator><![CDATA[Sarah Schlott]]></dc:creator>
		<pubDate>Tue, 27 May 2025 01:57:55 +0000</pubDate>
				<category><![CDATA[Excel]]></category>
		<category><![CDATA[FP&A]]></category>
		<category><![CDATA[Assumptions]]></category>
		<category><![CDATA[BI Tools]]></category>
		<category><![CDATA[Dashboard]]></category>
		<category><![CDATA[Data]]></category>
		<category><![CDATA[Decisions]]></category>
		<category><![CDATA[Finance]]></category>
		<category><![CDATA[Flexibility]]></category>
		<category><![CDATA[Inputs]]></category>
		<category><![CDATA[Logic]]></category>
		<guid isPermaLink="false">https://sarahgschlott.com/?p=4590</guid>

					<description><![CDATA[I’ve seen more dashboards die in the wild than PowerPoint decks in an abandoned investor folder. You know the type—some over-engineered, visually stunning, SaaS-powered monstrosity that looks great until someone asks for a new metric and you realize no one on the team knows how it was built. Or worse: the original architect left the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p data-pm-slice="1 1 []">I’ve seen more dashboards die in the wild than <a href="https://sarahgschlott.com/top-10-principles-for-transforming-fpa-towards-long-term-value-creation/">PowerPoint</a> decks in an abandoned investor folder. You know the type—some over-engineered, visually stunning, SaaS-powered monstrosity that looks great until someone asks for a new metric and you realize no one on the team knows how it was built. Or worse: the original architect left the company, and now it&#8217;s just sitting there, a $40K-a-year tombstone.</p>
<p>Here’s the part nobody wants to say out loud: if your dashboard can’t be broken down, rebuilt, and questioned in real time, it’s not a decision-making tool. It’s a slide.</p>
<p>And that’s why smart <a href="https://sarahgschlott.com/mastering-ai-in-finance-building-expertise-for-a-data-driven-future/">finance</a> teams start in <a href="https://sarahgschlott.com/top-10-principles-for-transforming-fpa-towards-long-term-value-creation/">Excel</a>.</p>
<p>Not because Excel is perfect—it isn’t. But because Excel is flexible, auditable, accessible, and brutally honest. The moment a number is wrong, it’s staring you in the face. No animations. No filters hiding the rot. Just you, the logic, and the truth.</p>
<p>Here are four tactical reasons why building your dashboards in Excel first isn’t just a good idea—it’s essential.</p>
<h2>1. Excel Forces You to Know Your Inputs</h2>
<p>Most dashboards are built backwards. People start with what they want to see—ARR, CAC, burn multiples, runway—and then go hunt down <a href="https://sarahgschlott.com/mastering-ai-in-finance-building-expertise-for-a-data-driven-future/">data</a> to make the visuals work. It’s upside-down logic.</p>
<p>In Excel, you start with raw data. Not cleaned. Not summarized. Just ugly CSVs that reflect the actual messiness of your systems. And in building your dashboard from that mess, you’re forced to:</p>
<ul data-spread="false">
<li>Map the data lineage—where it came from, what it means</li>
<li>Build intermediate calculations you can actually trace</li>
<li>Audit <a href="https://sarahgschlott.com/the-5-most-common-mistakes-i-see-in-financial-models-and-how-to-fix-them/">assumptions</a> on the spot (before they become permanent)</li>
</ul>
<p>By the time the dashboard is done, it’s not just pretty—it’s <em>yours</em>. You understand how every number got there because you fought for it. That’s not a dashboard. That’s institutional memory.</p>
<p><strong>Let me give you a real one:</strong> At a previous company, we rolled out a slick, vendor-built dashboard to track gross margin by SKU. Looked amazing—until a VP noticed that gross margin had magically doubled in <a href="https://sarahgschlott.com/top-10-principles-for-transforming-fpa-towards-long-term-value-creation/">Q4</a>. Panic. Meetings. Finger-pointing. Turns out someone was pulling &#8220;net revenue&#8221; from one sheet and &#8220;COGS&#8221; from another in two completely different time zones. We found the issue—but only after rebuilding the logic in Excel from scratch. That’s when I learned: if you don’t know what’s under the hood, the dashboard is just window dressing.</p>
<h2>2. Real-Time Flexibility When the CFO (Inevitably) Asks “Can You Just…”</h2>
<p>Anyone who&#8217;s been in finance for more than 15 minutes knows this move:</p>
<p>You present a clean, polished dashboard. The CFO leans in, squints, and says: &#8220;Can you just add margin % by region for last quarter—but only for enterprise deals?&#8221;</p>
<p>The $80K BI tool freezes. Your developer isn’t in the room. Everyone stares.</p>
<p>But in Excel?</p>
<ul data-spread="false">
<li>You copy a tab</li>
<li>Adjust the filter logic</li>
<li>Rewrite a couple of SUMIFs</li>
<li>And you have the answer before the CFO finishes sipping their coffee</li>
</ul>
<p>Flexibility wins. Especially in meetings where questions shift and expectations bend. Excel is the only tool that lets finance adapt in real time without logging a ticket.</p>
<h2>3. Version Control and Audit Trail Without the Bureaucracy</h2>
<p>BI tools have audit logs. Excel has something better: visible logic.</p>
<p>You can see:</p>
<ul data-spread="false">
<li>The cell formulas</li>
<li>The assumptions</li>
<li>The actual values</li>
<li>The exact moment where someone forced a hardcoded number (and why)</li>
</ul>
<p>There’s a reason auditors still love Excel: it doesn’t hide the sausage-making.</p>
<p>Here’s a simple breakdown of what Excel lets you track in a way most tools can’t:</p>
<table>
<tbody>
<tr>
<th>Element</th>
<th>Excel</th>
<th>Most BI Tools</th>
</tr>
<tr>
<td>Source Traceability</td>
<td>Manual but transparent</td>
<td>Often obscured</td>
</tr>
<tr>
<td>Calculation Logic</td>
<td>Cell-based, easy to audit</td>
<td>Scripted, less readable</td>
</tr>
<tr>
<td><a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">Scenario</a> Adjustments</td>
<td>Real-time via formulas</td>
<td>Requires config changes</td>
</tr>
<tr>
<td>What-If Flexibility</td>
<td>Instant</td>
<td>Limited, unless modeled</td>
</tr>
<tr>
<td>Training Curve</td>
<td>Low (ubiquitous knowledge)</td>
<td>Medium to high</td>
</tr>
</tbody>
</table>
<p>It’s not about being anti-tech. It’s about using the tool that makes your thinking visible. In Excel, your logic is on the table. And that makes it easier to defend under pressure.</p>
<h2>4. It Makes Transitioning to BI Easier, Not Harder</h2>
<p>Here’s the part the software sales reps don’t tell you: a good Excel dashboard is the blueprint for a great BI build.</p>
<p>When you start in Excel:</p>
<ul data-spread="false">
<li>You’ve already validated the KPIs</li>
<li>You know the edge cases</li>
<li>You’ve tested the audience reactions</li>
<li>You’ve iterated through five versions in two weeks because the COO wanted a different <a href="https://sarahgschlott.com/the-5-most-common-mistakes-i-see-in-financial-models-and-how-to-fix-them/">revenue</a> split</li>
</ul>
<p>That means when you <em>do</em> transition to a formal dashboard, you’re not building from theory—you’re translating from practice.</p>
<p>Every BI team I’ve worked with moves faster when there’s a solid Excel prototype in hand. It reduces dev time, cuts feedback loops, and avoids the “that’s not what we meant” trap.</p>
<p>Excel first isn’t a rejection of technology. It’s a handshake between reality and readiness.</p>
<h2>Dashboards Aren’t the Point—Decisions Are</h2>
<p>Most execs don’t want another dashboard. They want clarity. They want context. They want answers. And those answers live somewhere between the ERP dump and the Monday morning <a href="https://sarahgschlott.com/how-to-make-your-fpa-function-a-strategic-partner-not-a-reporting-machine/">forecast</a> <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">review</a>.</p>
<p>If you build in Excel first, you’re forcing the conversation to happen at the right altitude. You’re not asking what colors or fonts look best. You’re asking: “What assumptions drive this model? What happens if they break?”</p>
<p>And that’s where the real value is.</p>
<p>I wrote this because I’ve seen too many smart teams get burned by overbuilding too early—mistaking presentation for process. If you found this helpful, please share it. I put real time into getting this right because I think finance should be simpler, not sexier.</p>
<p>And if you’ve got questions, feedback, or just want to compare broken dashboard horror stories, my DMs are open.</p>
<p>Here’s a final twist to get you thinking: What if the future of finance isn’t about building faster dashboards—but slower thinking?</p>
<p>Are you building tools to look smart—or to <em>be</em> smart under pressure?</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
