Scroll Top

What Does Backlog Mean? Six Business Senses

Updated September 2026 · Written and maintained by the Progression Agency strategy team

Backlog means work that has been committed but not yet completed. That single definition covers six quite different business situations, and two of them point in opposite directions: a rising sales backlog is usually good news, while a rising support backlog is always bad news. This page defines each sense, explains why the count is the least useful number you can report about one, sets out how to work a backlog down in an order that actually holds, and covers the words backlog gets confused with — queue, pipeline, roadmap and technical debt.

The short answerA backlog is accumulated work that is committed but not yet done. In sales and manufacturing it is orders won and not yet delivered, and it is an asset. In operations, support and product it is work owed and not yet reached, and it is a liability. The number to report is not the count — it is the aging: how old the oldest item is, and what the median age is. Two teams reporting an identical backlog count can be in completely different situations, and only the age distribution tells them apart. And a backlog whose inflow exceeds its throughput cannot be cleared by working harder, which is the single most common mistake made with one.

Backlog, in five points
Backlog means accumulated work that is committed but not yet completed. In sales it is revenue you have won and not delivered — an asset. In operations it is work you owe and cannot reach — a liability. Same word, opposite implications.
Backlog — Committed, not completed. Work owed but not yet done.
Sales — An asset. Revenue won, not yet delivered.
Ops — A liability. Work owed you cannot reach.
Product — A list of intent. Not a commitment, despite the name.
Support — Always bad news. Tickets waiting on you.
Ask — Which backlog?. The word alone reports nothing.

Backlog meaning, in one sentence

Answer first: a backlog is the accumulated body of work that has been committed to but not yet completed. The word carries no judgement on its own — whether a backlog is good or bad depends entirely on which of the six senses below you mean.

Where the word comes from

The term originally referred to a large log placed at the back of a fire to burn slowly, and it carried the sense of a reserve held back. The modern business usage keeps the reserve idea and loses the fire: a stock of work held, waiting, not yet consumed.

Backlogs meaning in the plural

Answer first: identical. Backlogs, backlog, backlogs means, backlog means — these are the same word being searched with different grammar, not different concepts. The plural is used when several separate backlogs exist, which in most organizations they do: a sales backlog, a support backlog and a product backlog can all exist at once and behave completely differently.

The six senses of backlog

Answer first: sales or order backlog, operations backlog, support backlog, product backlog, financial or billing backlog, and technical debt. They share the definition and almost nothing else, including whether a rise is good news.

The six senses of backlog
Order backlog rising is usually good news; support backlog rising is always bad news. Anybody reporting ‘the backlog’ without saying which one is reporting nothing.
Six senses, defined
SenseWhat is waitingRising isWho watches itThe health measure
Sales / order backlogOrders won, not yet deliveredUsually goodFinance and leadershipDeliverability against capacity
Operations backlogWork owed, not yet performedBadOperationsAging and inflow versus throughput
Support backlogTickets received, not yet resolvedAlways badSupport leadershipAge of oldest open ticket
Product backlogFeatures considered, not builtNeutral to badProduct teamsWhether anything ever leaves it
Billing backlogWork delivered, not yet invoicedBadFinanceDays between delivery and invoice
Technical debtQuality work deferredBad, slowlyEngineeringRate of accumulation versus repayment

The conclusion: when somebody says ‘the backlog is up’, the first question is which one. A rising order backlog and a rising support backlog are opposite pieces of news and the same three words describe both.

Sales and order backlog

Answer first: orders a company has won but not yet delivered or recognized as revenue. In manufacturing, construction and enterprise software this is a genuine forward indicator and it is frequently reported to investors, because it says something about revenue already secured.

When a sales backlog stops being good news

When it grows because delivery cannot keep up rather than because sales are strong. A large order backlog with lengthening delivery times is a capacity problem wearing a growth costume, and customers experience it as lateness regardless of how it appears on a chart.

Operations backlog

Answer first: work the organization owes and has not reached. Fulfillment, installations, maintenance, processing. Unlike sales backlog, this is unambiguously a liability, and its cost compounds because delayed work generates its own follow-up work — chasing, apologizing, re-scheduling.

Support backlog

Answer first: tickets received and not resolved. This is the sense where aging matters most, because customer tolerance decays sharply with time and an old unresolved ticket generates more contact rather than less.

Product backlog

