An idea backlog is the single place where every possible post lives before anyone decides to publish it. It is not a calendar and it is not a content plan. It is the raw inventory: the half-formed angles, the customer questions, the screenshots of competitor posts, the line a salesperson said on a call that made a prospect nod. The job of a backlog is capture and organization, so that when planning day arrives, you are choosing from a stocked shelf instead of staring at a blank composer.
Most teams skip this layer entirely. They jump straight from “we need to post” to “what should we post,” and that gap is where consistency dies. A backlog closes it.
Why capture is the bottleneck, not creativity
The common complaint is “we have run out of ideas.” That is almost never true. The real problem is that ideas arrive at inconvenient moments and are never written down. A support agent answers the same question for the fifth time this week. A founder reads a comment that perfectly frames an objection. A case study lands. None of it gets captured, so by the time someone sits down to plan, all of that signal has evaporated and the team is genuinely starting from zero.
A backlog fixes a capture problem before it tries to fix a creativity problem. The discipline is simple: when an idea appears, it goes into one inbox immediately, in one sentence, with no pressure to be good yet. Filtering comes later. Capture and judgment are separate jobs, and mixing them is why most idea lists die after two weeks.
What belongs in a backlog entry
A backlog is only useful if entries carry enough context to be revived weeks later. A naked title like “pricing post” tells future-you nothing. Each entry should hold a handful of fields so it can be sorted, filtered and picked without a meeting.
| Field | Purpose | Example |
|---|---|---|
| One-line idea | The angle in plain language | “Why we charge per seat, not per post” |
| Source | Where it came from | Sales call, 12 March |
| Audience | Who it speaks to | Agency owners evaluating tools |
| Proof | What makes it credible | Pricing page, two client quotes |
| Pillar | Which theme it serves | Transparency |
| Status | Where it sits | Raw / shortlisted / scheduled / parked |
| Priority | How urgent or strong | High / medium / someday |
That last pair, status and priority, is what separates a backlog from a junk drawer. Without them you get hoarding: hundreds of entries, none of them moving. With them, the backlog becomes a pipeline.
How to tag so the backlog stays findable
Tagging is the difference between a backlog you mine and a backlog you avoid. Keep the tag set small and stable. Three dimensions are usually enough:
- Theme or pillar so you can balance the mix and avoid posting six product-pushy ideas in a row. Map these to your social media content pillars .
- Funnel stage so you can pull awareness ideas for a quiet week and bottom-of-funnel ideas before a launch.
- Effort so you can grab a quick text post when time is short and reserve carousels and video for when it is not.
Resist the urge to invent a fourth and fifth dimension. Every extra tag is a decision someone has to make at capture time, and friction at capture is what empties a backlog.
Sourcing ideas you already own
The richest backlog is fed from material the business already produces. You do not have to invent angles when your own assets are full of them. Strong recurring sources:
- Customer questions. Every repeated question is a post. Pull from your own FAQs , support tickets and sales objections.
- Existing pages. Product pages, pricing pages and case studies each carry several distinct angles. A single case study can seed an outcome post, a process post and a quote post.
- Old high-performers. Posts that worked once can be reframed. Add a “refresh” tag and revisit them when the backlog runs thin.
- Comments and replies. What people argue with or ask for under your posts is next month’s content.
This is the same instinct behind turning website content into social posts : the source material exists, it just needs to be captured as discrete, taggable ideas.
Keeping the backlog from becoming a graveyard
Backlogs fail in two opposite ways. Some stay empty because nobody captures. Others bloat into a thousand stale entries nobody trusts. A few habits keep it healthy:
- Groom monthly. Spend twenty minutes archiving anything older than ninety days that never moved past “raw.” If it has not earned a slot in three months, it probably will not.
- Cap the shortlist. Only a handful of ideas should ever sit in “shortlisted” at once. The shortlist is what feeds your content calendar ; keeping it short forces real choices.
- Promote, do not duplicate. When an idea is picked, change its status rather than copying it into a separate doc. One source of truth.
A well-groomed backlog of forty live ideas beats a chaotic dump of four hundred dead ones every time.
Where Utin fits
Utin is being built to feed this backlog automatically. It scans your website and turns pages, FAQs and proof into tagged, source-linked idea entries, so the capture step happens without anyone remembering to do it. From there the strongest ideas flow into drafts and a calendar. If you want to follow the build, you can register interest for the early pilot.
A backlog answers the question “what could we post.” A separate but related practice answers “what should we test, and what did we learn.” For that, read the social media experiment backlog , which treats ideas as hypotheses rather than inventory.