Content Prioritisation Framework.
A practitioner’s framework for deciding which content ideas to make and which to kill before they waste your time. Score the idea, defend the call, and keep a backlog that earns its place instead of becoming a graveyard.
I built this content prioritisation framework as a solo content marketer, where there’s no team to absorb a bad bet and every wrong call costs a week I don’t get back. It runs on three questions, scored fast, applied to every idea before it touches the calendar. It’s built for speed, a defensible call in minutes rather than a scoring ritual that takes longer than the writing would have, and it gives you a way to say no to people who outrank you without turning the no into a fight you lose. It’s based on production calls, not theory. The longer write-up, with the killed-content examples and the relationship tactics, lives in How I Decide What Not to Write.
Two halves, one decision.
Most prioritisation advice stops at the scoring matrix and leaves you to figure out the hard part on your own. This content prioritisation framework has two halves because the matrix is only useful if you can make its verdict stick.
Deciding what’s worth making
A repeatable read on every idea against impact, effort, and alignment. The goal is a fast directional call, scored high/medium/low rather than to false-precision decimals, so the decision gets made on outcomes instead of on whoever asked loudest or most recently.
Making the no survive contact
A score means nothing if the requester outranks you and won’t accept it. The second half is how you turn a scoring verdict into a trade-off conversation, sort a not-now idea from a dead one, and build a backlog you’ll actually reopen. This is the part that protects your credibility and your seat at the strategy table.
Impact, effort, alignment, in that order.
The three axes don’t carry equal weight, and the order you ask them in changes the answer. Impact is the gate. An idea that can’t clear it doesn’t earn the effort and alignment questions at all, which is how you keep the whole thing to minutes.
Impact: does this clear the gate?
The business-outcome question, asked first because a no here ends the conversation. If the idea can’t articulate what it’s supposed to achieve in one sentence, that’s the answer and you’ve spent thirty seconds finding it.
Effort: what does clearing it cost?
Only worth asking once the impact is there. Effort doesn’t disqualify a high-impact idea; it raises the bar on how high that impact needs to be to justify the spend.
Alignment: is this the right moment for it?
The axis that kills good ideas, which is why it comes last. A high-impact, low-effort piece can still be wrong if it pulls against current positioning or speaks to a persona you’ve deprioritised.
The scoring axes: what decides yes or no.
These are the three reads that produce the verdict. Keep them loose and directional. The value is in naming why you’re hesitating, not in the precision of the number.
Impact
Will this generate pipeline, support a deal already moving, rank for a query buyers actually search, or build authority in a space that matters to your positioning? A piece mapped to a buyer question at a defined funnel stage scores high. A piece that exists because “we should probably have something on this” scores low. The one-sentence test settles most of these on the spot.
Effort
Not just writing time. Research, stakeholder interviews, design dependencies, review cycles, the SME who takes three weeks to answer one question. A 2,000-word technical piece needing four interviews and two rounds of engineering review is a completely different bet from a sharp opinion piece you can draft in an afternoon, even when both score the same on impact.
Alignment
Does this fit the strategy you’re actually running right now? When my last company pivoted its ICP mid-quarter, a stack of perfectly good content ideas failed the alignment test overnight because they spoke to the audience we were moving away from. Good idea, wrong moment, killed.
Opportunity cost
The axis hiding behind the other three. Nothing gets made in a vacuum, so the question on any maybe is what drops off the calendar to make room for it. This is also the axis you hand to a stakeholder when you need the no to read as a trade-off rather than a refusal.
What the research says about wasted content.
The case for prioritising at all rests on how much content gets made and then never used. The numbers have been consistent for over a decade, which is the uncomfortable part.
of content produced by B2B marketing organisations goes unused, sitting on sales portals and website shelves
Forresterthe non-usage rate some companies reported back to Forrester after that figure was published, spending millions on content nobody viewed
Forresterof B2B organisations most successful at content marketing have a documented strategy, versus far fewer of the rest
Content Marketing InstituteCMI’s read on why this happens is that teams chase too many goals at once, which produces one-off content and is as bad as having no goal at all
Content Marketing InstituteThe throughline: the failure was never producing too little. It was producing too much of the wrong thing, with no system for deciding which thing.
The decision layer: making the no stick.
Scoring gives you the verdict. This layer is how the verdict survives a requester who outranks you and a backlog that wants to turn into a junk drawer.
Let the framework do the talking
Say no on personal judgment and you’ve invited an argument between your opinion and theirs, which you lose on rank. Say no on a transparent scoring system tied to outcomes you both already agreed on, and the fight changes shape. Now it’s the idea against the strategy, not you against them.
Reframe it as a trade-off
The strongest move is to make the opportunity cost visible and ask which option moves the needle more. Half the time the requester pulls the idea themselves once the cost is spelled out. The other half they argue the impact is higher than you scored it, and sometimes they’re right, and you update.
Make every no a strategic one
A strategic no names the axis the idea failed on, acknowledges what was good about it, and usually offers a path. A lazy no is a reflexive “no bandwidth” with nothing behind it, and it teaches people you’re a bottleneck to route around. The strategic kind keeps people bringing you ideas because they trust the process. I went deeper on this in why content ownership means owning the calls you make.
Curate the backlog, don’t hoard it
When you kill an idea, call it dead-dead or not-now on the spot. Dead-dead ideas get cut, because a backlog full of permanently bad ideas is noise that buries the good ones. Not-now ideas get parked with a note on what would have to change for them to become viable, so when the strategy shifts you can move fast on thinking that’s already done.
“I’ve scored this against what we’re trying to hit this quarter, and here’s where it comes out. If we make it, here’s what drops off the calendar to make room. Which one moves the needle more?”
The decision blueprint.
How the two layers run on a single idea, start to finish.
Gate on impact
Can you name what this is supposed to achieve in one sentence? No means stop here.
Price the effort
Total cost, not just word count. High effort raises the impact bar; it doesn’t auto-kill.
Check alignment
Right audience, right positioning, right moment. A yes on impact and effort still dies here if the answer is no.
Name the trade-off
If it’s a maybe, decide what it displaces. That comparison usually makes the call for you.
Deliver the verdict
Yes goes on the calendar. No gets the strategic treatment: the axis it failed, what was good, the path forward.
File the kill
Dead-dead gets cut. Not-now gets parked with its reopen condition attached.
How it fits into the content workflow.
The content prioritisation framework sits at the front of the pipeline, before anything gets scheduled, and it leaves a paper trail you can point to later.
Intake
Every request and idea hits the same three questions before it’s allowed near the calendar. No exceptions for seniority.
Score
Impact gate first, then effort, then alignment. Minutes, not meetings.
Decide
Yes, no, or not-now. The no gets reasoning attached on the spot.
Communicate
Strategic no for anything you’re killing, trade-off framing for anything a stakeholder is pushing.
Park
Not-now ideas go to the curated backlog with a reopen condition.
Revisit
When the ICP shifts or a launch ships, pull the parked ideas that now pass alignment and move.
What a strategic no looks like versus a lazy no.
Both are a no. Only one keeps you credible.
Lazy no: refusal with nothing behind it
- “We don’t have bandwidth”
- “That’s not really our thing”
- No axis named, no reasoning shown
- Reads as a bottleneck to route around
- Teaches people to stop bringing you ideas, or to go over your head
Strategic no: refusal the requester can accept
- Names the specific axis the idea failed on
- Acknowledges what was genuinely good about it
- Offers a path: park it, test it small, revisit on a trigger
- Tied to a strategy you both already agreed on
- Keeps the ideas, and the trust, flowing
Real content I’ve killed.
Two of these three were good ideas. They lost to better ones, which is the whole point.
The exhaustive glossary nobody asked for
Weeks of work, and when I scored it honestly the impact was low: the terms were well-covered elsewhere, it mapped to no active buyer question, and it would have ranked for nothing. Killed before I wrote a word, which saved two weeks.
The executive’s passion piece
A senior stakeholder wanted a long opinion piece on a macro trend they found fascinating and that was irrelevant to anyone in our buying cycle. Instead of the 2,000-word essay, I proposed a short social post to test whether the topic drew any interest at all. It got modest engagement, we learned the appetite wasn’t there, and we’d spent an hour instead of a week finding out.
The competitor-chasing content
A competitor ran a big push on a theme and the instinct was to respond in kind. The alignment test killed it: chasing their narrative meant playing on their turf and reinforcing their framing. We did something on our actual differentiator instead.
Where a content prioritisation framework breaks down.
The content prioritisation framework is simple. The ways people break it are predictable.
Defaulting to whoever asked loudest
With no system, the calendar becomes a record of other people’s impulses: the loudest request, the highest-ranking requester, the article someone read over the weekend. The work gets made, and most of it joins the 60 to 70% that goes unused.
Run every idea through the same three questions before it’s scheduled, regardless of who it came from. The framework outranks seniority.
Saying no on opinion instead of on outcomes
A no based on your personal judgment is an argument you lose to anyone who outranks you. It also reads as obstruction, which is how you get cut out of the decision entirely.
Score against outcomes you both already agreed on, and make the no the framework’s verdict rather than yours. Then it’s the idea versus the strategy, not you versus them.
Treating every no as final
Kill an idea outright and you lose the genuinely good ones that were just badly timed. A perfectly viable piece for a deprioritised persona was an early idea, and timing changes.
Sort every kill into dead-dead or not-now, and park the not-nows with the condition that would revive them. The backlog becomes a strategic reserve instead of a place ideas go to die.
Hoarding instead of curating the backlog
The opposite failure: everything rejected gets dumped into one list that nobody ever reopens, because finding the three usable ideas means digging through fifty dead ones.
Cut the dead-dead ideas entirely. A backlog you trust enough to reopen is worth more than a complete archive you never touch. This is part of treating content as a system, which I covered in why you need a content system, not a content team.
This content prioritisation framework optimises for a solo or lean-team reality, where saying no is survival and there’s no one to hand the overflow to. On a bigger team with spare capacity, the calculus shifts and some of the ruthlessness softens. The scoring is also deliberately directional, not precise, so it’ll feel too loose for anyone who wants a formula that spits out a ranked queue. That looseness is the feature, because the moment the scoring takes longer than the writing, you’ve rebuilt the bureaucracy this was meant to kill. What holds across every version I’ve run is the order: gate on impact, price the effort, check alignment, then defend the call so it sticks. The exact thresholds are yours to set.