The problem is the data model, not discipline. While time is a field on a card, duration, simultaneity and history are inexpressible; no amount of careful upkeep compensates for that.
Duration, simultaneity, horizon and your own history go missing when time is a field on a record rather than the surface everything sits on. This document states the problem, defines the model that treats time as the carrier, and describes the mechanisms, the cost, the risks and the way to check whether any of it worked.
About this document
| Genre | An analytical document — a whitepaper. |
| Audience | Team and department leads, process owners, and independent practitioners evaluating the approach before applying it. |
| What it provides | A statement of the problem, a description of the model, the mechanisms behind the effect, a pilot programme, metrics, risks, and requirements for a tool. |
| What it does not contain | A product specification, a commercial offer, or promises of productivity. |
| Companion document | The Timeline Thinking manifesto — the declarative version of the same ideas. |
| Last updated |
How to read this. The document stands alone: it requires no acquaintance with the manifesto and does not restate it. The manifesto answers the question “what do we believe”. The long-form account of the approach answers “how is it built and what do I do”. This document answers “what problem does it solve, by what mechanism, what does it cost, and how do I check that it worked”.
Contents
Abstract
Tools for organising work — task lists, calendars, kanban boards, trackers — inherited a common data model in which time is an attribute of a record: a task has a due date, an event has a date. That model answers the question “what do I do next” and is structurally incapable of answering “how long will this take”, “what will it collide with” and “how long did work like this actually take before”. We call the resulting deficit temporal blindness: the systematic invisibility of duration, simultaneity, horizon, and one’s own history.
Temporal blindness does not feel like missing information. It feels like a run of surprises: “everything landed in the same month”, “we estimated three times more optimistically than it turned out”, “I came back to something I had parked and lost the context”. Each surprise gets a local explanation, so the systemic source goes unnoticed for years.
Timeline Thinking is an approach in which time is taken as the carrier rather than an attribute: activity is laid out on a shared timeline — one axis of time crossed by parallel lanes; work is represented as durations with internal phases and markers; the past stays on the same timeline as the future; and the viewing scale moves freely, from a week to a decade.
The document describes the problem (§1), states the thesis and its boundaries (§2), defines the model and the operations on it (§3), works through the causal mechanisms by which the approach has an effect (§4), gives scenarios (§5), a 90-day pilot programme (§6), metrics (§7), risks (§8) and economics (§9). Requirements for a tool are given separately and are vendor-neutral (§11), along with a list of what remains unverified (§12).
Key claims
The problem is the data model, not discipline. While time is a field on a card, duration, simultaneity and history are inexpressible; no amount of careful upkeep compensates for that.
Four blind spots make up one problem: invisible duration, invisible parallelism, a short horizon, and a lost trace. They reinforce one another.
The first shift is duration instead of a due date. A deadline is the end of a span; managing deadlines alone is managing the moment of failure.
The second shift is parallel lines instead of a queue. Most failures are born where lines cross, not inside any one of them.
The third shift is keeping the past in the system. A retained trace turns estimation from an act of intuition into a statistical procedure on your own data.
The approach gives visibility, not speed. It does not promise more work in the same time; it promises that you see overload, collisions and the drift between plan and fact earlier.
Upkeep costs on the order of 15–30 minutes per person per week, plus a one-off layout when a large piece of work starts. More than that means an antipattern has kicked in.
The main adoption risk is the timeline turning into an instrument of supervision. When that happens the data becomes defensive, and the approach loses its point entirely.
Section 1
Temporal blindness is a state in which someone taking part in an activity cannot get an answer to questions about time without reconstructing it by hand:
The key word is reconstructing. The information formally exists: the dates are in the tracker, the meetings in the calendar, the correspondence in the mail. But to get an answer out of it, a person has to assemble the picture in their head, and working memory is not built for that. In practice this means the answer is either never obtained at all, or obtained as an impression.
Form 1. Invisible duration. Work is represented as a point (a due date) or as a state (“in progress”). A two-hour item and a two-month item take up the same line in a list. Consequence: planning becomes an enumeration of intentions rather than the placement of volumes into finite space.
Form 2. Invisible simultaneity. Tools show one line: a project, a board, a sprint. A person, however, takes part in several lines at once, and their capacity is shared across all of them. Consequence: commitments are taken independently of one another and executed out of a single resource.
Form 3. A short horizon. A calendar is readable at the week, a board at “today”, a sprint at two weeks. No mainstream tool gives a readable quarter or year. Consequence: seasonality, cycles and the accumulation of commitments stay invisible until they arrive.
Form 4. A lost trace. Finished work is archived, hidden, moved to “Done”. Consequence: the only available source of estimates is memory — and memory of duration is systematically biased toward optimism.
Below are the typical observable symptoms and their actual source. It is precisely the mismatch between symptom and source that makes the problem durable: every individual case gets its own particular explanation.
| Symptom | Usual explanation | Actual source |
|---|---|---|
| “Everything landed in November” | an unlucky coincidence | form 2: commitments were taken one line at a time |
| “We estimated three times too optimistically” | hard piece of work, bad luck | form 4: no access to the durations of past work |
| “The deadline arrived out of nowhere” | we lost track of it | form 1: the end was being managed, not the span |
| “Half the quarter went on waiting” | the people upstream let us down | form 1: the waiting was never drawn as a duration |
| “I came back to the project and lost a day” | context switching | form 4: there is no trace, so there is nothing to restore from |
| “Status meetings take a day a week” | too much communication | forms 2 and 3: the state is visible nowhere, so it has to be said out loud |
| “Plans are useless, everything changes” | the environment is uncertain | form 1: dates were planned, not volumes and reserves |
Each class of tools is optimal for its own question and stays silent about time in its own way: a list answers “what is next”, a calendar “where am I busy”, a board “what is happening now”, a tracker “what state is this unit of work in”, notes “what do I know”. None of them answers “how does this unfold, and what does it land on top of”.
The project Gantt chart — the one mainstream tool in which time really is the carrier — has degenerated inside organisations into a reporting artefact: excessive detail, a rigid network of dependencies, upkeep by an administrator, and a plan treated as a promise. What is left is Gantt theatre: the chart is stale by its second week and lives separately from the work.
Section 2
Activity becomes manageable when it is represented not as a set of records with dates, but as the arrangement of durations on a shared axis of time across several parallel lines, with the past retained and the scale freely changeable.
Everything that follows is derived from that sentence. It contains exactly four requirements: durations (not points), a shared axis (not separate projects), parallelism (not a queue), and a retained past (not an archive). The fifth — free scale — is a technical condition of readability.
Timeline Thinking is a practice of organising understanding and control in which:
This section exists to cut off inflated expectations in advance: they are the main reason approaches like this get rejected after the first month.
Section 3
| Primitive | The question it answers | Notes |
|---|---|---|
| Timeline | “which area of activity is this” | the whole plane: the axis of time with every lane on it. You start a separate one when its contents need no comparison with the neighbouring one |
| Lane | “whose rhythm is this” | a person, a team, a department, an area of life, a storyline |
| Span | “what lasts” | a project, a phase, a state, a period; open ends are allowed |
| Phase | “what kinds of part is it made of” | internal structure of a span, without spawning new entities |
| Marker | “how will we know this work is going as intended” | a significant point inside a span or a phase; may carry task state |
| Milestone | “what is this line’s significant stage or goal” | a significant point on the lane as a whole, belonging to no individual span |
| Point (event) | “what happened at a moment” | a meeting, a publication, a payment, an incident; may carry task state |
| Buffer | “where do I put this until I know” | an unstructured inbox |
A marker, a milestone and a point are three different things, and it is worth telling them apart from the very beginning. A marker lives inside a piece of work and speaks about how that work is going: did we get to where we meant to get. A point is simply something that happened at a moment. A milestone sits on the lane and marks a stage or a goal of the line itself — it belongs to no span, and it stays meaningful even when the work underneath it changes.
The set is deliberately small. Expanding the ontology is the classic way to kill models like this: every new entity demands a decision at the point of entry, and decisions at the entrance kill entry.
A model is defined not only by what it contains but by what you do with it. There are five operations, and each is tied to a rhythm.
| Operation | When | Result |
|---|---|---|
| Capture | the moment the thought appears — seconds | an entry in the buffer, or a place on the timeline straight away if there is enough to go on |
| Layout | when a large piece of work starts, 20–40 minutes | a span with phases, markers, and the “worst week” located |
| The weekly review | weekly, 15 minutes | an emptied buffer, boundaries moved to match fact, one decision |
| The zoom cycle | monthly and quarterly | answers to the questions of scale: direction, collisions, capacity |
| The trace review | quarterly, and when a large piece of work finishes | the plan-versus-fact coefficient, applied to the next estimate |
The buffer is insurance, not a mandatory stop. If at the moment a thought appears you already have enough to go on — you know what it is, how long it lasts and which lane it belongs to — placing it straight away is better than routing it through the buffer. The buffer exists for the other case: when there is no time or no material to decide with, and the only alternative is losing the thought.
The operations matter more than the composition of the model. A timeline that never gets reviewed degrades faster than a list, and does more harm than one, because it goes on looking trustworthy.
Testable statements; a violation means the model has drifted.
Section 4
This section answers “by what mechanism, exactly”, without appeals to belief. Each entry is a causal chain plus a way of testing it on your own data.
| Mechanism | What it makes visible | Metric to check it |
|---|---|---|
| Volume instead of intention | capacity | refusals taken before the start |
| Early detection | crossings between lines | the discovery distance |
| Reference class | real duration | the fact-over-plan coefficient and its spread |
| External memory | current state | time to get back into context |
| Emptiness as reserve | missing buffers | share of milestones with a buffer |
| Drift as data | systematic error | share of work with the plan retained |
Section 5
Important. The scenarios below are synthetic illustrations built out of typical situations, not reports from adoptions. The numbers in them convey scale; they are not measurements.
Situation. Three areas of work, fifteen people, quarterly planning in a tracker, a status meeting once a week. The recurring complaint: “everything converges at the end of the quarter”.
What they do. One lane per area, plus a lane for external dependencies. Initiatives become spans with phases — “work it out → build → ship → observe”. Markers inside the phases are the dates by which something has to be true; the lane’s milestones are the major goals of the area that this work leads to. Everything that depends on other parties — legal approvals, deliveries, partner replies — becomes separate points.
What becomes visible on the very first layout. Three initiatives from different areas all lay claim to the same month of the same person. The “observe” phase after shipping was never planned, yet always took two weeks. Half the dependencies on other parties fall inside the holiday period.
The decision that gets taken. One initiative moves out by a month — not because it matters less, but because it is now visible that three do not fit in parallel.
Situation. Several channels, a publication plan in a spreadsheet, and a chronic sense of scramble before each piece goes out.
What they do. One lane per channel, one span per production cycle of a piece (“research → draft → edits → production”), with publication dates as points.
What becomes visible. The publications are evenly spread; the production cycles are not — they overlap at the tails. The real load falls not on publication days but on the intervals between them, and those intervals do not exist in the publication calendar at all.
The decision. What moves is not the release schedule but the starts of the cycles.
Situation. A course of several modules, several cohorts, teachers who overlap.
What they do. One lane per cohort and one lane per teacher. Modules become spans; checkpoints become markers inside them.
What becomes visible. For students, the third week of every module is the point where assignments from three courses converge. For a teacher, the peak of marking coincides with the start of the next cohort.
The decision. Checkpoints move by a week — a change that is impossible without looking at all cohorts at once.
Situation. Freelance or research work: several clients or topics, no external structure, the horizon held in the head.
What they do. One lane per client or topic, plus lanes for personal areas — health, study, family. Commitments become spans.
What becomes visible. The total load taken on exceeds the available time by 30–40% — systematically, not in the odd month. The personal lanes are empty for half a year at a stretch.
The decision. Declining one commitment during negotiation — the cheapest refusal available.
Situation. You need to understand what happened: an outage, a conflict, a long story with several parties.
What they do. Chronology mode — there is no future. Every dated fact goes into the buffer without judgement, then gets laid out on lanes by source: the system, the team, the external party.
What becomes visible. The gaps — intervals where nothing was recorded; the substantial thing is usually in there. And coincidences in time between lanes, which get lost in a textual account.
The decision. The chronology becomes the primary artefact of the review: a sequence shown answers more questions than a sequence narrated.
Section 6
Designed for a team of up to fifteen people, or for a single practitioner. It is built deliberately so that each phase is useful on its own and could be the last: an approach that requires full adoption before the first benefit does not survive its third week.
Before the start · 1–2 hours
Weeks 1–2 · Goal: stop losing incoming things and learn to see volume
Passing criterion: nothing on the timeline that lasts longer than a day is represented as a point.
What already pays off: the visible volume of commitments taken. As a rule, this step reveals 1.5–2 times more work than anyone assumed.
Weeks 3–6 · Goal: see the crossings and establish a rhythm
Passing criterion: three reviews happened in a row, and each one ended in a decision.
What already pays off: the first collisions found in advance.
Weeks 7–12 · Goal: turn the past into an instrument of estimation
Passing criterion: the next estimate is made with an explicit correction for your own coefficient, rather than by eye.
| Moment | Sign of success | Sign that it is time to stop |
|---|---|---|
| End of week 2 | volume has become visible, the buffer is in use | nobody opened the timeline once after setting it up |
| End of week 6 | the review has become a habit, 1+ collision found | the review has turned into a report for a manager |
| End of week 12 | there is a coefficient, and estimates have changed | upkeep takes more than an hour a week |
Stopping is a legitimate outcome. The approach delivers value in layers, and the second one — durations instead of items, with no lanes and no trace yet — is already self-sufficient.
Section 7
Metrics exist to test the hypothesis that this is useful, not to appraise people. The moment measurement starts to affect pay or reputation, the data becomes defensive — and with it the only source of feedback disappears. This is not an ethical footnote but an engineering constraint: a measurement system that influences what it measures stops measuring.
The regularity of the review is not an indicator but a precondition: until the ritual is a habit, every number below is unreliable, because the model lags reality. Computing “reviews held ÷ reviews planned” is meaningless — a continuous flow of work has no finite number of planned reviews. A qualitative sign is enough: skips happen less often than once a month.
| Indicator | How to compute it | Expected direction |
|---|---|---|
| Estimation coefficient | median of fact ÷ plan across work of the same kind | stabilises; the spread narrows |
| Discovery distance | days between finding a conflict and the conflict landing | grows |
| Share of work with a duration | spans ÷ (spans + points that last more than a day) | tends toward 1 |
| Refusals before the start | number of commitments declined during discussion | grows (and that is a positive result) |
| Time spent on status discussion | hours per week spent retelling state | falls |
| Share of milestones with a buffer | milestones with an unoccupied interval in front of them | grows |
| Overdue items | number of overdue commitments in the period | falls slowly, with a quarter’s lag |
For the first 4–6 weeks the indicators typically get worse: overdue work that nobody used to track becomes visible, and volume that nobody used to measure becomes measurable. That is the effect of visibility appearing, not of anything degrading. A meaningful comparison is not possible any earlier than a quarter in.
Section 8
| Risk | Early sign | Counter-measure |
|---|---|---|
| The timeline as supervision | a manager demands detail about someone else’s time | write down the Phase 0 rule; an aggregated overview instead of a personal one; the timeline is owned by whoever does the work |
| A reporting artefact | the timeline is updated before a meeting rather than during the review | it is kept by whoever does the work; the review must end in a decision |
| Over-modeling | weeks go into structure rather than content | the invariant “detail never exceeds the horizon”; a cap on the number of lanes |
| Duplicating systems | calendar meetings get copied over by hand | draw the line: the calendar holds other people’s claims on your time, the timeline holds your own work |
| Fading after the start | reviews get skipped from the second week | a fixed time for the review; the rule “15 minutes, no more”; durations alone as an acceptable stopping point |
| Punishing divergence | the boundaries of past spans get adjusted to fit the plan | keep the planned and the actual line separate; discuss divergence as data |
| Total rollout | the approach is introduced organisation-wide by decree | a pilot on one unit; spread by example, not by regulation |
| False precision | every date is known and every span is closed | make open intervals legitimate, along with the phrasing “not before” |
The first two risks stand apart: they do not reduce the effect, they zero it. Both turn the timeline from an instrument of understanding into a subject of reporting, after which what gets written into it is the safe version rather than the real one.
Section 9
| Item | One-off | Recurring |
|---|---|---|
| Initial layout of current work | 1–2 hours per person | — |
| Layout of a new large piece of work | — | 20–40 minutes at the start |
| The weekly review | — | 15 minutes per person |
| Quarterly zoom cycle and trace review | — | 1–2 hours per quarter |
| Learning it | an hour of reading plus one review done together | — |
The recurring load comes to roughly 15–30 minutes per person per week. That is the upper bound of normal: exceeding it almost always means an antipattern has fired, not that the work is objectively complex.
The cost is compared not with “productivity” but with the price of the specific events the approach prevents:
The break-even point is reached on the first collision prevented. That is exactly why the pilot is built around the layout and the review rather than around completeness of data.
For single-threaded work with a horizon of a few days the recurring cost is not recovered: there is nothing to prevent, no reference class accumulates, and the horizon is empty. In that case the correct conclusion is not to adopt it (§12).
Section 10
The approach adds a dimension; it does not replace systems. Each of the practices below covers one of its weaknesses.
| Practice | What we take from it | What we add |
|---|---|---|
| GTD | capture into a single entrance, a regular review | durations, parallel lines, a horizon |
| Kanban | limiting work in progress, flow | an axis of time, memory, a horizon |
| The calendar | commitments and reminders | your own work and its volume |
| OKRs and goals | direction and priorities | capacity: how much room there actually is |
| Gantt / PERT | the form: spans and lanes on a shared axis, milestones | survivability: minimal detail, the plan as a hypothesis, upkeep by whoever does the work |
| Note-taking systems | context and knowledge | the processual dimension: how it unfolded |
The combining formula: capture from GTD, flow from kanban, commitments from the calendar, direction from goals, and the shape of time from Gantt.
Section 11
This section is vendor-neutral: it is a checklist for evaluating any solution, including a spreadsheet and a sheet of paper.
The Timelines product was designed as a direct embodiment of the model described here: a timeline is a Timeline (a board), a lane is a swimlane, a span is a bar (including an open one), a phase is a segment, a marker inside work is a marker, a lane milestone is a milestone, a point or a task is a point, and the buffer is the inbox. This does not mean the approach requires the product: the mapping is given as an example of full coverage of the checklist, not as a condition of practising the approach.
Section 12
An honest list of what we do not know and what would be worth checking before asserting anything stronger:
These questions are a programme for later work, not caveats. A document claiming more than this without data would be advertising.
Section 13
The problem described in §1 is not solved by effort, and it is not a consequence of poor discipline. It follows from a data model in which time is an attribute of a record. In that model duration, simultaneity, horizon and history are inexpressible, and no amount of careful upkeep will change that.
Timeline Thinking proposes one change, carried through consistently: treat time as the carrier. From it follow the primitives (§3), the operations (§3.2), the mechanisms behind the effect (§4) and the practices of adoption (§6). The approach does not promise speed — it gives visibility: overload, collisions and the drift between plan and fact become observable before they turn into events.
Testing this is cheaper than debating it. The minimal experiment takes two hours: lay your current work out as spans on a shared axis, and find the week where everything converges.
The result is usually unpleasant exactly once — and useful every time after that.
Appendix A
Answer yes or no. The questions are about the last three months.
Interpretation. “Yes” to 1, 6 and 7, and “no” to 2, 3, 4, 5, 8, 9 and 10 are signs of temporal blindness. Five signs or more mean the deficit is structural rather than situational: it will not be removed by effort and calls for a change of model. One or two signs are situational — targeted measures are enough. Zero signs mean the approach is probably not for you, and that is a perfectly normal result.
Appendix B
| Temporal blindness | the inability to get an answer about duration, simultaneity, horizon and history without reconstructing it by hand |
| Timeline | the whole plane of “axis of time × lanes” on which activity is laid out; not one line and not one lane |
| Lane | a parallel line; it answers the question “whose rhythm is this” |
| Span | something that lasts; open ends are allowed |
| Open-ended span | a span with an unknown start or end; the form honest uncertainty takes |
| Phase | a part of a span that differs in the character of the work |
| Marker | a significant point inside a span or a phase: it shows whether the work is going as intended |
| Milestone | a significant point on the lane as a whole: a stage or goal of the line, belonging to no individual span |
| Point (event) | something that happens at a moment and has no duration |
| Buffer | the unstructured inbox for thoughts that have not been placed yet |
| Layout | placing a piece of work in time at the moment it starts |
| The weekly review | a weekly ritual, 15 minutes: the buffer, boundaries moved to match fact, a look ahead, one decision |
| The zoom cycle | reading the same material at several scales, top down |
| The trace | the retained past, used as a source of estimates |
| Gap | significant emptiness; reserve |
| Collision | several lines crossing over the same stretch of time |
| Estimation coefficient | the ratio of actual to planned duration across work of the same kind |
Boards, lanes, spans with phases, markers and milestones, an inbox and a past that stays put — the primitives of this document, as an app. It’s completely free.