Tasks: The Execution Surface That Questions What You Do

Three Dimensions, One Surface

A Task in Fathom is not just an item on a list. Every Task exists in three dimensions simultaneously — and each dimension answers a different question about the work.

To Dos: What Needs Doing

The first dimension is the familiar one: the item itself. A To Do is concrete, completable, and optionally deadline-bound. Fathom groups To Dos by urgency — Overdue, Today, This Week — so the surface you see each morning is already sorted by when things are due rather than when they happened to be captured.

The difference from a conventional list is provenance. To Dos in Fathom can be derived from your Goals — created as the concrete next steps a Goal requires and linked to it, so the justification travels with the task rather than accumulating from inbox pressure. A derived To Do carries its reason with it: you know why it exists, because you can see the Goal it serves. An item you cannot connect to anything is still allowed — life contains dentist appointments — but the system makes the distinction visible instead of letting reactive work masquerade as progress.

Projects: What It Belongs To

The second dimension is context. Related work can be grouped into a Project — an optional container that sits under one of the six life Pillars: Work, Wealth, Wellbeing, Recreation, Connection, and Environment. A Project might be "Fathom launch," "House renovation," or "Board readiness" — a named arena of related effort with its own tasks and its own share of your week.

Projects serve two purposes. The first is organisational: they keep related tasks together so a body of work can be seen and managed as a whole. The second is diagnostic: because every Project is anchored to a Pillar, the shape of your commitments becomes visible at the domain level. If every active Project sits under Work, that is not a scheduling detail — it is a finding. The imbalance that Pillars diagnoses in the Evaluate stage shows up here as its concrete cause: this is where the imbalance is being produced, task by task, week by week.

Projects are deliberately optional. Not every task needs a container, and forcing one produces filing theatre rather than clarity. The rule is simple: if work is related and ongoing, group it; if it is a one-off, let it stand alone.

Time: What It Costs

The third dimension is the one no to-do list has, and the one that changes everything: cost.

Every week contains exactly 168 hours. No exceptions, no rollovers, no top-ups. Fathom starts from that number and subtracts your baseline — sleep, meals, care, the non-negotiable maintenance of being a person. What remains is the discretionary balance, and Fathom puts it in front of you plainly: You have 91 hours unspoken for. Intentionality starts here.

Those remaining hours are then allocated deliberately — across Projects and Pillars, in advance, as a budget rather than a post-mortem. The mechanism matters: allocation happens before the week, so the question you face is "What do I want these hours to buy?" rather than the retrospective and unanswerable "Where did the week go?" A Project with no hours assigned is not a project; it is a hope. A Pillar receiving two of your ninety-one discretionary hours is not being balanced against the others; it is being abandoned, quietly, with plausible deniability.

This is the honest dimension. Most people manage money with more rigour than time, despite time being the only one of the two that cannot be earned back. Time-use research consistently finds a wide gap between how people believe their hours are distributed and how they actually are — and the direction of the error is predictable: meaningful activity is overestimated, reactive and passive time underestimated. The Time dimension exists to close that gap with arithmetic instead of impressions.

---

Tasks vs Goals and Habits: A Critical Distinction

The three Execute components are easily conflated and serve different functions.

Goals describe outcomes — where you are heading. They are time-bound, reviewed periodically, and optional: direction, not identity. Habits describe rhythm — what you do repeatedly, on purpose. They are ongoing, tracked daily, and compound whether or not any particular Goal justifies them. Tasks describe the day-to-day — the specific, completable work that needs doing now, this week, by Friday.

The operational difference is completion. A Habit is never finished; its value is in repetition. A Goal is reached or revised; its value is in direction. A Task is done and gone; its value is in the specific thing it moved. A Goal without Tasks is a wish with a deadline — direction with no mechanism. Tasks without Goals are motion without direction — a busy week that adds up to nothing in particular. Habits hold the ground between them: the repeated behaviours that keep the system running whether or not a given task is due today.

Run together, the three answer Execute's question in full. Goals say where. Habits say how, repeatedly. Tasks say what, today — and the Time dimension says what it all costs.

---

Common Task Failure Patterns

The reactive week. Every task arrived from outside — email, requests, other people's urgency — and none derived from your Goals. The week was full and produced nothing you chose. The tell: pull the thread on any task and it leads to an inbox, not a Value.

Unallocated hours. Tasks exist, Projects exist, but no hours were assigned in advance. Time gets claimed by default — by the loudest demand, the nearest screen — and the week's shape is discovered afterwards rather than decided beforehand.

The single-Pillar portfolio. Every task and every allocated hour sits under Work. The other five Pillars are not failing; they are simply absent from the ledger. This pattern is invisible on a flat to-do list and unmissable on a Pillar-anchored one.

Capture without completion. The list grows faster than it shrinks, becoming an archive of guilt rather than an execution surface. The fix is rarely more discipline; it is honest deletion. A task you have carried for six weeks without touching is not pending — it is undecided, and pretending otherwise costs attention every time you scroll past it.

Fictional budgeting. Allocating 60 productive hours to a week that contains a baseline, a family, and a human body. Over-allocation is not ambition; it is a plan to fail and then misattribute the failure to willpower. The 168-hour arithmetic is unforgiving precisely so that the plan cannot lie.

Task-sized goals, goal-sized tasks. "Rebuild professional network" is not a task — it is a Goal wearing the wrong clothes, and it will sit uncompleted forever because it cannot be completed in a sitting. "Email David about the Manchester intro" is a task. If an item survives three weeks untouched, the most common reason is that it is not actually actionable at its current size.

---

Start Running Your Days Deliberately

The Tasks framework is one component of Fathom's integrated personal development system — a structured approach to self-understanding, intentional living, and behavioural evidence for executives and professionals navigating complexity. Your 168 hours will be allocated to something this week. The only question is whether that allocation reflects what you decided matters — or simply what happened. Explore how Fathom works or get started today.