What Your Task Velocity Is Really Telling You
A Task Velocity score is easy to read on the surface — above 1.0x is good, below 1.0x is bad. But that framing misses most of what the number is actually telling you. This article is for people who already understand what Task Velocity is and want to use it as a diagnostic tool, not just a scorecard.
The Three Reasons Velocity Drops
When Task Velocity falls below 1.0x or trends downward over several weeks, it's almost always one of three things.
Inbox inflation. You're capturing more than you're processing. This is common when a new project starts, when you're in a busy period, or when you've been using Principal Task as a capture-only tool without doing regular reviews. The signal here is a large number of open tasks with no due dates, no folders, and no statuses. If you filter the velocity chart by folder and find one folder with dramatically lower velocity than the others, that folder is likely the culprit. The fix is a deliberate audit: assign, break down, or delete the tasks that are inflating the list.
Genuine workload increase. Sometimes you're just being asked to do more than can be done. This shows up as a consistent downward trend even when your tasks are well-organized and your completion rate on individual items is healthy. If this is what's happening, the score is telling you something real about capacity, not about your system. The useful question isn't "how do I fix my score" — it's "what do I stop doing, defer, or delegate?"
Stale tasks from past projects. Tasks that were relevant three months ago but will never be completed are still counted. They appear as persistent open items and drag the denominator of your score upward without any corresponding completions. If your oldest open tasks are months or years old, a cleanup pass — completing, canceling, or deleting them — will give you a more accurate picture and likely raise your score.
When a Score Below 1.0x Is Fine
A score below 1.0x during certain periods is not a warning sign — it's a natural reflection of how work happens. When you kick off a major project, you'll create a lot of tasks at once and completion will lag behind creation for a few weeks. When you're in a research or planning mode, you're building inventory before you start executing. When life gets unusually busy, completions slow down even if you're working just as hard.
The pattern that warrants attention isn't a single low reading — it's a sustained downward trend over several consecutive 30-day windows, or a score that has been below 1.0x for long enough that you've lost confidence in your task list as a reliable view of your actual work. A brief dip followed by recovery is normal variation. A floor that keeps dropping is a signal.
Using Filters to Diagnose Your Score
Premium feature. Filter controls on the Task Velocity chart are available on paid plans. Free users see their overall score only.
The most powerful use of Task Velocity isn't the overall number — it's the filtered number. Premium users can filter the velocity chart by Folder, Context, Priority, and Status using the gear icon on the velocity card in the Dashboard. Each filter changes the score to reflect only the tasks that match.
The diagnostic value is in the comparison. If your overall velocity is 1.1x but filtered to your largest project folder it drops to 0.5x, you've found where the backlog is accumulating. If filtering by a specific context produces a dramatically different score than filtering by another, you're seeing an imbalance in how different types of work are moving. The overall score smooths over these differences; the filtered score surfaces them.
On mobile: Click the Settings icon to set the filter options for the velocity chart.
The Weekly Velocity Review
The most useful habit around Task Velocity isn't watching the number daily — it's checking it as part of a weekly review. Once a week, look at the score and the trend. Ask two questions: is it moving in the direction you'd expect given how the week went, and is anything unusual worth investigating?
The goal isn't to maximize the number. A sustained 1.5x might mean you're completing trivial tasks while deferring important ones. A 0.9x during a hard week might be exactly right. What you're looking for is a pattern you understand, not a number you're optimizing. When the score surprises you — higher or lower than expected — that's the useful signal. Something in your work changed, and the velocity score is the instrument that caught it.
For the broader weekly review practice that makes this habit effective, see Building a System That Actually Works.
What to Do When Velocity Stalls
A score that has been flat or declining for several weeks calls for deliberate action. Here are five moves that tend to break the stall.
Audit tasks open longer than 30 days. Open the task list and sort or filter for old items. For each one: decide whether to complete it now, break it into a concrete next action, or delete it. Tasks that survive a review but never get done are false positives — they inflate the denominator without ever contributing a completion.
Break large tasks down. A single task called "Update the proposal" sitting open for two weeks contributes nothing to velocity until it's complete. Break it into the actual steps — "Pull last year's version," "Update section 2," "Send to client for review" — and completions start registering. See Break Any Project Down with Subtasks for how to structure this.
Use due dates to surface work. Tasks without due dates don't appear in Today's Focus or This Week. If large blocks of your list are undated, they're invisible until you go looking. Assigning dates makes work visible, which makes it more likely to get done.
Clear completions the same day. The velocity calculation depends on completion timestamps. Tasks finished but not marked complete don't register. The habit of marking tasks done as you finish them — not at the end of the week — keeps the score accurate and responsive.
Use the velocity filters to find the stall point. If you have access to the premium chart filters, narrow by folder and context to find where completions are lagging. A stall is rarely distributed evenly — it usually has a source.