Answer first: a list of features, fixes and ideas a product team might build. It is the sense most often misused, because in many organizations it has become a place items go to avoid somebody having to say no to them. That is not a backlog; it is an archive with optimistic labeling.

Billing backlog

Answer first: work delivered but not yet invoiced. It is quietly expensive, because every day between delivery and invoice is a day of financing somebody else’s business, and it is usually invisible until somebody looks for it deliberately.

Technical debt

Answer first: quality and maintenance work deferred in favor of speed. It is a specific kind of backlog rather than a synonym for one, and its distinguishing feature is that it accrues interest — deferred work makes future work slower, which generates more deferral.

Why aging matters more than count

Answer first: because two teams with an identical backlog count can be in completely different situations, and only the age distribution distinguishes them. Report the oldest item and the median age; the count on its own is close to meaningless.

Why aging matters more than count
Illustrative, not measured. Two teams reporting an identical backlog count can have completely different situations, and only the age distribution distinguishes them.
Age — The number that matters. Not the count.
Inflow — Track it. Arrivals per period.
Throughput — Track it too. Completions per period.
Gap — Inflow minus throughput. If positive, the backlog grows regardless of effort.
Median — Age, not average. Averages hide the stuck tail.
Oldest — Report it every time. It is the most honest single number.
What each backlog measure tells you
MeasureWhat it tells youWhat it hidesReport it?
Total countVolume waitingEverything about urgencyOnly alongside aging
Age of oldest itemWhether anything is stuckVolumeAlways
Median ageWhether the tail is typical or exceptionalThe extremesAlways
Items over 90 daysThe size of the stuck tailRecent flowAlways
Inflow per periodWhether the problem is arriving fasterCapacityAlways
Throughput per periodWhat you can actually clearDemandAlways
Inflow minus throughputWhether it is growing or shrinkingCompositionAlways — this is the key number

The conclusion: the last row is the number that decides whether a backlog is solvable with effort. If arrivals exceed completions, no amount of working harder clears it — the arithmetic simply moves the date at which it becomes unmanageable.

How to work a backlog down

Answer first: measure aging, stop the inflow, separate items by cause, delete the dead ones, sequence what remains by one consistent rule, then fix the intake. In that order — most teams start at sequencing and wonder why it does not hold.

How to work a backlog down
Step two is the one that decides everything. If arrivals exceed completions, adding effort moves the date and not the outcome.
Stop — The inflow first. Or effort just moves the date.
Delete — The dead items. They cost attention on every read.
Sequence — One rule, held. Oldest-first or value-first, decide once.
Cap — The size. A hard limit forces the delete conversation.
Review — Monthly. Or the list rots quietly.
Fix — The intake. Or you repeat this next quarter.

Step one: measure aging, not count

Before anything else, produce the age distribution. It converts ‘we have four hundred items’ into ‘we have three hundred and forty items under a week old and sixty that have been open for more than a year’, which are two entirely different problems requiring two entirely different responses.

Step two: stop the inflow

If inflow exceeds throughput, the backlog grows regardless of effort. Reducing inflow means either preventing the work arriving — fixing the cause of the tickets, tightening what gets accepted — or increasing throughput permanently. A temporary push clears the visible pile and the pile returns.

Step three: separate by cause

Blocked — Waiting on something external. Not the same as undone.
Waiting — On a person or a decision. Chase the person, not the item.
Undone — Genuinely not started. The only category that needs capacity.
Dead — Nobody will ever do it. Delete it; archiving is not deleting.
Duplicate — Recorded twice. Merge, do not close silently.
Unclear — Nobody knows what it means. Clarify or delete; do not carry it.

Four categories, and only one of them needs capacity: blocked on something external, waiting on a named person, genuinely not started, and should be deleted. Teams routinely apply capacity to all four, which is why backlog pushes exhaust people and achieve less than expected.

Step four: delete the dead

Answer first: deletion is a legitimate completion and treating it as failure is the main reason backlogs grow forever. An item nobody will ever do costs attention every single time somebody reads the list, and that cost is paid weekly for years.

Step five: sequence by one rule

Oldest-first or highest-value-first. Both are defensible; alternating between them is not, because it produces a list where the ordering logic is unknowable and everybody negotiates their own item upward.

Step six: fix the intake

Otherwise the same backlog reassembles within a quarter. The intake fix is usually either a definition of what gets accepted, a required piece of information at submission, or removing the underlying cause that generates the work.

Backlog, queue, pipeline, roadmap and WIP

