Good News Makes Me Nervous

I have a slightly inconvenient habit in Finance.

When the numbers are bad, I ask questions.

When the numbers are good, I ask more questions.

Revenue is $800,000 ahead of forecast?

Great.

Why?

Gross margin improved three points?

Wonderful.

What happened?

Cash collections suddenly accelerated?

Now I’m suspicious.

This is probably not the personality trait my family would choose to highlight about me. My husband has spent years watching me receive perfectly good news and immediately begin looking for the small door marked potential disaster.

Finance just gave this tendency a respectable career.

But there’s a reason I’m suspicious of good news.

Bad news gets investigated.

Good news gets congratulated.

And sometimes that’s exactly how the next forecast miss gets started.

The $800,000 question

Imagine we’re sitting in a monthly business review and revenue comes in $800,000 above forecast.

There’s usually a brief moment when everyone is happy.

Sales had a great month. The business beat the plan. Someone might even point out that Finance was too conservative.

Fine.

But I want to know where the $800,000 came from.

Did we win business we weren’t expecting?

Did an existing customer expand?

Did something scheduled for next month close early?

Did implementation happen faster than expected?

Was there a pricing benefit?

Was there an assumption in the forecast that was simply wrong?

Those answers describe very different businesses.

If customers are expanding faster than we expected, I may want to revisit the rest of the year.

If $500,000 of next month’s revenue arrived early, I probably shouldn’t.

Same favorable variance.

Completely different information.

That distinction matters because the job isn’t to explain why the number is green.

The job is to understand what the green number is telling us.

A beat can borrow from the future

Timing is one of the first places I look when something comes in unexpectedly favorable.

A big customer signs earlier.

A shipment moves.

A project gets completed.

A payment arrives.

An expense doesn’t.

Everything looks wonderful.

Sometimes it is wonderful.

Other times we’ve simply moved something across a calendar.

That becomes especially important during forecasting because businesses have a natural tendency to treat upside as evidence and downside as an exception.

Revenue arrives early and suddenly we’re discussing whether the full-year forecast should go up.

Revenue slips and we’re explaining why it’ll definitely arrive next month.

You can probably see where this goes.

If we’re going to change our view of the future, I want to understand whether something about the business actually changed.

The calendar changing isn’t always the same thing.

I’m especially suspicious of margin improvement

Revenue gets most of the attention, but unexpected margin improvement can be even more interesting.

If gross margin jumps, I want to understand the mechanics.

Did pricing improve?

Did product mix change?

Did input costs decline?

Did utilization improve?

Did we become more efficient?

Or did an expense land somewhere we weren’t expecting?

There is a large difference between:

“Margins improved because the business is operating better.”

and

“Margins improved because something hasn’t hit the P&L yet.”

Both can produce a very attractive chart.

Only one necessarily deserves a victory lap.

This is where FP&A earns its seat in the conversation.

Not by being the person who refuses to celebrate anything.

Nobody wants to work with that person.

The value is being able to distinguish between a result and a signal.

Favorable variances deserve variance analysis too

Most finance organizations have a deeply ingrained response to misses.

Actual is below plan.

Investigate.

Find the driver.

Talk to the business.

Explain the variance.

Update the forecast.

Actual is above plan?

Nice job, everyone.

Next slide.

I’ve never completely understood that.

A favorable variance is still telling us our expectation of the business differed from reality.

That should make us curious.

Maybe we underestimated demand.

Maybe our pricing assumptions were wrong.

Maybe Sales changed behavior.

Maybe a productivity initiative is actually working.

Maybe customers are paying faster because something changed in collections.

Those aren’t merely explanations for why we beat a number.

They’re information we can use.

And occasionally the good variance reveals something more important than the bad one.

The question isn’t “Was it good?”

When I’m looking at an unexpected favorable result, I usually want to sort it mentally into a few buckets.

Was it structural?

Something about the business may genuinely have improved. Pricing, retention, productivity, conversion, customer behavior, operating leverage.

If so, we should understand it well enough to determine whether our assumptions about the future need to change.

Was it timing?

Nothing fundamental changed. Something simply happened earlier or later than expected.

Important to understand, but probably not a reason to rewrite the year.

Was it a one-off?

A large deal. A settlement. A temporary cost benefit. Something real, but not something I’d build into the next twelve months.

Or were we simply wrong?

I think Finance occasionally has trouble with this one.

Sometimes there isn’t an elegant business explanation.

Our assumption was bad.

That’s useful information too.

I’d rather discover that an assumption doesn’t hold than spend three months defending it because it happens to live in the official forecast.

This is where forecasting gets interesting

A forecast isn’t valuable because it predicts every number correctly.

It won’t.

What makes it valuable is that it forces us to make our assumptions about the business visible.

We think customers will buy at this rate.

We think headcount will grow at this pace.

We think margins will behave this way.

We think collections will take this long.

Then reality shows up and starts arguing with us.

That’s the interesting part.

Every variance is new information about the business.

The mistake is treating favorable variances as proof that things are going well and unfavorable variances as problems requiring investigation.

Both are evidence.

Both can expose weak assumptions.

Both can change what we believe happens next.

Sometimes good news is actually good news

