Read Unfinished Work Age Without Confusing It with Completion Time

Ask how long unfinished work has been open

A queue count tells you how many items are present under a stated definition. It does not tell you whether those items started recently or have remained unfinished for a long time. Two queues can contain the same number of items and have very different age profiles. Read age alongside the count when your question concerns work that has already started and is still unfinished. Keep that question separate from how many items finished during an interval or how long completed items took.

This guide uses an original six-item fictional schedule with invented day markers. The file is not an export from a team, a model evaluation, a book excerpt or a reported client outcome. No task board was connected or changed. The examples illustrate definitions, arithmetic and summary limits. They do not recommend a staffing level, set a delivery promise, identify an actual bottleneck or establish that a particular management action will improve performance. Every interpretation should remain within the information actually supplied.

The May 2025 Kanban Guide distinguishes work-item age for unfinished work from cycle time for finished work, with start and finish boundaries defined by the workflow. That distinction is useful even when a reader is simply reviewing a report rather than implementing the entire method. This page does not claim that a fictional worksheet constitutes a Kanban system. It focuses on a narrow reading task: identifying the population, clock and boundary behind a statement about how old work is.

Choose the start boundary before calculating

The start of an item's age must correspond to the question. A request received, a task accepted and active work begun can be different events. This exercise uses a field called start_day representing an already chosen workflow start. It does not equate that field with the date someone first mentioned an idea or the instant a person began hands-on effort. If an actual report uses another start boundary, retain that boundary's name rather than replacing it with a more convenient label.

Define finished just as carefully. A draft may remain unfinished while required review is pending. An item assigned to another team can remain inside the overall workflow even though the original person's action is complete. Do not infer a finish from an assignment change or a status color without knowing the reporting rule. The downloadable example supplies explicit finish markers for two items. Its other four entries are open at the snapshot under the fictional rule, including one whose start marker is missing.

Record the snapshot cut alongside the start rule. Age is measured through a particular point, so a copied value can become ambiguous when separated from the cut. A report saying nine days old is incomplete without the time basis and observation point. If a dashboard refreshes at a different time from the underlying export, identify which cut produced the number. The goal is to reconstruct the statement another reader actually saw, not to invent a current value from stale or partial records.

Use explicit elapsed-time arithmetic

The teaching file uses abstract Day 0, Day 1 and later day markers with a snapshot at Day 10. These are ordinal markers on a fictional elapsed-day scale, not dates in a local calendar. Age equals snapshot marker minus start marker for the unfinished items with known starts. An item starting at Day 1 therefore has age nine at Day 10. We do not count both labeled endpoints as separate full days. This convention is declared so the arithmetic can be reproduced without a hidden inclusive-counting rule.

An actual reporting system may use elapsed hours, calendar days or a defined business-time calendar. Those quantities should not be mixed. If one report excludes weekends and another uses continuous elapsed time, a matching numeral is not enough to establish equivalent duration. This page supplies no business-calendar implementation, timezone conversion or rule for pauses. Preserve the actual system's definitions and identify unresolved clock questions before comparing its age values across teams, periods or tools.

Age also differs from hands-on effort. An item can accumulate elapsed age while waiting for information or review. The simple subtraction in this guide cannot determine how much effort someone spent, which stage contained the delay or who was responsible. Use appropriate records for those separate questions. Do not turn an age value into a claim that a person worked continuously for that duration, was idle for that duration or caused an avoidable delay. The number alone supports none of those conclusions.

Read the original six-item snapshot

At fictional Day 10, A is open with start Day 1, B is open with start Day 4 and C is open with start Day 9. Their known ages are nine, six and one. D started at Day 5 and finished at Day 8, so its completed duration is three. E started at Day 2 and finished at Day 9, so its completed duration is seven. F is open but has no supplied start marker. These entries are deliberately authored, not observations of operational work.

There are four open items: A, B, C and F. Three have known ages, and one has an unknown age. There are two finished items, D and E. Keep those counts separate. A report that describes the queue as three open items because only three ages can be calculated would lose F from the population. A report that supplies a fourth age of zero would invent a start condition. Count presence from the stated status and calculate age only where the required start information exists.

The known-age sum is sixteen elapsed days across three items. The arithmetic mean is sixteen divided by three, approximately 5.33 days. Sorting one, six and nine gives a median of six and a maximum of nine among those known values. Label all three summaries as covering the three open items with known starts. They are not complete summaries of all four open items because F's age remains unresolved. The unknown entry belongs beside the calculation rather than disappearing from the caption.

Do not substitute completed durations for unfinished ages