Answer first: these are five different things and they get used interchangeably. A queue is ordered, a pipeline is not yet committed, a roadmap has dates, work in progress is being done now, and a backlog is committed work waiting.

Queue — Ordered, first in first out. A backlog is not necessarily ordered.
Pipeline — Not yet won. A backlog is already committed.
Roadmap — Intent over time. A backlog has no dates.
WIP — Being worked now. A backlog is waiting.
Debt — Deferred quality work. A subset of backlog, not a synonym.
Wish list — Not a backlog. However often it is called one.
Five terms, distinguished
TermCommitted?Ordered?Being worked?Has dates?
BacklogYesNot necessarilyNoNo
QueueYesYes, by ruleNoNo
PipelineNo — still being wonLoosely, by stageNoSometimes forecast
RoadmapPartiallyBy themeNoYes
Work in progressYesN/AYesUsually
Wish listNoNoNoNo

The conclusion: the distinction that matters most in practice is backlog versus wish list. A backlog contains work somebody intends to do. A wish list contains work somebody did not want to refuse. Mixing the two makes the backlog unusable for planning, which is exactly what has happened in most product organizations.

Backlog by industry

Answer first: the word means something specific and different in each of these, and the metric that matters differs with it.

Manufacturing — Orders not yet shipped. Reported to investors as an asset.
Construction — Contracted work not yet built. A forward revenue indicator.
Software — Features not yet built. A list of intent, not commitment.
Support — Tickets not yet resolved. Aging is the health measure.
Legal — Matters not yet concluded. Capacity constrained.
Recruitment — Roles not yet filled. Time-to-fill is the real metric.
What backlog means, by industry
IndustryBacklog meansReported toThe number that matters
ManufacturingOrders received, not yet shippedInvestors, as a forward indicatorBacklog months of production
ConstructionContracted work not yet builtInvestors and lendersBacklog in months of revenue
Enterprise softwareContracted revenue not yet recognizedFinance and investorsRemaining performance obligations
Support and serviceTickets not yet resolvedOperations leadershipAge of oldest open item
Product developmentFeatures and fixes not yet builtInternal onlyWhether anything ever leaves it
Legal and professionalMatters not yet concludedPartnersCapacity utilization
RecruitmentRoles open, not yet filledLeadershipTime to fill
HealthcarePatients waiting for a procedureRegulators and boardsLongest wait, not average wait

Note the last row in particular. In contexts where waiting has a human cost, the longest wait is the honest figure and the average wait is the flattering one — which is why the average is the one usually quoted.

Is a backlog good or bad?

Answer first: it depends on whether the backlog represents demand you have won or work you owe. Won-and-undelivered is an asset with a capacity risk attached; owed-and-unreached is a liability with a customer-experience cost attached.

Signs a backlog is healthy or not
The last row is the commonest product-team failure: a backlog that has become a place items go to avoid being said no to. That is not a backlog, it is an archive with optimistic labeling.
  1. A sales backlog is good until delivery times lengthen, at which point it becomes a capacity problem that customers experience as lateness.
  2. An operations backlog is bad and gets worse than linearly, because delayed work generates chasing, apologizing and rescheduling work of its own.
  3. A support backlog is unambiguously bad, and its cost is measured in customers lost rather than in tickets outstanding.
  4. A product backlog is neutral if items leave it and bad if they do not. A product backlog where nothing is ever deleted is a record of indecision.
  5. Technical debt is bad slowly, which is why it is deferred, and which is why it eventually stops being deferrable.

The life of a backlog item

The life of a backlog item
Deletion is a legitimate outcome and treating it as failure is why backlogs grow forever. An item nobody will ever do costs attention every time somebody reads the list.

The stage nobody measures is ‘blocked’. Most backlog items spend the majority of their life waiting on something or someone rather than waiting for capacity, and a team that measures only capacity will keep adding people to a problem that is not about people.

A complete question set on backlogs

Answer first: the questions people actually ask about backlogs, each answered directly. If you are trying to make sense of one in your own organization, these are the answers to have to hand.

Definition and scope

Is a backlog the same as being behind schedule?

No. A backlog can be entirely on schedule — an order backlog with delivery dates being met is simply committed work waiting its turn. Being behind means the committed dates are not being met, which is a different problem.

Can a backlog be zero?

In support and operations, briefly, and it usually indicates either very low demand or excess capacity. In sales a zero order backlog means nothing is sold ahead, which for most businesses is worse news than a large one.

