<?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>Q4 &#8211; Sarah Schlott</title>
	<atom:link href="https://sarahgschlott.com/tag/q4/feed/" rel="self" type="application/rss+xml" />
	<link>https://sarahgschlott.com</link>
	<description>FP&#38;A Insights</description>
	<lastBuildDate>Thu, 14 Aug 2025 04:48:34 +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>Q4 &#8211; Sarah Schlott</title>
	<link>https://sarahgschlott.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>The Silent Killer of FP&#038;A Accuracy: Calendar Drift</title>
		<link>https://sarahgschlott.com/the-silent-killer-of-fpa-accuracy-calendar-drift/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-silent-killer-of-fpa-accuracy-calendar-drift</link>
		
		<dc:creator><![CDATA[Sarah Schlott]]></dc:creator>
		<pubDate>Thu, 03 Jul 2025 22:00:41 +0000</pubDate>
				<category><![CDATA[FP&A]]></category>
		<category><![CDATA[CEO]]></category>
		<category><![CDATA[GAAP]]></category>
		<category><![CDATA[Google Sheets]]></category>
		<category><![CDATA[PO]]></category>
		<category><![CDATA[Q1]]></category>
		<category><![CDATA[Q2]]></category>
		<category><![CDATA[Q3]]></category>
		<category><![CDATA[Q4]]></category>
		<category><![CDATA[Slack]]></category>
		<guid isPermaLink="false">https://sarahgschlott.com/?p=4723</guid>

					<description><![CDATA[There’s a silent saboteur inside every FP&#38;A model. Not bias.Not bad inputs.Not even the politics. It’s time. Not as in timing—that’s obvious.As in calendar drift: the misalignment between when things are supposed to happen and when they actually do. At first glance, it looks like nothing. Your sales team says Q3 will close $4M.Great—you drop [&#8230;]]]></description>
										<content:encoded><![CDATA[<p data-start="109" data-end="159">There’s a silent saboteur inside every FP&amp;A <a href="https://sarahgschlott.com/how-to-make-your-fpa-function-a-strategic-partner-not-a-reporting-machine/">model</a>.</p>
<p data-start="161" data-end="213">Not bias.<br data-start="170" data-end="173" />Not bad inputs.<br data-start="188" data-end="191" />Not even the politics.</p>
<p data-start="215" data-end="225">It’s time.</p>
<p data-start="227" data-end="376">Not as in <em data-start="237" data-end="245">timing</em>—that’s obvious.<br data-start="261" data-end="264" />As in <strong data-start="270" data-end="288">calendar drift</strong>: the misalignment between when things are supposed to happen and when they actually do.</p>
<p data-start="378" data-end="417">At first glance, it looks like nothing.</p>
<p data-start="419" data-end="512">Your sales team says Q3 will close $4M.<br data-start="458" data-end="461" />Great—you drop it into July, August, and September.</p>
<p data-start="514" data-end="634">But what they meant was:<br data-start="538" data-end="541" />• $200K in July<br data-start="556" data-end="559" />• $1.2M in August<br data-start="576" data-end="579" />• $2.6M—if the stars align—on the last day of September</p>
<p data-start="636" data-end="758">Meanwhile, <a href="https://sarahgschlott.com/mastering-ai-in-finance-building-expertise-for-a-data-driven-future/">finance</a> logs that as three equal $1.33M monthly chunks. The board sees the nice smooth curve. Everyone’s happy.</p>
<p data-start="760" data-end="778">Until October 1st.</p>
<p data-start="780" data-end="804">That’s when you realize:</p>
<p data-start="806" data-end="867">You didn’t miss the quarter.<br data-start="834" data-end="837" />You just got <strong data-start="850" data-end="866">time-shifted</strong>.</p>
<p data-start="869" data-end="941">And because no one accounted for the drift—you now look like you missed.</p>
<h2 data-start="948" data-end="1011">Chapter 1: What Is Calendar Drift (And Why No One Tracks It)</h2>
<p data-start="1013" data-end="1052">Calendar drift isn’t just late <a href="https://sarahgschlott.com/the-5-most-common-mistakes-i-see-in-financial-models-and-how-to-fix-them/">revenue</a>.</p>
<p data-start="1054" data-end="1114">It’s the compound effect of micro-misalignments across time.</p>
<p data-start="1116" data-end="1376">In FP&amp;A terms, that means:<br data-start="1142" data-end="1145" />• Revenue showing up in Q2 that was sold in Q1<br data-start="1191" data-end="1194" />• Expenses logged in August that were incurred in July<br data-start="1248" data-end="1251" />• Commissions paid in October for deals forecasted in June<br data-start="1309" data-end="1312" />• Capex spread evenly, even though delivery was delayed 3 months</p>
<p data-start="1378" data-end="1560">These small time delays create <strong data-start="1409" data-end="1435">false variance signals</strong>, which:<br data-start="1443" data-end="1446" />→ Trigger fire drills that weren’t needed<br data-start="1487" data-end="1490" />→ Obscure actual execution issues<br data-start="1523" data-end="1526" />→ Undermine trust in your <a href="https://sarahgschlott.com/how-to-make-your-fpa-function-a-strategic-partner-not-a-reporting-machine/">forecast</a></p>
<p data-start="1562" data-end="1587">Why don’t teams catch it?</p>
<p data-start="1589" data-end="1648">Because most models are built for <em data-start="1623" data-end="1634">magnitude</em>—not <em data-start="1639" data-end="1647">timing</em>.</p>
<p data-start="1650" data-end="1693">They ask “how much?”<br data-start="1670" data-end="1673" />Not: “when exactly?”</p>
<p data-start="1695" data-end="1815">And in a world where GAAP governs <em data-start="1729" data-end="1742">recognition</em> but operations govern <em data-start="1765" data-end="1776">execution</em>, the two timelines are rarely in sync.</p>
<h2 data-start="1822" data-end="1884">Chapter 2: The Drift Shows Up Differently in Every Function</h2>
<p data-start="1886" data-end="1909">Drift hides everywhere.</p>
<p data-start="1911" data-end="1956">But it wears a different mask in each domain:</p>
<h3 data-start="1958" data-end="1976">1. <strong data-start="1965" data-end="1974">Sales</strong></h3>
<p data-start="1977" data-end="2096">They forecast based on pipeline stage or gut feel.<br data-start="2027" data-end="2030" />So Q3 might “feel strong” today—until procurement delays it to <a href="https://sarahgschlott.com/top-10-principles-for-transforming-fpa-towards-long-term-value-creation/">Q4</a>.</p>
<p data-start="2098" data-end="2151">Drift Factor: Optimism bias + lagging contract cycles</p>
<h3 data-start="2153" data-end="2175">2. <strong data-start="2160" data-end="2173">Marketing</strong></h3>
<p data-start="2176" data-end="2271">Campaign spend is planned quarterly—but vendors bill when they want, and results lag even more.</p>
<p data-start="2273" data-end="2322">Drift Factor: Misaligned spend vs. impact windows</p>
<h3 data-start="2324" data-end="2346">3. <strong data-start="2331" data-end="2344">Headcount</strong></h3>
<p data-start="2347" data-end="2427">You get approval for a Q1 hire. It takes 8 weeks to source. They start in March.</p>
<p data-start="2429" data-end="2491">Drift Factor: Planning assumes “date of approval = start date”</p>
<h3 data-start="2493" data-end="2517">4. <strong data-start="2500" data-end="2515">Procurement</strong></h3>
<p data-start="2518" data-end="2604">PO is issued in May. Invoiced in July. Paid in September.<br data-start="2575" data-end="2578" />Which month owns the <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">cost</a>?</p>
<p data-start="2606" data-end="2645">Drift Factor: Multi-month cash burn lag</p>
<h3 data-start="2647" data-end="2667">5. <strong data-start="2654" data-end="2665">Product</strong></h3>
<p data-start="2668" data-end="2777">Roadmaps drive capex plans, but hardware is backordered 10 weeks. Implementation falls into the next quarter.</p>
<p data-start="2779" data-end="2828">Drift Factor: Capex recognition vs. usage reality</p>
<p data-start="2830" data-end="2905">The bottom line? <strong data-start="2847" data-end="2867">Everyone drifts.</strong><br data-start="2867" data-end="2870" />But no one thinks it’s their fault.</p>
<h2 data-start="2912" data-end="2970">Chapter 3: Why Calendar Drift Destroys Trust in Finance</h2>
<p data-start="2972" data-end="3023">Most leadership teams don’t get mad at being wrong.</p>
<p data-start="3025" data-end="3057">They get mad at being surprised.</p>
<p data-start="3059" data-end="3183">Calendar drift breaks trust because it makes FP&amp;A look erratic—like the forecast is a moving target or a bunch of guesswork.</p>
<p data-start="3185" data-end="3250">Executives see a few things and start asking the wrong questions:</p>
<p data-start="3252" data-end="3415">• “Why did this number swing so much quarter-over-quarter?”<br data-start="3311" data-end="3314" />• “Didn’t we already account for that last month?”<br data-start="3364" data-end="3367" />• “Why does finance keep changing the forecast?”</p>
<p data-start="3417" data-end="3443">What’s <em data-start="3424" data-end="3432">really</em> happening:</p>
<p data-start="3445" data-end="3635">→ The number didn’t change. The <strong data-start="3477" data-end="3487">timing</strong> did.<br data-start="3492" data-end="3495" />→ The inputs weren’t wrong. The <strong data-start="3527" data-end="3540">alignment</strong> was off.<br data-start="3549" data-end="3552" />→ Finance isn’t flip-flopping. They’re just trying to re-sync the model to reality.</p>
<p data-start="3637" data-end="3725">But if you don’t explain the lag mechanics of your model, they’ll never see it that way.</p>
<p data-start="3727" data-end="3773">They’ll just think: <strong data-start="3747" data-end="3773">finance missed. again.</strong></p>
<h2 data-start="3780" data-end="3843">Chapter 4: The 4-Week Window That Blows Up Forecast Accuracy</h2>
<p data-start="3845" data-end="3899">Here’s the dirty secret most teams never say out loud:</p>
<p data-start="3901" data-end="3962"><strong data-start="3901" data-end="3962">A 30-day delay can destroy your credibility for 6 months.</strong></p>
<p data-start="3964" data-end="3968">Why?</p>
<p data-start="3970" data-end="4053">Because models operate on monthly cycles.<br data-start="4011" data-end="4014" />But the business moves on rolling ones.</p>
<p data-start="4055" data-end="4096">Let’s walk through a real-world <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">scenario</a>:</p>
<ul>
<li data-start="4100" data-end="4155">Your Q2 forecast includes $5M in revenue from Deal A.</li>
<li data-start="4158" data-end="4214">Deal A closes on June 28—but rev rec kicks in on July 1.</li>
</ul>
<p data-start="4216" data-end="4378">Suddenly, your Q2 revenue is $5M short.<br data-start="4255" data-end="4258" />And your Q3 is “inflated” by $5M.<br data-start="4291" data-end="4294" />Nothing changed in the business.<br data-start="4326" data-end="4329" />But the <strong data-start="4337" data-end="4349">calendar</strong> just torched your trendline.</p>
<p data-start="4380" data-end="4487">Now the CEO is on your case:<br data-start="4408" data-end="4411" />“What happened in Q2?”<br data-start="4433" data-end="4436" />“Why does Q3 look spiky?”<br data-start="4461" data-end="4464" />“Should we be worried?”</p>
<p data-start="4489" data-end="4575">It doesn’t matter that the deal landed.<br data-start="4528" data-end="4531" />It matters <strong data-start="4542" data-end="4575">when the model said it would.</strong></p>
<p data-start="4577" data-end="4692">And unless your team is logging execution dates <em data-start="4625" data-end="4640">independently</em> from recognition dates, you’ll never fix the drift.</p>
<h2 data-start="4699" data-end="4746">Chapter 5: The Psychology of Misaligned Time</h2>
<p data-start="4748" data-end="4815">Calendar drift is a <a href="https://sarahgschlott.com/mastering-ai-in-finance-building-expertise-for-a-data-driven-future/">data</a> problem—but it’s also a <strong data-start="4797" data-end="4814">cognitive one</strong>.</p>
<p data-start="4817" data-end="4874"><a href="https://sarahgschlott.com/rolling-forecasts-vs-budgets-what-high-performing-teams-get-right/">Finance teams</a> are taught to think in quarters and months.</p>
<p data-start="4876" data-end="4958">But humans don’t operate like that.<br data-start="4911" data-end="4914" />We think in events, not calendar increments.</p>
<p data-start="4960" data-end="5069">→ “The week after that big demo”<br data-start="4992" data-end="4995" />→ “Sometime before back-to-school”<br data-start="5029" data-end="5032" />→ “Once the new head of sales starts”</p>
<p data-start="5071" data-end="5122">That’s how ops and revenue leaders actually behave.</p>
<p data-start="5124" data-end="5218">Which means your model needs a <strong data-start="5155" data-end="5176">translation layer</strong> between <em data-start="5185" data-end="5197">human time</em> and <em data-start="5202" data-end="5217">calendar time</em>.</p>
<p data-start="5220" data-end="5322">Otherwise, you’re building a predictive engine that’s misaligned with how the business actually flows.</p>
<h2 data-start="5329" data-end="5384">Chapter 6: How to Spot Calendar Drift in Your Models</h2>
<p data-start="5386" data-end="5435">Most teams don’t catch drift until it’s too late.</p>
<p data-start="5437" data-end="5494">But there are 4 signals that almost always show up first:</p>
<h3 data-start="5496" data-end="5539">1. <strong data-start="5503" data-end="5539">Lagging Pipeline to Close Ratios</strong></h3>
<p data-start="5540" data-end="5664">→ Deals are still closing, but way after forecasted close date<br data-start="5602" data-end="5605" />→ Your “win rate” looks fine but conversion <em data-start="5649" data-end="5657">timing</em> is off</p>
<h3 data-start="5666" data-end="5707">2. <strong data-start="5673" data-end="5707">Recurring Variance “Reversals”</strong></h3>
<p data-start="5708" data-end="5804">→ A big miss in Q1 is magically “fixed” in Q2<br data-start="5753" data-end="5756" />→ The number wasn’t wrong—it just showed up late</p>
<h3 data-start="5806" data-end="5840">3. <strong data-start="5813" data-end="5840">Unexplainable Cash Gaps</strong></h3>
<p data-start="5841" data-end="5977">→ Revenue was on target<br data-start="5864" data-end="5867" />→ Expenses were forecasted<br data-start="5893" data-end="5896" />→ But cash still dropped—because of delayed vendor payments or backloaded payroll</p>
<h3 data-start="5979" data-end="6011">4. <strong data-start="5986" data-end="6011">Non-linear Trendlines</strong></h3>
<p data-start="6012" data-end="6159">→ Instead of clean curves, your metrics look like sawtooth waves<br data-start="6076" data-end="6079" />→ That’s a classic drift pattern—caused by lumpy timing, not performance changes</p>
<p data-start="6161" data-end="6179">Spot any of those?</p>
<p data-start="6181" data-end="6207">You’re dealing with drift.</p>
<h2 data-start="6214" data-end="6273">Chapter 7: How to Fix It—Without Burning Down Your Model</h2>
<p data-start="6275" data-end="6327">Fixing drift doesn’t mean reinventing your forecast.</p>
<p data-start="6329" data-end="6375">But it <strong data-start="6336" data-end="6344">does</strong> require one fundamental shift:</p>
<h3 data-start="6377" data-end="6439">Move from <em data-start="6391" data-end="6408">monthly buckets</em> to <em data-start="6412" data-end="6439">event-driven time models.</em></h3>
<p data-start="6441" data-end="6461">Here’s how to start:</p>
<h3 data-start="6463" data-end="6508">1. <strong data-start="6470" data-end="6508">Add an “Execution Timestamp” Field</strong></h3>
<p data-start="6509" data-end="6627">In every input sheet—sales, hiring, procurement—add a second date column:<br />
→ When is this <em data-start="6598" data-end="6608">actually</em> expected to occur?</p>
<p data-start="6629" data-end="6729">Let revenue log deal <em data-start="6650" data-end="6657">start</em> date and rev rec date.<br />
Let HR log offer <em data-start="6698" data-end="6706">accept</em> date and <em data-start="6716" data-end="6723">start</em> date.</p>
<p data-start="6731" data-end="6786">Then forecast based on <em data-start="6754" data-end="6769">execution lag</em>, not assumption.</p>
<h3 data-start="6793" data-end="6843">2. <strong data-start="6800" data-end="6843">Layer in Lag-Based Forecast Adjustments</strong></h3>
<p data-start="6844" data-end="6920">Use historical lags (actual vs. forecasted timing) to adjust current inputs.</p>
<p data-start="6922" data-end="7036">Example:<br />
If Q2 deals closed 21 days later than forecasted last year, apply a +3-week lag buffer to this year’s Q2.</p>
<p data-start="7038" data-end="7107">This “drift curve” helps smooth false variance and build credibility.</p>
<h3 data-start="7114" data-end="7181">3. <strong data-start="7121" data-end="7181">Tie Spend to Project or Campaign Timelines, Not Quarters</strong></h3>
<p data-start="7182" data-end="7328">Instead of allocating marketing <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">budget</a> evenly across Q3, tie spend to:<br />
→ Campaign kickoff dates<br data-start="7277" data-end="7280" />→ Vendor billing cycles<br data-start="7303" data-end="7306" />→ Target launch events</p>
<p data-start="7330" data-end="7391">This creates a reality-based burn curve—not a fabricated one.</p>
<h3 data-start="7398" data-end="7468">4. <strong data-start="7405" data-end="7468">Use Rolling Forecast Windows with Leading Indicator Anchors</strong></h3>
<p data-start="7469" data-end="7614">→ Stop using fixed-month snapshots<br data-start="7503" data-end="7506" />→ Build weekly models anchored to leading ops signals (e.g., pipeline stage velocity, offer acceptance rate)</p>
<p data-start="7616" data-end="7695">Rolling windows reduce drift by letting timing flex—without breaking the model.</p>
<h2 data-start="7702" data-end="7751">Chapter 8: What Happens When You Fix the Drift</h2>
<p data-start="7753" data-end="7817">When you build for calendar realism instead of calendar fiction:</p>
<p data-start="7819" data-end="7941">→ Forecast accuracy improves<br data-start="7847" data-end="7850" />→ FP&amp;A trust goes up<br data-start="7870" data-end="7873" />→ Fire drills go down<br data-start="7894" data-end="7897" />→ Leadership stops second-guessing the model</p>
<p data-start="7943" data-end="7962">But more than that?</p>
<p data-start="7964" data-end="8004">You stop being the “variance explainer.”</p>
<p data-start="8006" data-end="8053">And you start being the <strong data-start="8030" data-end="8053">reality translator.</strong></p>
<p data-start="8055" data-end="8091">Because that’s what great FP&amp;A does.</p>
<p data-start="8093" data-end="8126">Not report what already happened.</p>
<p data-start="8128" data-end="8208"><strong data-start="8128" data-end="8208">But re-sync the map to the terrain—before anyone else sees the misalignment.</strong></p>
<h2 data-start="8215" data-end="8264">The Real Skill Nobody Teaches in FP&amp;A</h2>
<p data-start="8266" data-end="8324">We train finance teams to analyze ratios and build models.</p>
<p data-start="8326" data-end="8376">We don’t train them to ask:<br data-start="8353" data-end="8356" /><strong data-start="8356" data-end="8376">“When, exactly?”</strong></p>
<p data-start="8378" data-end="8424">That’s the missing variable in most forecasts.</p>
<p data-start="8426" data-end="8510">And the reason why so many models feel “mostly right” but never quite match reality.</p>
<p data-start="8512" data-end="8557">So if you want to uplevel your FP&amp;A practice?</p>
<p data-start="8559" data-end="8592">Forget the formulas for a minute.</p>
<p data-start="8594" data-end="8617">Start by chasing drift.</p>
<p data-start="8619" data-end="8710">Because no matter how good your inputs are—<br data-start="8662" data-end="8665" /><strong data-start="8665" data-end="8710">If the timing’s off, the truth gets lost.</strong></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Top 10 Principles for Transforming FP&#038;A Towards Long-Term Value Creation</title>
		<link>https://sarahgschlott.com/top-10-principles-for-transforming-fpa-towards-long-term-value-creation/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=top-10-principles-for-transforming-fpa-towards-long-term-value-creation</link>
		
		<dc:creator><![CDATA[Sarah Schlott]]></dc:creator>
		<pubDate>Thu, 08 May 2025 01:42:34 +0000</pubDate>
				<category><![CDATA[FP&A]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[E-E-A-T]]></category>
		<category><![CDATA[ESG]]></category>
		<category><![CDATA[Excel]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[KPI]]></category>
		<category><![CDATA[P&L]]></category>
		<category><![CDATA[PowerPoint]]></category>
		<category><![CDATA[Q4]]></category>
		<guid isPermaLink="false">https://sarahgschlott.com/?p=4417</guid>

					<description><![CDATA[It’s been said a hundred times in every boardroom I’ve ever sat in: “We need to be more strategic with our planning.” Great. But what does that actually mean in a world where financial planning and analysis (FP&#38;A) is still, in many places, little more than spreadsheet jockeying dressed in quarterly PowerPoint suits? I’ve watched [&#8230;]]]></description>
										<content:encoded><![CDATA[<p data-pm-slice="1 1 []">It’s been said a hundred times in every boardroom I’ve ever sat in: “We need to be more strategic with our planning.” Great. But what does that actually mean in a world where financial planning and analysis (FP&amp;A) is still, in many places, little more than spreadsheet jockeying dressed in quarterly PowerPoint suits? I’ve watched teams get bogged down by noise, misaligned incentives, and legacy rituals designed to make people feel productive—not to actually build long-term enterprise value.</p>
<p>In this post, I’ll walk through the top 10 strategic FP&amp;A principles that I believe—based on hard-won scars and quiet breakthroughs—can transform corporate financial planning into a long-horizon value engine. Not the kind of fluff you hear on earnings calls, but the kind that makes organizations resilient, aligned, and free from the tyranny of short-termism.</p>
<p>&nbsp;</p>
<p><img fetchpriority="high" decoding="async" class="aligncenter size-large wp-image-4422" src="https://sarahgschlott.com/wp-content/uploads/2025/05/ChatGPT-Image-May-7-2025-09_49_44-PM-1030x687.jpg" alt="" width="1030" height="687" srcset="https://sarahgschlott.com/wp-content/uploads/2025/05/ChatGPT-Image-May-7-2025-09_49_44-PM-1030x687.jpg 1030w, https://sarahgschlott.com/wp-content/uploads/2025/05/ChatGPT-Image-May-7-2025-09_49_44-PM-300x200.jpg 300w, https://sarahgschlott.com/wp-content/uploads/2025/05/ChatGPT-Image-May-7-2025-09_49_44-PM-768x512.jpg 768w, https://sarahgschlott.com/wp-content/uploads/2025/05/ChatGPT-Image-May-7-2025-09_49_44-PM-705x470.jpg 705w, https://sarahgschlott.com/wp-content/uploads/2025/05/ChatGPT-Image-May-7-2025-09_49_44-PM.jpg 1200w" sizes="(max-width: 1030px) 100vw, 1030px" /></p>
<h2>Principle 1: Kill the Budget (or at Least Loosen Its Grip)</h2>
<p>If you’re still setting rigid annual budgets in Q4 and expecting them to hold up 10 months later, you’re doing it wrong. Budgets aren’t strategy—they’re constraints. Instead, adopt rolling forecasts and <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">scenario</a> planning that mirror actual market dynamics.</p>
<ul data-spread="false">
<li>Static budgets create false certainty</li>
<li>Rolling forecasts build adaptability</li>
<li><a href="https://sarahgschlott.com/how-to-make-your-fpa-function-a-strategic-partner-not-a-reporting-machine/">Scenario planning</a> clarifies response options before crises hit</li>
</ul>
<h2>Principle 2: Shift from Reporting to Sensing</h2>
<p>Most FP&amp;A teams spend 70% of their time on backward-looking financial reporting and 30% explaining what already happened. Flip it. Use real-time <a href="https://sarahgschlott.com/mastering-ai-in-finance-building-expertise-for-a-data-driven-future/">data</a> to sense early trends. Financial planning intelligence should be predictive, not just reflective.</p>
<ul data-spread="false">
<li>Invest in data infrastructure for real-time insights</li>
<li>Build dashboards that flag leading indicators, not just lagging metrics</li>
<li>Create feedback loops between operations and <a href="https://sarahgschlott.com/mastering-ai-in-finance-building-expertise-for-a-data-driven-future/">finance</a></li>
</ul>
<h2>Principle 3: Don’t Report Everything—Report What Matters</h2>
<p>Too much financial data creates informational smog. Your job isn’t to recreate the data warehouse—it’s to distill what’s actionable. I once sat in on a monthly business <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">review</a> that had 115 slides. Only three changed any decisions.</p>
<p>Ask:</p>
<ul data-spread="false">
<li>Who is the audience?</li>
<li>What do they need to know to act?</li>
<li>What <em>won’t</em> we report—and why?</li>
</ul>
<h2>Principle 4: Build Models That Tell Stories, Not Just Numbers</h2>
<p>A spreadsheet can show you variance. A good FP&amp;A model explains why it happened, who it affects, and what’s likely to come next. When I started using narrative-style annotations in financial models, people finally stopped asking for more slides.</p>
<table>
<tbody>
<tr>
<th>Feature</th>
<th>Traditional Model</th>
<th>Strategic FP&amp;A Model</th>
</tr>
<tr>
<td>Output</td>
<td>Static numbers</td>
<td>Dynamic insights</td>
</tr>
<tr>
<td>Use case</td>
<td>Compliance</td>
<td>Decision support</td>
</tr>
<tr>
<td>Structure</td>
<td>Flat tabs</td>
<td>Integrated, cross-functional</td>
</tr>
<tr>
<td>Format</td>
<td>Excel-heavy</td>
<td>API-driven, dashboard-first</td>
</tr>
</tbody>
</table>
<h2>Principle 5: Align Incentives with Long-Term Outcomes</h2>
<p>Short-term KPIs are like sugar. They’re cheap, addictive, and leave your organization crashing. Reframe incentives around strategic financial outcomes—customer retention, net present value of new initiatives, or operating margin over a 3-year horizon.</p>
<ul data-spread="false">
<li>Link compensation to long-term value creation, not quarterly wins</li>
<li>Embed ESG and sustainability into financial planning and analysis</li>
<li>Teach teams how to think in systems, not silos</li>
</ul>
<h2>Principle 6: Make Planning an Ongoing Dialogue, Not an Annual Ritual</h2>
<p>Annual financial planning is often a lonely exercise. One team builds, another signs off, and then everyone forgets until next year. The alternative? Treat planning as a living dialogue across departments.</p>
<ul data-spread="false">
<li>Hold quarterly <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">strategic alignment</a> reviews</li>
<li>Involve product, marketing, and ops in scenario planning</li>
<li>Turn planning into decision-making, not documentation</li>
</ul>
<h2>Principle 7: Prioritize Drivers Over Outcomes</h2>
<p>You can’t control <a href="https://sarahgschlott.com/the-5-most-common-mistakes-i-see-in-financial-models-and-how-to-fix-them/">revenue</a>. You can control the number of qualified leads, the conversion rate, the <a href="https://sarahgschlott.com/the-5-most-common-mistakes-i-see-in-financial-models-and-how-to-fix-them/">churn</a> rate, and your gross margin. These are your operational levers. Build your financial models around them—not just the outcomes they produce.</p>
<p>Focus on:</p>
<ul data-spread="false">
<li>Leading indicators vs lagging KPIs</li>
<li>Controllable vs exogenous variables</li>
<li>Strategy-linked <a href="https://sarahgschlott.com/the-5-most-common-mistakes-i-see-in-financial-models-and-how-to-fix-them/">assumptions</a> and risk factors</li>
</ul>
<h2>Principle 8: Democratize Financial Literacy</h2>
<p>Finance shouldn’t be a dark art. When more people understand the P&amp;L and the tradeoffs behind capital allocation, better business decisions happen. This is the cheapest transformation you can make.</p>
<ul data-spread="false">
<li>Run profit &amp; loss literacy workshops across departments</li>
<li>Build self-service financial planning tools</li>
<li>Replace finance jargon with actionable plain language</li>
</ul>
<h2>Principle 9: Marry Tech with Talent</h2>
<p>No digital finance transformation survives contact with a talent gap. You can buy the best planning software on the planet, but if your FP&amp;A team can’t interpret, challenge, and communicate what comes out of it, it’s useless.</p>
<ul data-spread="false">
<li>Upskill FP&amp;A staff in data analysis, finance automation, and storytelling</li>
<li>Hire financial translators: people who speak both numbers and business</li>
<li>Don’t automate judgment—augment it</li>
</ul>
<h2>Principle 10: Elevate FP&amp;A to a Strategic Business Partner</h2>
<p>The real north star: FP&amp;A as a strategy function, not just a <a href="https://sarahgschlott.com/implementing-zero-based-budgeting-in-fpa-a-10-step-guide/">cost</a> center. This means your financial planning analysts earn their seat at the table—not just by being precise, but by being forward-thinking.</p>
<p>That means:</p>
<ul data-spread="false">
<li>Bringing opportunity costs into every conversation</li>
<li>Framing decisions through capital efficiency and risk-adjusted returns</li>
<li>Being the voice of long-term value—not just short-term constraints</li>
</ul>
<h2>Final Thoughts: Towards an FP&amp;A Function That Thinks Like a Founder</h2>
<p>If you take one thing away from this, let it be this: good FP&amp;A doesn’t chase accuracy for its own sake. It uses data to illuminate uncertainty and build better business bets. It’s part economics, part psychology, part street smarts.</p>
<p>The companies I’ve seen win over the long run aren’t the ones with the tightest budgets. They’re the ones where finance dares to think like investors, align capital with mission, and measure success not by this quarter—but by the next decade.</p>
<p>And if that sounds radical—it’s because it is. But trust me: it works.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
