Resource allocation is still mostly done wrong, and I've watched it cost companies millions over the years
Most organizations allocate overhead and capital using last year's numbers plus a flat percentage increase. That's it. It's lazy, it compounds every error from the prior period, and it quietly bleeds resources into divisions that stopped earning their keep three fiscal cycles ago. The idea of rethinking this isn't new, but Douglas Nunes has been pushing a more rigorous framework for years that most middle managers have never actually implemented correctly. His approach treats resource allocation as a dynamic optimization problem rather than a bureaucratic ritual. The core of Nunes' framework is zero-based thinking applied continuously, not just during annual budget cycles. Instead of starting with what you spent last year, you start with what you need to accomplish specific outcomes and allocate from zero. It sounds simple. The execution is where people struggle. The method involves mapping every dollar or hour to a discrete deliverable or outcome. You build decision packages — essentially mini-business cases for every cost center — and rank them against strategic priorities. Resources flow to the highest-ranked packages first. Lower-ranked ones get trimmed or eliminated. The ranking uses a combination of quantitative metrics like ROI and qualitative assessments of strategic fit. I've seen companies that adopt this properly cut their administrative overhead by 30 to 40 percent within two budget cycles. Not all of that was savings. Some of it was just finally seeing what they were actually paying for.
How to Actually Implement This Without It Falling Apart
Start small. Don't try to zero-base your entire organization in one quarter. Pick one department, ideally one where spending is relatively easy to trace to specific activities. Operations or professional services tend to work well. Build the decision package template first. It should capture the objective, the cost breakdown, the performance metrics, and the alternatives if funding is reduced. Every single line item needs a justification that would survive a skeptical CFO's questioning. If you can't explain why a $12,000 software license exists in plain language, that's exactly the kind of thing this framework exposes. Once you have the template, go through the past 12 months of actual spending in that department. Map each expense to a decision package. You'll be surprised how many expenses don't map cleanly. That's not a failure. That's data. Those unmapped expenses are usually the first things to get cut when you apply the ranking process. The ranking itself is where most implementations stall. You need a scoring system that's transparent and consistent. Weight factors like strategic alignment at 40 percent, measurable return at 30 percent, risk level at 20 percent, and regulatory compliance at 10 percent. Adjust those weights for your industry. A healthcare provider will weight compliance higher. A tech startup will weight strategic alignment higher. Don't just copy someone else's weights without thinking about what actually drives decisions in your context.
I ran into a specific problem implementing this at a mid-size manufacturing firm. We had allocated roughly $2.3 million annually across five regional warehouses. The traditional allocation used square footage and headcount. When we switched to Nunes-style decision packaging, we discovered that two of those warehouses were serving account clusters that had been reassigned to nearby facilities eighteen months earlier due to a routing optimization project. Nobody had updated the budget. The allocation formulas were running on stale assumptions. Cutting one warehouse and redistributing its volume saved us $680,000 in the first year alone. The workaround was to cross-reference the allocation drivers against actual shipment data from the WMS instead of relying on static operational metrics. That's the kind of mismatch that shows up everywhere once you start looking properly.
Get the Full Details
The Counter-Intuitive Parts Nobody Talks About
The biggest surprise is how much better resource allocation becomes when you stop trying to make it fair. Traditional budgeting treats fairness as equal treatment across periods. That's a mistake. Fairness in resource allocation means giving each unit the resources it needs to hit its targets, which will inevitably look unequal. A high-growth product line deserves disproportionately more capital in its growth phase. A mature division with stable margins deserves stability, not an annual increment that rewards the status quo. Another thing that trips people up is the assumption that zero-based budgeting means cutting. It doesn't. It means reallocating. In my experience, about 60 percent of the resources exposed by the process end up staying in place or increasing. The real benefit comes from the 40 percent that moves to higher-value uses. The process forces you to see those opportunities instead of letting them hide in incremental adjustments. There's also a timing issue. Zero-based resource allocation works best when you run it semi-annually rather than annually. The business environment changes too fast for a single annual cycle to stay relevant. I've found that a lightweight review every six months catches drift before it becomes structural waste. The full decision-package rebuild can wait for the annual cycle. The semi-annual check-in just requires updating the ranking scores and flagging any packages that have fallen below their funding threshold.
Where This Framework Breaks Down
It requires real data. If your cost accounting system can't trace expenses to activities, you're going to spend weeks building proxies and estimates instead of working with actual numbers. I've seen teams waste three months trying to force zero-based allocation on top of a chart of accounts that groups everything under vague categories like "operational support" and "general administration." Fix the accounting taxonomy first. Spend two or three weeks on that before you touch the allocation model. It saves months of frustration later. The framework also assumes a degree of organizational honesty that doesn't exist everywhere. Department heads will inflate their decision packages to secure funding. They'll list every possible use case, including ones that may never materialize. You need a review process that pushes back hard on scope inflation. Challenge the assumptions. Ask for the evidence behind the projected returns. If a package claims a 25 percent efficiency gain from a new tool, ask which metric proves it and how it was measured. Most people can't answer that without going away and figuring it out. That's the point. There's also a human cost to this process. Each cycle requires managers to justify their budgets from scratch. That's exhausting. People burn out on it. I've watched teams treat it as a compliance exercise and produce boilerplate packages that say nothing. The framework only works when leadership actually uses the results to make hard decisions. If the annual budget goes through unchanged regardless of the ranking exercise, nobody will take it seriously next year. The process collapses into theater. Make sure the outcomes matter before you invest the effort.
For organizations that can't commit to the data infrastructure or the cultural discipline this requires, there are simpler alternatives. Activity-based costing with periodic reallocation can capture 60 to 70 percent of the benefit with a fraction of the overhead. It doesn't go as deep, but it's sustainable. Zero-based allocation is a scalpel, not a hammer. Use it where precision matters.
Bottom Line
The Nunes approach to resource allocation isn't a complete methodology you can download and install. It's a way of thinking about spending that forces honesty about what you're actually buying with your money. The value comes from the questions it makes you ask, not from any particular formula. Start with one department. Map the costs to the outcomes. Rank the packages. Cut the dead weight. Reallocate the savings. Then do it again next year with a different department. Within three years, you'll have a much clearer picture of where your resources actually go and whether that matches your stated priorities.