Is a backlog an asset or a liability?

An order backlog is closer to an asset — revenue secured, not yet delivered. An operations or support backlog is a liability — work owed, not yet done. The word alone does not tell you which.

Does a backlog appear on financial statements?

Not as a line item in the way inventory does, but related concepts do — remaining performance obligations under revenue recognition standards, for instance. Companies frequently discuss backlog in commentary alongside statements rather than within them.

Measurement

What is backlog burn rate?

The rate at which backlog is converted into completed work, usually expressed per period. Compared against inflow, it tells you whether the backlog is growing or shrinking, which is the only question that matters at the start.

What is backlog coverage?

How long the current backlog would sustain output at current throughput — frequently expressed in months. In manufacturing and construction it is one of the standard forward indicators.

Should I measure backlog in items or in effort?

Effort, wherever items vary widely in size. Four hundred items where one takes a day and another takes a month is not a meaningful count, and effort-weighted backlog is the honest version.

How do I spot a backlog that is being gamed?

Look for items closed and immediately reopened, items reclassified into a different queue, and a count that falls while the age of the oldest item rises. All three reduce the reported number without reducing the work.

Product backlogs specifically

How big should a product backlog be?

Small enough that somebody can read all of it. Once it exceeds that, items at the bottom are effectively invisible and the list has stopped functioning as a decision tool.

What is backlog grooming or refinement?

The regular practice of reviewing items, clarifying them, re-ordering them and deleting the ones that will never be built. The deletion half is the part most often skipped and the part that keeps the list usable.

Should old product backlog items be deleted or archived?

Deleted, in practice. Archiving usually means moving them somewhere nobody looks, which is deletion with extra steps and a false sense of preservation. If an idea matters it will be raised again.

Why do product backlogs grow forever?

Because adding an item is a way of not saying no. It resolves the immediate conversation at no apparent cost, and the cost is paid later by everybody who has to read the list.

Practical management

Who should own the backlog?

One person for the list as a whole, plus a named owner for each item. Shared ownership of a backlog produces a list nobody prunes, because pruning somebody else’s item feels presumptuous.

Should I cap the size of a backlog?

It is a useful forcing device. A hard cap means adding something requires removing something, which converts the vague intention to prioritize into an actual decision made at the moment of addition.

What is a reasonable aging target?

It depends entirely on the sense and the sector, so set your own from your own data rather than borrowing one. A useful starting discipline is that nothing should be older than the period in which you review the backlog.

How do I explain a growing backlog to leadership?

With the inflow and throughput figures rather than the count. ‘Arrivals exceeded completions by sixteen a week for eleven weeks’ is a diagnosis; ‘the backlog is up’ is a complaint, and it invites the wrong response.

Common mistakes with backlogs

Mistakes and what to do instead
MistakeWhy it costsInstead
Reporting the count onlyHides whether anything is stuckReport oldest and median age too
Adding effort without stopping inflowClears the pile; the pile returnsFix inflow first
Never deleting anythingDead items cost attention weeklyDelete, do not archive indefinitely
Using the backlog as a wish listMakes it useless for planningSay no, or record it elsewhere
Alternating sequencing rulesEverybody negotiates their item upwardOne rule, held
Averaging the waitHides the stuck tailReport the longest wait
Treating blocked and undone the sameApplies capacity where it cannot helpSeparate by cause first
No owner per itemItems age without anybody responsibleAn owner and a decision date each

What causes backlogs in the first place

Answer first: four causes, and only one of them is a capacity problem. Demand exceeding capacity, work arriving faster than it can be triaged, items blocked on something external, and work that should never have been accepted. Adding people solves the first and none of the others.

Four causes and their actual fixes
CauseWhat it looks likeThe fixWhat does not work
Genuine capacity shortfallSteady inflow, throughput below it, few blocked itemsMore capacity, permanentlyA temporary push
Triage failureLarge volume of unclassified itemsA triage step with an ownerWorking the list in arrival order
BlockingItems old but untouched, not for lack of effortChase the blocker, not the itemAdding capacity
Accepting work that should be refusedBacklog full of items nobody will doA definition of what gets acceptedPrioritizing harder
ReworkThe same item returning repeatedlyFix the quality problem upstreamClosing it faster
SeasonalityPredictable peaksPlan capacity around the peakTreating each peak as a surprise

The conclusion: diagnose before you resource. Most backlog interventions add capacity because that is the visible lever, and in three of the six rows above capacity is not the constraint.

