Subscribe by Email

Your email:

Editorial Info

As a source for thoughtful articles featuring trends, news, insight, and expertise relating to the FP&A industry, the Agile Planner welcomes guest contributors and content suggestions.  If you have an article that you would like to share or a topic you would like to suggest we discuss, please let us know.

blog@alightplanning.com

Follow Me

The Agile Planner

Current Articles | RSS Feed RSS Feed

Driver-Based Budgeting vs. Driver-Based Planning

driver-based budgeting

I am pleased to say that when I now google “Driver-Based Planning: How is it Defined?” the organic search points to the earlier blog post by that name. However, this proposed definition of “driver-based planning” actually created more of a stir in the finance community than I had anticipated. I have been thinking a lot about this “driver-based” thing and thought I’d share the latest thinking after returning from a trip to San Diego where I got to present “The Planning Maturity Curve: Where Are You? Where Do You Want to Be?” as part of the ASMI Budgeting and Forecasting Summit.

I am working on an improved definition that should resonate with the thought-leaders and begin a conversation to create simple, doable steps to improve business performance in organizations of all sizes. While my goals may be lofty, if you keep reading, and participate in this discussion, we might just end up with an HBR article and a new movement for management consulting to tackle.

The terms “driver-based budgeting” and “driver-based planning” are often used interchangeably. This ambiguity is the impetus for this week’s blog.

Let’s begin with a pretty good definition I’ve seen proposed elsewhere: “Driver based budgeting is an approach for simplifying, expediting, and improving the budgeting process.”

It’s easiest to understand driver-based budgeting by looking at an extreme example of what is not driver-based budgeting. Imagine a budget where every manager not only enters in dollar amounts for expense items such as travel and supplies, but also enters the base salary, payroll taxes, and benefit costs by employee. They do so by typing in dollar amounts or looking up the value in a table for each and every employee. You can imagine that travel expenses are entered as dollar amounts for various trips broken out by airfare, hotel, and the like. The numbers are all added up and that makes the budget. The point is: there is no multiplication happening in this budget process, and a budget without multiplication is not a driver-based budget. If you read between the lines, you also get the impression that this budget is fairly detailed with dollar amounts for every single expense item. In fact, it is the goal to be precise and enter in the exact estimate (how’s that for an oxymoron?) of each expense item, which will be more accurate if it is built “bottoms-up”…

Driver-Based Budgeting Simple Definition

A budget that is highly driver-based would have multiplication.

For example, in a more driver-based budget, payroll taxes might be calculated as base salary multiplied by a set payroll tax rate. Depending on the industry, variable costs may be “driver-based”; for example, cost of goods sold might be multiplied by a dollar amount per unit sold.

The thing that makes it “driver-based” is simply the mathematical fact that the budget is partially derived using multiplication. The more multiplication in the budget, the more it is driver-based. You know you are moving to a driver-based budget if managers enter things like:

  • (number of conferences attended) x (average cost per conference),

  • (number of beverages ordered per table occupied) x (number of tables occupied),

  • Etc.

As a general rule, minimizing the number of inputs and maximizing the number of linked (automated/calculated) relationships will optimize the driver-based budget model. Optimizing the driver-based budget reduces errors simply by requiring fewer manual inputs, and it saves time since calculations happen more or less instantaneously. If you are able to leverage a Unit-Rate-Amount architecture, then you will be able to clearly see the driver relationships. Better visibility into the numbers is generally very important to management. Moreover, as noted in “Causal Analysis”, a Unit-Rate-Amount structure enables you to answer the question “why the variance” by breaking out the impacts of units and rates on the variance amount.

So, “driver-based” can be roughly translated as “has multiplication.” Now we are left with the terms “budgeting” and “planning”. If we can agree that budgeting and planning are different, then we can now agree that driver-based budgeting and driver-based planning are also different.

Before we go onto driver-based planning, let’s conclude with a better definition of driver-based budgeting.

Driver-Based Budgeting Better Definition

A budget is driver-based to the extent that it makes use of multiplication and therefore incorporates automated calculations that assume certain factors are multiplied together. Driver-based budgeting is important since it can be used to “simplify, expedite, and improve the budgeting process” as noted earlier. So, if done properly, a driver-based budget will streamline and improve the budget process; however, keep in mind, we’re still talking about budgeting here. I am taking it as a given that the budgeting process does not improve your organization’s bottom line. Therefore, the success of driver-based budgeting is measured by time saved not better business decisions.

Preview of the new definition of Driver-Based Planning: The new definition of driver-based planning is most easily differentiated from driver-based budgeting by simply looking at the outcome: improved profitability and cash flow. Driver-based planning is not something we need to do faster; driver-based planning is something we need to do better, including more often to support best practices such as agile planning and rolling forecasts.

 

is-your-organization-ready-tomove

Comments

"Therefore, the success of driver-based budgeting is measured by time saved not better business decisions." 
 
Not to pick on budgeting, but this observation reminds me of David Letterman's classic quip: "We're hopelessly lost, but making great time!"
Posted @ Thursday, September 22, 2011 1:20 PM by Chris Vacano
I completely agree with the statements made in this article. Budgeting is still budgeting even if you speed it up. This does nothing to improve the fact, that the speedily consolidated numbers are still going to be wrong and thus meaningless in a matter of a short time.  
 
Yogi Berra once said: "The future ain't what it used to be."  
 
This isn't just funny but contains much truth, as predicting the future isn't as easy as it used to be either. And a detailed budget isn't going to get it done.
Posted @ Wednesday, September 28, 2011 6:32 PM by JP Mueller
JP, Thanks for agreeing!  
 
I love the Yogi Berra quote: "The future ain't what it used to be."  
 
It really resonates - in fact, Rand Heer uses this same quote in his Research Paper: "The Planning Maturity Curve: Where are you? Where do you want to be?" 
 
I hear questions from everyone out there like this: "Can I compare budget to actuals" or can I compare "forecast to budget"... 
 
The real question Yogi would have us ask is: "Can I compare forecast to forecast?" 
 
Since the future keeps changing, management needs to understand how is "what you're saying" now different than "what you told me last time." The question is directed at the FP&A team... 
 
If you are doing a monthly or quarterly rolling forecast, you will therefore need to compare forecasts side by side... 
 
Taking it a step further, you will need to compare scenarios for the same forecast (same forecast meaning date the forecast/s is/are updated) based on "best case vs baseline vs worst case" 
 
Taking that yet another step, you may even want to compare scenarios that represent strategies like: " Enter Int'l market " vs "Focus on US Market" 
 
That is really where the fun begins. 
 
The more steps you take it, the more "mature" your organization in the planning maturity curve framework...  
 
I bet Yogi would have us move across that planning curve! 
 
Thanks again for the great comment!
Posted @ Thursday, October 27, 2011 11:39 AM by Ben Lamorte
Ben, 
 
I think there are two elements to a "driver-based" definition. Multiplication is certainly one. The second, at least for me, associates with clarifying that all drivers are not created equal. One class of drivers is units; I refer to the second class as "planning factors." For example, using Rand's sw company illustration from his Agile Planning presentation, the only driver is # of services customers. All the other "drivers" (viz, conversion rate, hrs/customer, staff util rate, billing rate, staff hrs/mo and staff expenses/mo are planning factors.
Posted @ Saturday, June 02, 2012 9:06 AM by Alan Dybvig
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics