I work at a service-based company with revenue of about $20 million, and I've been thinking recently about a question: What does a truly "collaborative budgeting" process look like? In practice, what different process options are there? We consider our budgeting process to be quite collaborative—many people are involved, and input is gathered broadly—but perhaps that's just my wishful thinking. This doubt partly stems from a recent comment by our Controller: she said that among all the budgeting processes she's participated in, ours is the "least collaborative." This puzzles me, because I didn't come down from the mountain alone with two stone tablets of budgeting rules, so why such an assessment? I look forward to your insights. Thanks.—Edward

What is "collaborative budgeting"?

"Collaborative budgeting" is not a standardized financial term, but rather a broad concept describing the degree of participation and interaction in the budgeting process. It generally refers to breaking away from traditional top-down or single-department-dominated models during budget preparation, allowing more stakeholders (such as department managers, project leaders, and frontline employees) to participate in goal setting, resource allocation, and data validation. However, a large number of participants does not equal a high degree of collaboration—the core of collaboration lies in the two-way flow of information, the substantive impact of opinions, and the transparency of decision-making.

Levels of collaboration: from "informing" to "co-creation"

Based on my experience, the degree of collaboration in a budgeting process can be divided into several progressive levels:

  • Informative: Senior management sets the budget and communicates it downward; employees are merely informed of the results with no room for participation.
  • Consultative: Management solicits input from various departments, but final decision-making power remains concentrated at the top; feedback may be adopted or ignored.
  • Participative: Department managers have a certain degree of autonomy in budget preparation, submitting drafts through meetings or systems and engaging in multiple rounds of negotiation.
  • Co-creative: Cross-functional teams jointly set goals, share data, and make decisions together; the budget becomes a product of collective intelligence, with feedback loops built into the process.

Your mention of "budgeting involving many people" may fall under the participative level, but the Controller's comment suggests the actual process may remain at the "informative" or "consultative" level—for example, although many are asked to provide numbers, there is a lack of genuine dialogue mechanisms, or final adjustments do not reflect grassroots input.

Process options: from traditional to agile

In practice, budgeting processes typically follow several models, with significant differences in their degree of collaboration:

  1. Traditional incremental budgeting: Based on the previous year's data, adjusted by a fixed ratio. Collaboration is limited to within departments, cross-departmental communication is minimal, and this easily leads to "budget games."
  2. Zero-based budgeting (ZBB): Every expenditure must be justified from zero, requiring departments to provide detailed rationales. This increases the intensity of participation, but without a unified framework, it may devolve into a pile of documents from "each fending for themselves."
  3. Rolling budgets: Forecasts are updated periodically, requiring continuous interaction between finance and business units. Collaboration is reflected in continuity over time, but if data systems are not interconnected, collaboration may remain superficial.
  4. Beyond Budgeting: Abandons fixed annual budgets in favor of dynamic targets and empowerment mechanisms. This requires a high degree of trust and information transparency, representing the ultimate form of collaboration, but it is difficult to implement.

A company of your size ($20 million) is typically suited to a participative or rolling budget approach, but the key lies in whether the process design provides "meaningful dialogue" rather than "ceremonial sign-offs."

Why does "many participants" not equal "collaboration"?

The Controller's comment may stem from the following common pitfalls:

  • Participation without empowerment: Employees are asked to provide data but have no authority to adjust priorities, and the final budget is unilaterally modified by senior management.
  • Information silos: Departments prepare independently without shared assumptions (such as sales forecasts or cost drivers), leading to conflicting figures.
  • Rigid processes: Timelines are too tight, leaving no buffer for negotiation and revision, reducing "collaboration" to "rushing to meet deadlines."
  • Cultural factors: If a "culture of silence" exists within the organization, even if meetings include many people, few actually speak up, or their opinions are not recorded.

To improve, it is recommended to start with the following: clarify budget goals and responsibilities, establish cross-departmental review meetings, use a unified data platform, and set up "challenge sessions" that allow assumptions to be questioned. Additionally, external consultants or "budget workshops" could be introduced to foster genuine dialogue.

Conclusion

Collaborative budgeting is not simply about "many hands make light work," but rather about using structured processes, transparent rules, and empowerment mechanisms to make budgeting a tool for organizational learning. You don't have to carry the stone tablets down the mountain alone—but perhaps you need to redesign the route up the mountain so that everyone carries a map and a compass.