Backlogs and customer experience

Answer first: customers do not experience your backlog count; they experience their own wait. That is why the longest wait is the honest metric and the average is the flattering one, and why communication about a wait changes the experience of it more than a marginal reduction in the wait itself.

  • Tell people where they are. An acknowledged wait is tolerated far better than a silent one, and it reduces the chasing contacts that inflate the backlog further.
  • Give a date, not a platitude. ‘Within ten working days’ is usable; ‘as soon as possible’ generates a follow-up.
  • Update when the date changes, before it passes rather than after.
  • Handle the oldest items specifically. The stuck tail is where complaints and lost customers come from, and it is invisible in the average.
  • Measure chase contacts. They are a direct readout of how well you are communicating, and they are pure additional inflow caused by your own silence.

Reporting a backlog honestly

Answer first: count, oldest item, median age, items over ninety days, inflow, throughput, and the difference between the last two. Seven numbers, one line each, and together they tell the whole story that the count alone conceals.

Support backlog, week ending [DATE]
Open items: 412
Oldest open item: 214 days
Median age: 4 days
Items over 90 days: 38
Inflow this week: 260
Throughput this week: 244
Net change: +16

Read that example and the situation is immediately legible: current flow is roughly healthy, there is a stuck tail of thirty-eight items that has been ignored, and the backlog is growing slowly because inflow exceeds throughput by sixteen a week. None of that is visible in ‘412 open items’, which is what most reports contain.

Related reading on the surrounding measurement discipline: how to calculate a success rate and what retention means.

Updated August 2026. The worked examples and distributions on this page are illustrative figures chosen to show the shape of the problem, not measured findings from any organization, and they are labeled as such where they appear.

Reporting a backlog nobody can act on?

Send us how it is currently measured. We will tell you what the count is hiding, whether the inflow or the throughput is the real problem, and how to report it so the answer is legible in one line.

Get a second opinion

Measurement and operations, from the people who publish the platforms

Publicly available talks from Google Ads, Think with Google, Ad Age, HubSpot, Ahrefs and Neil Patel on measurement and reporting discipline — the habits that make any operational number trustworthy. None of these are ours; each is credited to its channel by name and upload date, every identifier was verified live before publication, and each tile loads its player only when you click it.

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Social, content and brand

By industry and by situation

Backlogging: meaning, and what the verb form signals

Backlogging is the verb form, and it carries a meaning the noun does not. To backlog something is to place it deliberately into the queue rather than act on it now — a decision, not an accident. In software and operations teams the word is often used defensively: backlogging a request is how a team says no without saying no, and a backlog that grows faster than it is worked is a record of decisions nobody wanted to make out loud. In inventory and manufacturing the same word describes orders accepted but not yet fulfilled, where backlogging is a deliberate policy — you take the order now and produce later. The distinction worth holding onto is that a backlog is a state and backlogging is a choice, which is why the second is the more revealing word when you hear it in a status meeting.

Frequently asked questions