D and E have completed durations of three and seven, with a mean of five. That mean describes those two finished items. It is not the average age of the open queue, which has three known ages and one unknown. The two populations have different membership and different endpoints. A label such as average task time can conceal this difference. Ask whether the report concerns currently unfinished work, work completed in a particular interval or another explicitly defined set.

An unfinished item's current age does not supply its final duration. At Day 10, A has accumulated nine elapsed days under the fictional clock, but its finish has not been supplied. Saying that A's cycle time is nine would falsely close the measurement at the snapshot. A careful description says that it is still open with age nine. The eventual finish may produce a longer duration. This page does not estimate how much longer, assign a probability to a finish date or infer an outcome from the two completed examples.

If the slowest work remains unfinished while quicker items finish, a completed-only summary can omit the currently old work. That is a population-selection issue to inspect, not proof of misconduct or a particular mathematical distribution. Display the open-age view and completed-duration view together with their definitions. The six fictional entries demonstrate why the distinction matters, but they are too limited and deliberately invented to support a statistical conclusion about a real process, a team or future delivery behavior.

Handle the missing start without creating a false zero

F is explicitly open at the snapshot, but the start field is blank. The file does not say whether this is an export omission, an incomplete record or some other real-world event, because no real event produced it. Do not infer the cause. Report one open item with unknown start and unknown age. That gives the reader an honest boundary: the queue count is known under the supplied status, while the complete age profile cannot yet be calculated from the available fields.

If zero were inserted as F's age, the mean across four values would be sixteen divided by four, or four days. That is lower than 5.33, but it rests on an invented zero. If someone instead supplied an actual start marker later, the age could change the mean in either direction. Do not choose the replacement that makes a dashboard look healthier. Preserve the missing state and seek the authoritative record if the real operating question depends on a complete view.

A start marker after the snapshot would create a negative subtraction in this simple model. That should prompt a definition or record check rather than an interpretation that an open item has negative age. A start exactly at the snapshot has age zero under the declared elapsed-time convention and is different from a missing start. The original file contains neither a negative-age case nor a real correction. These separate arithmetic possibilities illustrate why the status of an input matters before averaging outputs.

Name the summary instead of calling everything typical

NIST's measures-of-location reference distinguishes the arithmetic mean from the median. The mean adds the values and divides by their number; the median uses their ordered position, with the stated rule for an even-sized list. For our three known ages, the mean is about 5.33 and the median is six. Neither is a universal description of every item. Show the underlying list or an appropriate distribution view so the summary does not replace the actual variation that a reader needs to understand.

The largest known age is nine, but it is not necessarily the largest age in the complete open population because F's age is unknown. Use a heading such as largest known age rather than oldest item in the whole queue. That small wording difference preserves the limitation. Likewise, a mean based on three available starts should not be labeled the full-queue mean. An apparently minor caption can determine whether a reader interprets a correct calculation as a broader unsupported claim.

Avoid treating a difference between mean and median as a diagnosis. The invented values do not establish a probability distribution, an outlier rule, a normal operating range or a threshold for intervention. A real report may benefit from other summaries, but their definitions and purpose should be stated. This guide does not choose a universal age limit or suggest that every item above a median is a problem. The right follow-up depends on the actual workflow and relevant context.

Compare two snapshots without losing membership

Consider a separate hypothetical continuation in which A, B and C remain open at Day 12 with the same starts. Their ages would be eleven, eight and three. Each rises by two, and their known-age mean becomes twenty-two divided by three, approximately 7.33. This continuation assumes no finish or start correction for those three entries. It does not predict that they will remain open. F is still unresolved, so the known-age summary still covers only three of the four open items.

Now consider an alternative continuation rather than an additional observation to pool with that one. Suppose A finishes at Day 11, while B and C remain open at Day 12. A's completed duration would be ten. B and C's current ages would be eight and three, with a mean of 5.5. The oldest known open age would fall from A's hypothetical eleven in the first continuation to B's eight in the alternative. That change reflects different membership, not a claim that the age of an unchanged item moved backward.

Keep the alternatives visibly separate. They are two authored completions of the fictional situation, not two observed days of a client engagement. A lower open-age mean after an old item leaves the queue does not establish that all remaining work became faster. A new short-age item entering can also change an aggregate without reducing any existing item's age. Reconcile which items entered, left and remained before interpreting a summary movement as evidence of a process improvement.

Preserve waiting and blocked context without rewriting the clock

An open item may have a recorded blocked or waiting status in a real workflow. Whether the age clock continues through that state depends on the metric definition. Do not silently pause the clock to make a reported age smaller if the defined quantity is elapsed time from start to the current cut. If a separate active-time measure is useful, label it separately and state how it is obtained. Our fictional file contains no stage events, pause intervals or labor records that could calculate it.

