I was with my executive peer group recently, and we were working through a familiar problem together: too many priorities and not enough clarity for deciding which ones actually belong on the list.
It always seems to go this way. The whiteboard fills up fast. Everything is important, and everyone is fighting to get their initiative included. By the time you're done, you have twenty-three items on the list, three of them are contradictory, and five of them are contingent on something else getting done first.
It begged the question: If I gave my team a list like this, where would they even start?
One of the leaders in the room, Jordan Debilzan, offered a lens that cut through faster than any prioritization matrix I've seen. I've been using it since.
Is the initiative Foundation, Growth, or Continuous Improvement?
That's it. Three buckets. Everything belongs in one of them.
What is the three-bucket framework?
It's a prioritization framework that sorts every business initiative into one of three strategic buckets — and the bucket tells you the sequence. Foundation work has to be healthy before Growth delivers its full return. Continuous Improvement runs in the background, compounding results over time. That's the whole model.
Bucket 1: Foundation
This is the work nobody wants to fund, but everyone depends on. We're talking:
-
ERP systems
-
CRM adoption
-
Pricing architecture
-
Accurate costing models
-
Capacity data
These are the things that, when broken, create invisible drag on everything else. But when they're fixed, they allow everything else to actually work.
Foundation work doesn't close deals or show up in revenue. It doesn't make it onto board slides as an exciting new initiative. But it is the single biggest determinant of whether the items in your Growth bucket will deliver what they promise — or if they're just going to create more chaos at a higher volume.
The companies I work with that are scaling almost always have the same Foundation problem: they're running their pricing, their data, and their systems on assumptions that were set years ago and never updated. The business grew. The infrastructure didn't. And now every new initiative is fighting against a system that can't support it.
Bucket 2: Growth
New markets. Acquisitions. New channels, new verticals, new offerings. This is where the energy lives in every leadership meeting, every board conversation, and every offsite.
It's also the bucket that fails most visibly when Foundation is broken — because you're stacking new weight onto a system that was already straining. The acquisition looks great on paper, and then you try to integrate it and realize your pricing model doesn't translate, your ERP can't handle the new entity, and your team is duct-taping everything together.
Growth is the right goal. But it's only as strong as the Foundation underneath it.
Bucket 3: Continuous improvement
Pricing refinement. Lead time reduction. Margin tuning. Win rate improvement. Sales process iteration. These things don't have a launch date — they're ongoing, compounding, and almost always the highest-ROI work a company can do. They're also the first thing that gets cut when everyone's chasing the Growth initiatives.
Continuous Improvement isn't a nice-to-have. It's the flywheel that makes everything else more durable.
How to use this with your leadership team
When a new initiative surfaces — and one always will — the filter is simple: Which bucket is this, and is that bucket currently resourced?
If the board wants a market takeover (Growth), but your pricing architecture is broken and your CRM isn't adopted (Foundation), you now have a framing that isn't a defensive.
It's no longer, "We're not ready."
It's now, "We have an open Foundation dependency that puts this Growth bet at real risk. Here's what we close first, and here's the timeline."
How we're using this at Vye
When clients come to us, the ask usually sounds like one of these:
-
I need more leads
-
I need more awareness
-
I need to fix my pipeline
And our first move isn't to start building campaigns. It's to ask: where are you in the three buckets? (In the past I wasn't laying out the buckets clearly, but I will be now.)
Because if your brand doesn't speak to the right people, your website lacks a clear buying journey, and your messaging doesn't reflect what you actually do, then your Foundation isn't there. And that means leads won't convert, awareness won't compound, and pipeline will leak faster than you can fill it.
So we can sequence it the same way:
-
Foundation — Brand clarity, ICP targeting, website experience, and the core infrastructure that everything else depends on
-
Growth — Awareness, demand generation, pipeline creation, and market expansion
-
Continuous improvement — RevOps, pipeline acceleration, retention, and expansion revenue
The outcomes we drive for clients map directly to these buckets: brand visibility and market position, predictable lead flow, a sales and marketing engine that doesn't leak, and more revenue from the customers you already have.
The framework works because it's honest about sequence. You don't get to skip Foundation. And once you're clear on where you are, the priorities stop feeling overwhelming and start feeling obvious.
Give every initiative a bucket. Manage the buckets intentionally.
Frequently asked questions
What's the difference between a prioritization framework and a prioritization matrix?
A prioritization matrix scores individual tasks against fixed criteria (like impact vs. effort). A prioritization framework like this one organizes initiatives into strategic categories that define sequence — it's built for leadership-level resource allocation decisions, not task-level ranking.
How do I know if my business has a Foundation problem?
Common signs: growth initiatives that underperform without a clear reason, poor CRM adoption, pricing that doesn't reflect current costs, or messaging that doesn't resonate with your target buyer. If your team is constantly "putting out fires," a Foundation gap is usually underneath it.
Can an initiative belong in more than one bucket?
Sometimes. A CRM implementation might be Foundation work that also enables Growth. When that happens, assign it to the bucket that represents its primary constraint — the problem it has to solve first.
Does this framework apply to marketing specifically?
Yes. The demand for Growth work (more leads, more awareness) consistently overshadows Foundation gaps (weak brand, poor website conversion, unclear ICP) until the Growth investment fails to deliver. The three-bucket model helps explain why a particular investment won't work yet — and what has to happen first.