What does backlog mean?
A backlog is accumulated work that has been committed to but not yet completed. The word carries no judgement on its own — a sales backlog of orders won and undelivered is usually good news, while a support backlog of unresolved tickets is always bad news, and the same three words describe both.
What does backlogs mean in the plural?
The same thing. Backlogs, backlog, backlogs means and backlog means are the same concept searched with different grammar. The plural is used when several separate backlogs exist at once, which in most organizations they do — a sales backlog, a support backlog and a product backlog can coexist and behave completely differently.
Is a backlog good or bad?
It depends on whether it represents demand you have won or work you owe. Won-and-undelivered is an asset with a capacity risk attached. Owed-and-unreached is a liability with a customer-experience cost attached. A rising order backlog and a rising support backlog are opposite pieces of news.
What is a sales or order backlog?
Orders a company has won but not yet delivered or recognized as revenue. In manufacturing, construction and enterprise software it is a genuine forward indicator of secured revenue and is frequently reported to investors. It stops being good news when it grows because delivery cannot keep up rather than because sales are strong.
What is a product backlog?
A list of features, fixes and ideas a product team might build. It is the sense most often misused, because in many organizations it has become a place items go to avoid somebody having to say no to them. A product backlog where nothing is ever deleted is a record of indecision rather than a plan.
What is the difference between a backlog and a queue?
A queue is ordered by an explicit rule — usually first in, first out. A backlog is committed work waiting, and it is not necessarily ordered at all. Treating a backlog as a queue implies a sequencing discipline that most backlogs do not have.
What is the difference between a backlog and a pipeline?
A pipeline contains work not yet won — opportunities still being pursued. A backlog contains work already committed. Confusing the two produces revenue forecasts that count the same work twice, or capacity plans that assume commitments that do not exist.
What is the difference between a backlog and a roadmap?
A roadmap has dates and themes; a backlog has neither. A roadmap says roughly when things will happen; a backlog says what is waiting. A backlog presented as a roadmap creates expectations about timing that nobody committed to.
Is technical debt a backlog?
It is a specific kind of backlog rather than a synonym for one — quality and maintenance work deferred in favor of speed. Its distinguishing feature is that it accrues interest: deferred work makes future work slower, which generates more deferral, which is why it eventually stops being deferrable.
Why is backlog aging more important than the count?
Because two teams reporting an identical count can be in completely different situations. One may have four hundred items all under a week old, which is healthy flow. Another may have four hundred of which sixty have been open for over a year, which is a stuck tail. Only the age distribution tells them apart.
What backlog metrics should I report?
Seven: total count, age of the oldest item, median age, number of items over ninety days, inflow per period, throughput per period, and the difference between inflow and throughput. That last number decides whether the backlog is solvable with effort at all.
How do I reduce a backlog?
Measure aging first, stop the inflow second, separate items by cause third, delete the dead ones, sequence what remains by one consistent rule, then fix the intake. Most teams start at sequencing, which is why their backlog pushes clear the visible pile and the pile returns within a quarter.
Why can’t I clear a backlog by working harder?
If inflow exceeds throughput, the backlog grows regardless of effort — the arithmetic simply moves the date at which it becomes unmanageable. A temporary push clears the visible pile while arrivals continue, and the pile reassembles. Reducing inflow or permanently increasing throughput are the only two real options.
Should I delete items from a backlog?
Yes, and deletion is a legitimate completion rather than a failure. An item nobody will ever do costs attention every time somebody reads the list, and that cost is paid weekly for years. Treating deletion as failure is the main reason backlogs grow indefinitely.
How do I categorize backlog items?
Four categories, of which only one needs capacity: blocked on something external, waiting on a named person, genuinely not started, and should be deleted. Teams routinely apply capacity to all four, which is why backlog pushes exhaust people and achieve less than expected.
What is a backlog in manufacturing?
Orders received but not yet shipped, usually reported as backlog months of production — how long it would take to clear at current output. It is treated as a forward indicator of revenue, and a lengthening one signals either strong demand or a capacity constraint depending on what else is moving.
What is a backlog in construction?
Contracted work not yet built, normally expressed in months of revenue. It is reported to investors and lenders as an indicator of secured future work, and it is one of the more meaningful forward indicators in the sector because the contracts are already signed.
What is a support backlog and how should it be measured?
Tickets received and not yet resolved. The measure that matters is the age of the oldest open item rather than the count, because customer tolerance decays sharply with time and an old unresolved ticket generates more contact rather than less — it actively increases inflow.
What is a billing backlog?
Work delivered but not yet invoiced. It is quietly expensive because every day between delivery and invoice is a day financing somebody else’s business, and it is usually invisible until somebody looks for it deliberately. Measure days between delivery and invoice, not the value outstanding.
Why is the average wait misleading?
Because it hides the stuck tail. If most items are cleared in two days and a handful have waited a year, the average looks acceptable and the experience of the people at the back of the queue does not appear anywhere. Report the longest wait, especially where waiting has a human cost.
What is ‘blocked’ and why does it matter?
An item waiting on something external — a decision, another team, a supplier, information from a customer. It matters because most backlog items spend the majority of their life blocked rather than waiting for capacity, and a team that measures only capacity will keep adding people to a problem that is not about people.
Should every backlog item have an owner?
Yes, with a decision date. Items without an owner age indefinitely because nobody is responsible for moving or removing them, and an unowned item is the most common thing found at the bottom of a hundred-item backlog.
How often should a backlog be reviewed?
Monthly at minimum for anything operational, and the review should include deletion as an explicit agenda item rather than as an exception. A backlog nobody prunes rots quietly, and the rot is invisible in the count.
What is the single biggest mistake with backlogs?
Reporting the count alone. It hides whether anything is stuck, whether the situation is improving or deteriorating, and whether effort can solve it. Seven numbers make a backlog legible; one number makes it an argument.
What does backlogging mean?
It is the verb form: to put something into the queue rather than deal with it now. That makes it a decision rather than a condition — backlogging a request is a way of declining it without a refusal. In manufacturing and inventory the same word describes accepting orders you will fulfill later, which is a deliberate policy rather than a failure. A backlog is a state; backlogging is a choice.

