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, back the call, and keep a backlog that earns its place instead of turning into a graveyard.
I built this content prioritisation framework as the only content person on a small marketing team, where nobody absorbs a bad bet and every wrong call costs a week I don’t get back. It runs on three quick questions applied to every idea before it touches the calendar, so you get a call you can stand behind in minutes instead of 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. Every rule in it came out of calls I’ve made on live calendars. 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 work out the hard part alone. 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 or low instead of to false-precision decimals, so you decide on outcomes instead of on whoever pushed hardest or asked 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. It’s the part that protects your credibility and keeps you in the strategy conversations.
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 keeps the whole call down 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 say 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?
It’s only worth asking once the impact is there, and high effort raises the bar on how much impact the idea needs to justify the spend instead of ruling it out.
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 that decide yes or no.
These three reads produce the verdict. Keep them loose and directional, because the value is in naming why you’re hesitating, and the score only needs to be rough.
Impact
Will this generate pipeline, support a deal already moving, rank for a query buyers search, or build authority on a topic your positioning depends on? A piece mapped to a buyer question at a defined funnel stage scores high, while one that exists because “we should probably have something on this” scores low, and the one-sentence test settles most of those on the spot.
Effort
Writing time is the smallest part of it, next to research, stakeholder interviews, design dependencies, review cycles and 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 different bet entirely 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 running right now? When a B2B SaaS company I worked at 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
It’s 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. It’s also the axis you hand a stakeholder when you need the no to read as a trade-off instead of 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, and on how stretched the people making it already are. The waste figures have been around for over a decade, which is the uncomfortable part.
of content produced by B2B marketing organisations goes unused, by SiriusDecisions’ estimate (now part of Forrester)
Forresterthe share of their content some companies reported going unused, after that estimate was published
Forresterof B2B marketers named lack of resources as their top content marketing challenge, the most cited answer
Content Marketing Institute, 2025B2B marketers say measuring content effectiveness is one of their top challenges, and if nobody measures content, nobody kills it either
Content Marketing Institute, 2026The throughline: teams that are short on people keep producing too much of the wrong content, with no system for deciding what’s right.
How the decision layer makes the no stick.
Scoring gives you the verdict, and this layer is how it 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 judgement and you’ve invited an argument between your opinion and theirs, which you lose on rank, but put the no on a scoring system everyone can see, tied to outcomes you both already agreed on, and it becomes the idea against the strategy, with you out of the firing line.
Reframe it as a trade-off
The strongest move is to make the opportunity cost visible and ask which option does more for the goal. Half the time the requester pulls the idea themselves once you spell out the cost, and the rest of the time they argue the impact is higher than you scored it, which it sometimes is, so 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, so people keep bringing you ideas because they trust the process. A lazy no (a reflexive “no bandwidth” with nothing behind it) teaches them you’re a bottleneck to route around. 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. Cut the dead-dead ones, because a backlog full of permanently bad ideas buries the good ones, and park the not-nows with a note on what would have to change for them to work, 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? If not, stop here.
Price the effort
Total cost, well beyond word count. High effort raises the impact bar without killing the idea automatically.
Check alignment
Right audience and positioning, at the 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, and no gets the strategic treatment: the axis it failed, what was good, the path forward.
File the kill
Cut the dead-dead and park the not-now 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, with no exceptions for seniority.
Score
Impact gate first, then effort, then alignment. Minutes, never meetings.
Decide
Yes, no or not-now, with the reasoning attached to any no on the spot.
Communicate
A 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, and 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 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
Content I’ve killed.
Two of these three were good ideas that lost to better ones, which is the whole point.
The exhaustive glossary nobody asked for
Weeks of work, and when I scored it the impact was low: the terms were well covered elsewhere, it mapped to no active buyer question, and it would have ranked for nothing. I killed it 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 nobody in our buying cycle cared about. 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 finding out instead of a week.
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, because chasing their narrative meant playing on their turf and reinforcing their framing. We made a piece on our own differentiator instead.
Where a content prioritisation framework breaks down.
The content prioritisation framework is simple, and the ways people break it are predictable enough to list.
Defaulting to whoever pushed hardest
With no system, the calendar becomes a record of other people’s impulses: the pushiest request, the highest-ranking requester, the article someone read over the weekend. You make the work, and most of it joins the 60 to 70% that goes unused.
Run every idea through the same three questions before it’s scheduled, whoever it came from. The framework outranks seniority.
Saying no on opinion instead of on outcomes
A no based on your personal judgement is an argument you lose to anyone who outranks you, and it 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 instead of yours. The idea is then up against the strategy, and nobody has to win an argument with you personally.
Treating every no as final
Kill an idea outright and you lose the good ones that were only badly timed. A piece written for a persona you’ve deprioritised can become the right piece the quarter that persona comes back.
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: you dump everything rejected into one list 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. It’s 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 is built for a solo or lean-team reality, where saying no is survival and there’s nobody 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, 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 back the call so it sticks. The exact thresholds are yours to set.