Ask what a blocked flag means and whether it is current. A flag can help identify a question for the responsible person, but it does not reveal the underlying reason without further evidence. An old item could be waiting on information, involve a different scope or contain a record problem. This article does not invent any of those explanations for A through F. Keep the age observation and the explanation separate until the actual source supports connecting them.

Avoid changing start markers solely to make an old item appear new after a handoff. If an actual process has reopening, splitting, merging or a revised work boundary, document the rule and preserve the relevant history. The simple six-row exercise does not implement those cases. A comparison across systems is only meaningful when their membership and timing rules fit the question. Do not use a neat spreadsheet total to hide a change in the way the work itself is defined.

Use the age view to ask a factual next question

A useful review might ask which currently open items have the largest known ages, which lack valid starts and what information the responsible people need next. That is different from automatically ordering work by age. Priority can involve constraints absent from the age table. This guide does not recommend bypassing approvals, interrupting a person, changing a service commitment or finishing the oldest item regardless of its actual context. The table organizes evidence for an accountable discussion rather than taking the decision itself.

Keep any action tied to an identified item and supported context. If a missing start needs correction, ask the record owner for the relevant evidence. If an item needs a decision, use the existing decision process and its authority. If a report needs clarification, state which field or boundary is ambiguous. Do not infer staffing shortages, employee performance, root causes or a financial benefit from the six invented rows. Those are separate claims requiring real information and an appropriate assessment.

The separate work-in-progress and throughput guide explains counts and event reconciliation. Use it when the question is how opening work, starts, finishes and cancellations relate. Use this page when the question is the elapsed age of unfinished work at a cut. The separate owner-and-backup guide addresses responsibility and continuity. Keeping those topics distinct prevents an age calculation from becoming a substitute for counting rules, ownership design or a forecast that it was never intended to provide.

Write a summary that keeps unknowns and limits intact

A faithful summary of the original snapshot says that four items are open, three have known ages of nine, six and one, and one has unknown age. The known-age mean is sixteen thirds, the median is six and the largest known value is nine. Two separate completed items have durations three and seven. An authored weak summary would say the team completes work in five days and has no overdue items. The file supplies no team, deadline or evidence supporting those claims.

That weak sentence is written for teaching, not observed from a model. If an assistant helps draft a real summary, provide the metric definition, cut, included population and missing-field status. Check that it has not changed a completed-only mean into a promise, converted a missing value to zero or described an available subset as the whole queue. A readable paragraph can conceal a denominator or membership error even when it repeats some individual numbers correctly.

Keep the source version and a short explanation with any shared table. The downloadable practice file contains invented identifiers and no personal or client data. It is a static teaching asset with no account access, messaging, network calls or task mutations. Replacing its inputs with sensitive records changes the working context, so use the actual appropriate environment. The arithmetic provides a reproducible description of supplied fields, not permission to publish private work details, an operational approval or a guarantee of improved outcomes.

Frequently asked questions

Is work-item age the same as completed cycle time?

No. In this guide, age concerns an unfinished item through the snapshot cut, while completed duration ends at the defined finish. A's age of nine at Day 10 does not give its eventual completion duration. D and E's finished durations describe a different population and should not be substituted for the open-age view.

How many open items are in the original file?

Four: A, B, C and F. Only three have known starts and calculable ages. Preserve F in the count while reporting its age as unknown. Omitting it because an age cannot be calculated would change the population; inserting a zero would invent information not supplied by the authored example.

Why are the known-age mean and median different?

They use different operations on the supplied list. Nine, six and one sum to sixteen, giving a mean of sixteen thirds across three items. The ordered middle value is six. Both are descriptions of the three known values only, not a distribution diagnosis, a target or a forecast for the complete queue.

Does a falling average prove that work is moving faster?

Not by itself. Items entering or leaving the open population can change the mean without reducing any unchanged item's age. Reconcile membership and definitions before interpreting the movement. The hypothetical continuations demonstrate arithmetic alternatives, not actual process improvements, employee outcomes or evidence that a management change caused a result.

Can I pause age while an item is waiting?

Use the actual metric definition and retain its label. Continuous elapsed age and a separately defined active-time measure are different quantities. Do not silently remove waiting intervals from a report that claims elapsed time from start. The practice file supplies no pause events or effort records and cannot calculate active work time.

Does this worksheet update a task board or predict delivery?

No. It is an original static CSV and visible teaching table. It makes no network or model calls, writes no task records and provides no completion-date forecast or operational approval. All items and day markers are deliberately invented; no client results, book quotations, named professional review or endorsements are asserted.