Sources and further reading

  1. Google Search Essentials — SEO starter guide
  2. Google: creating helpful, reliable, people-first content
  3. Google: intro to structured data
  4. Google: LocalBusiness structured data
  5. Google: FAQPage structured data
  6. Google: Article structured data
  7. Google: Product structured data
  8. Google: title links in search results
  9. Google: control your snippets
  10. Google: robots.txt introduction
  11. Google: sitemaps overview
  12. Google: consolidate duplicate URLs
  13. Google: redirects and Search
  14. Google: JavaScript SEO basics
  15. Google: multi-regional and multilingual sites
  16. Google Search Central Blog
  17. Google: get started with Search Console
  18. Google: how local search results are determined
  19. Google Business Profile: prohibited and restricted content
  20. Google Business Profile: address and service area guidelines
  21. Google Business Profile: review policy
  22. Google Business Profile: add or edit categories
  23. US Census Bureau QuickFacts: New Jersey
  24. US Census Bureau: American Community Survey
  25. US Census: Statistics of US Businesses
  26. Bureau of Labor Statistics: New Jersey data
  27. BLS: Occupational Employment and Wage Statistics
  28. NJ Department of Labor: labor market information
  29. New Jersey Business Action Center
  30. US Small Business Administration: New Jersey district
  31. USA.gov: business resources
  32. web.dev: Core Web Vitals explained
  33. web.dev: Largest Contentful Paint
  34. web.dev: Cumulative Layout Shift
  35. web.dev: Interaction to Next Paint
  36. Google PageSpeed Insights
  37. Google Rich Results Test
  38. Google Search Console
  39. W3C Markup Validation Service
  40. Schema.org: LocalBusiness type
  41. Schema.org: Service type
  42. Schema.org: FAQPage type
  43. Schema.org: HowTo type
  44. W3C: WCAG 2.2 quick reference
  45. Google Ads: location targeting settings
  46. Google Ads: about negative keywords
  47. Google Ads: about Quality Score
  48. Google Ads: importing offline conversions
  49. Google Ads: about Smart Bidding
  50. Google Ads: about Performance Max
  51. Google Local Services Ads: eligibility and screening
  52. Google Ads: keyword match types
  53. Google Analytics 4: about conversions
  54. Google Analytics 4: attribution models
  55. FTC: CAN-SPAM Act compliance guide
  56. FCC: telemarketing and robocall rules (TCPA)
  57. FTC endorsement guides — reviews and testimonials
  58. FTC: rule on consumer reviews and testimonials
  59. HHS: HIPAA guidance on online tracking technologies
  60. New Jersey Courts: attorney advertising guidelines
  61. New Jersey DCA: construction codes and permits
  62. New Jersey Home Improvement Contractor registration
  63. New Jersey Division of Consumer Affairs
  64. TikTok for Business
  65. TikTok Creative Center
  66. TikTok Ads Help Center
  67. TikTok Community Guidelines
  68. TikTok Terms of Service
  69. TikTok Privacy Policy
  70. TikTok Safety Center
  71. TikTok Transparency Center
  72. TikTok Creator Portal
  73. TikTok Newsroom
  74. TikTok for Developers
  75. TikTok advertising solutions
  76. TikTok Creator Marketplace
  77. TikTok Business Center
  78. TikTok for Business blog
  79. TikTok Creative Center: top ads
  80. TikTok Branded Content policy
  81. TikTok Shop for sellers
  82. Instagram for Business
  83. Instagram for Creators
  84. Instagram Help Center
  85. About Instagram
  86. Meta Business Suite
  87. Meta Business Help Center
  88. Meta Transparency Center
  89. About Meta
  90. Meta: Instagram platform docs
  91. YouTube Creators
  92. YouTube Official Blog
  93. YouTube Shorts help
  94. How YouTube Works
  95. YouTube Studio
  96. LinkedIn Marketing Solutions
  97. LinkedIn Help
  98. Pinterest Business
  99. Pinterest Business Help
  100. Snapchat for Business
  101. X for Business
  102. Reddit communities
  103. Reddit for Business Help
  104. ASCAP
  105. BMI
  106. SESAC
  107. Global Music Rights
  108. PRS for Music (UK)
  109. PPL (UK)
  110. SOCAN (Canada)
  111. APRA AMCOS (Australia)
  112. GEMA (Germany)
  113. SACEM (France)
  114. SIAE (Italy)
  115. JASRAC (Japan)
  116. IFPI
  117. RIAA
  118. National Music Publishers Association
  119. Harry Fox Agency
  120. SoundExchange
  121. Music Reports
  122. Epidemic Sound
  123. Artlist
  124. Soundstripe
  125. PremiumBeat
  126. AudioJungle
  127. Free Music Archive
  128. Creative Commons
  129. Incompetech
  130. FTC: advertising and marketing
  131. FTC: disclosures 101
  132. FTC: endorsement guides
  133. FTC: consumer reviews rule
  134. FTC: advertising FAQs
  135. US Copyright Office
  136. US Copyright Office: DMCA
  137. US Copyright Office: music FAQ
  138. US Copyright Office: fair use FAQ
  139. USPTO: trademarks
  140. UK Advertising Standards Authority
  141. ACCC (Australia)
  142. Competition Bureau Canada
  143. GDPR overview
  144. California Consumer Privacy Act
  145. COPPA
  146. FTC: children’s privacy
  147. W3C Web Accessibility Initiative
  148. W3C: WCAG
  149. W3C: captions
  150. W3C: making audio and video accessible
  151. ADA.gov
  152. WebAIM
  153. Epilepsy Foundation
  154. Pew Research: internet and technology
  155. DataReportal
  156. US Census Bureau
  157. US Bureau of Labor Statistics
  158. Interactive Advertising Bureau
  159. Think with Google
  160. Google Trends
  161. Nielsen insights
  162. Schema.org: VideoObject
  163. Schema.org: SocialMediaPosting
  164. Schema.org: MusicRecording
  165. Schema.org: HowTo
  166. Schema.org: FAQPage
  167. Schema.org: Organization
  168. Google: video best practices
  169. Google: video structured data
  170. CapCut
  171. Adobe Premiere Rush
  172. DaVinci Resolve
  173. Canva
  174. Descript
  175. VEED
  176. Kapwing
  177. Otter.ai
  178. Later
  179. Buffer
  180. Hootsuite
  181. Sprout Social
  182. Google Analytics
  183. Google Search Console
  184. Google Analytics developer docs
  185. GA4: events and conversions
  186. Matomo
  187. Plausible Analytics
  188. Similarweb
  189. UK Information Commissioner’s Office
  190. Office of the Privacy Commissioner of Canada
  191. Australian OAIC
  192. European Data Protection Board
  193. EU data protection
  194. EU Digital Services Act
  195. Ofcom
  196. FCC
  197. AIGA
  198. Nielsen Norman Group
  199. Smashing Magazine
  200. web.dev
  201. MDN: web media
  202. MDN: the video element
  203. ISO 21001 (reference)
  204. Buma/Stemra (Netherlands)
  205. STIM (Sweden)
  206. Teosto (Finland)
  207. Koda (Denmark)
  208. TONO (Norway)
  209. IMRO (Ireland)
  210. SGAE (Spain)
  211. ZAiKS (Poland)
  212. KOMCA (South Korea)
  213. MCSC (China)
  214. CISAC
  215. World Intellectual Property Organization
  216. TikTok: creating videos
  217. TikTok: exploring videos
  218. TikTok: privacy settings
  219. TikTok: growing your audience
  220. TikTok Creator Academy
  221. TikTok Effect House
  222. TikTok for small business
  223. Instagram: Reels help
  224. YouTube: Shorts best practice
  225. How YouTube recommends
  226. Pinterest Predicts
  227. Snapchat for Business
  228. Hootsuite blog
  229. Social Media Examiner
  230. Marketing Week
  231. Adweek
  232. US Census Bureau — Manufacturers’ Shipments, Inventories and Orders
  233. US Census Bureau — construction statistics
  234. US Bureau of Labor Statistics
  235. US Securities and Exchange Commission
  236. Financial Accounting Standards Board
  237. National Institute of Standards and Technology
  238. US Small Business Administration

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Our website uses cookies from third party services to improve your browsing experience. Read more about this and how you can control cookies by clicking "Privacy Preferences".
Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Privacy Policy
You have read and agreed to our privacy policy
Required