The Exception Effect: “Bank!”

In grade school, one of my best friends and I played basketball almost every day. We’d go to 11 or 21, scoring by ones and twos. It was always a hard-fought game — I wasn’t as good, so I had to hustle harder to keep up. And we had this running joke, almost like a rule: if you shot from outside the post and banked it off the backboard, it didn’t count unless you called “Bank!” before it went in.

That little rule was our way of saying, “Nice shot… but under these circumstances, it doesn’t really count.”

And that’s exactly how I think about the exception effect in the revenue bridge.

What Is the Exception Effect?

The exception effect is the catch-all bucket for those odd, one-off circumstances that don’t neatly fit into the usual categories like price, volume, mix, or currency exchange. Just like that bank shot without the call, it’s something that technically happened — but under the rules, it doesn’t count.

Common Causes of Exceptions

Depending on the business, exceptions can come from different places. In manufacturing, I often see them triggered by:

  • Credits — especially when issued incorrectly, like partial credits that don’t align with the original transaction.
  • Rebates — sometimes creating mismatches that don’t reconcile cleanly.
  • Incorrect billing — requiring a credit and rebill, which can throw off the data.

These don’t fit into price increases, volume changes, or mix effects. Instead, they land in the exception bucket.

Why Exceptions Matter

Think of the exception effect as the “doesn’t count” pile. Everything else contributes to the revenue bridge, but these anomalies distort the story, so we set them aside. The goal is to keep the exception effect as small as possible.

Why? Because a large exception effect muddies the narrative. It makes it harder to explain what’s really driving changes in revenue. We want to get the information to one number and that one number to be meaningful.

The best way to reduce exceptions is through front-end filtering in the raw data. By cleaning the data upfront, you prevent anomalies from sneaking into the bridge. Caution: when you filter you do add bias to the view of the revenue bridge.

The Bigger Story

The exception effect is a reminder that business data, like a game of basketball, has its quirks. Sometimes you hit the shot, but unless you called “Bank,” it doesn’t count.

Or think of it like a movie: the main film tells the story, but the bloopers reel is full of funny, awkward, or unexpected moments that don’t belong in the final cut. The exception effect is the bloopers reel of the revenue bridge. It’s entertaining (in a I can’t believe we do that . .  sort of way . . . ) to look at, but it’s not the story you want to tell.

Keep the exception effect small, and the revenue bridge delivers a clean, confident narrative.

Comments

Post a Comment

Popular posts from this blog

Intro

     After three years working in pricing—alongside a background in natural resource economics and a master’s in applied econometrics—I’ve come to see pricing as one of the most fascinating areas in business. It’s not just about supply and demand curves or profit maximization. In practice, pricing is messy, nuanced, and deeply human. That complexity is what makes it so compelling. I’ve wanted to document my journey and growth in this field, especially the patterns I’ve observed. As "pricers", we often focus on the exciting parts: choosing between value-based, cost-plus, or competitive models (and interesting variations such as good, better, best). Or speculating on how AI might transform pricing strategy, execution and analytics. But we also dig into the gritty details—the DNA of our systems—where real change happens. Early on, I felt lost. I didn’t know how to measure whether our pricing was working. That’s when I discovered revenue bridges and the power of using them fo...
Read more

Assessing Averages

Image
     I really love statistics. They’re all over the place business, economics, the grocery store — average cost per ounce, sale prices, distribution. But here’s the funny thing about some of the averages: the “ASP,” or Average Sale Price, is just that — an average. And if you’re not careful, you can end up averaging the averages. Think about it. Instead of saying, we did half a million dollars in revenue, sold 50,000 units, which equates to $10 per unit , what often happens is someone takes the, say 8 thousand transactions that the revenue happened over — a spread of prices — and averages those transaction-level averages. Suddenly, you’re looking at $9 or $12.50 instead of the true $10. That’s not just sloppy math; it’s misleading. Even weighted ASPs—which I recommend using in pricing—while technically correct, can still hide the real story. Dan Heath talks about this idea of untangling averages in his book “Reset”. His example comes from the military’s attempt to des...
Read more

Revenue Bridge?

Image
       Revenue bridges might not be carved from granite — but they’re just as solid when built on comparison. They’re built on the comparison of prices, volume, product mix. We compare constantly — especially in sports. Yankees vs. Dodgers. Jordan or LeBron. Scheffler vs. Tiger (too soon?) In the 1500s, Pope Leo X had a beloved white elephant named Hanno, living in luxury at the Vatican. Then came Ganda — a rhinoceros, the first seen in Europe in over a thousand years. Naturally, the Pope staged a showdown to answer the question of which animal was superior. Ganda charged. Hanno fled. The Pope laughed and after calling the rhino ‘a beast of Satan,’ was shipped off (but sadly didn’t survive the journey). Ganda lived on; however, in Albrecht Dürer’s famous woodcut — armor-plated and horned, despite the artist never seeing a rhino. Hanno remained the Pope's prized animal.  In business, we’re lucky to have more reliable comparisons than an elephant to a rhino. Rev...
Read more