I should probably make this clear before I ruin everyone’s next monthly review.

Sometimes the business just had a great month.

Sales executed.

Operations improved.

Customers paid.

Margins expanded.

People did good work and the numbers reflected it.

Celebrate it.

I’m not suggesting Finance sit in the corner waiting to explain why happiness is premature.

But after the celebration, I still want to understand what happened.

Because if something worked, I want to know whether we can do it again.

That’s the part of favorable variance analysis I think gets overlooked.

Investigating good news isn’t pessimism.

It’s how you figure out whether good performance was luck, timing, or something the business actually learned how to do better.

And if it’s the last one, that’s worth considerably more than beating the forecast once.

So yes, good news still makes me a little nervous.

My husband would probably tell you that’s just my personality.

He may be right.

Finance has simply provided me with enough spreadsheets to make it look professional.

I separate repeatable good news from borrowed good news

This is the distinction I am usually trying to make.

Repeatable good news comes from something the business can plausibly do again.

Better conversion. Sustainable pricing. Improved productivity. A process change that reduced cost.

Borrowed good news belongs partly to another period.

A customer paid early. A project slipped out. Hiring moved. An invoice did not arrive.

The current month looks better because another month will look worse.

Both can be favorable variances.

Only one should automatically improve the forward view.

Revenue upside needs a source

If revenue beats forecast, I want to know whether the underlying demand changed.

Was there more volume? Better pricing? Faster deal timing? Lower churn? A one-time order? Revenue recognized earlier than expected?

Those answers have different implications.

A deal that closed two weeks early may improve this month and reduce next month.

A sustained improvement in win rate may deserve a forecast change.

“Revenue beat” is the beginning of the analysis, not the conclusion.

Margin improvement can be particularly sneaky

Gross margin jumps three points and everyone is happy.

I am happy too.

Then I want to know whether cost moved with the revenue it belonged to.

Maybe mix improved. Maybe pricing held. Maybe vendor savings arrived.

Or maybe a cost was not accrued, implementation slipped, or a lower-margin project moved into next month.

I have seen enough favorable margin surprises reverse that I prefer understanding the mechanism before annualizing the celebration.

Cash can look good because somebody else is waiting

Cash collections ahead of forecast are genuinely useful.

But the bank balance can also improve because vendor payments slipped, CapEx moved, payroll timing changed or a tax payment landed in another period.

I like a cash bridge for exactly this reason.

What came in earlier? What went out later? What changed permanently?

A strong ending cash balance is good news.

I just want to know how much of it belongs to us versus next Tuesday.

Favorable headcount variance may be an operating miss

Payroll under budget gets described as savings surprisingly quickly.

If the company deliberately removed unnecessary roles, perhaps it is.

If recruiting failed to fill the engineers required for a launch, the lower payroll is not necessarily good news.

The P&L is favorable.

The operating plan may be behind.

This is why I do not like evaluating expense variances without understanding what the spend was supposed to accomplish.

Good news deserves the same root-cause discipline as bad news

Finance teams often have excellent processes for unfavorable variance.

Thresholds. Commentary. Owners. Corrective actions.

Then favorable variance gets a green arrow and a smile.

I would use the same basic questions.

What changed? Is it timing, volume, rate, mix or a decision? Is it recurring? Does it change the forecast? Is there an action worth repeating?

The tone can be happier.

The curiosity should remain.

Sometimes the good news is real—and that is valuable information

I do not want this to sound like Finance should distrust success until morale improves.

Sometimes the business genuinely did something better.

That is exactly why I investigate.

If a sales team changed qualification and win rates improved, I want to know. If Operations redesigned a process and labor productivity increased, I want to understand it. If a pricing change held better than expected, that belongs in the next decision.

Favorable variance can teach us what to repeat.

That is considerably more useful than simply reporting that the number was green.

The forecast should change only when the evidence changes

One strong month can tempt management to raise the year.

Sometimes that is right.

Sometimes it is how optimism gets into the forecast wearing an actual-results costume.

I want enough evidence to understand whether the driver changed.

If it did, update the assumption.

If the result was timing or one-time, preserve the annual view appropriately.

The forecast should learn from actuals without becoming emotionally dependent on the most recent month.

Celebration and skepticism can coexist

I think Finance occasionally acts as though asking a question ruins the party.

It does not have to.

Congratulate the team.

Then learn from the result.

If the upside is repeatable, that is better news than the original variance because now management has something it can use.

If it is timing, fine. We know not to overreact.

If it exposed a forecasting weakness, fix it.

Curiosity does not make good news smaller.

It tells us what kind of good news we actually have.

The same discipline improves future forecasting

When Finance explains favorable misses properly, the forecast gets better in both directions.

We learn which assumptions were too conservative, which operating drivers changed, and which apparent improvements were only timing.

That matters because systematic underforecasting is not automatically safer than systematic overforecasting.

Management can make bad decisions from either one.

If revenue is consistently stronger than Finance expects, perhaps hiring, inventory or cash planning is now too conservative.

If expenses are consistently favorable because hiring always slips, the operating plan may be too aggressive.

Accuracy is not about making every month land perfectly.

It is about learning where our view of the business is repeatedly wrong.