track-anything

name	track-anything
category	data
description	Set up a low-friction log and a weekly review that makes the data useful. Covers entry structure, capture trigger, honest gaps, summaries, and follow-up. Use when they say "I want to track X", "help me build a habit", or keep abandoning logs.

track-anything

Set up tracking with someone for a thing they actually care about: gym sessions, study hours, money from a side hustle, practice reps, sleep, applications sent. Most tracking stops because logging costs too much and the log is never read. You are building both halves: a capture flow measured in seconds, and a review loop that pays the data back. A spreadsheet is the tool; apps come and go, their sheet is theirs.

Choose what one entry is

Ask what they want to be true in three months, then work backwards to the smallest record that shows progress toward it. One row per event, three to five columns: date, the one number that matters, and at most two context fields. A notes column is allowed; required fields beyond date and the number increase the cost of keeping the log. Concrete examples: workout = date, exercise, weight×reps; sales = date, item, amount; study = date, subject, minutes. Resist the urge to track everything — they can add a column in month two if a real question demands it.

Make logging nearly free

Build the sheet together and then attack the capture cost:

• Sheet on their phone home screen, sorted newest-first so the entry row is always at the top.
• Data validation dropdowns for category fields — tapping beats typing and keeps labels consistent for later counting.
• Decide the trigger moment: log immediately after the event, tied to something that already happens (leaving the gym, closing a sale). Avoid a delayed entry plan unless the person's routine supports it.
• Missed days stay blank. Backfilling from memory manufactures data; a gap is honest information about the week. Say this now so a broken streak does not end the whole log.

Build the review loop

Tracking without review is a chore with no payoff. Add a review tab computed from the log: this week's total or count vs last week, current streak, and best-ever — the same shape as simple-dashboard, scaled down. Then set the ritual: once a week, same day, two minutes. They look at the review tab and answer two questions in a short log line: what does the data say, and what is one adjustment for next week? The adjustment is the point — a log that never changes behavior is a diary, which is fine, but not what they asked for. Averages over weeks beat any single day; teach them to shrug at outliers.

Done

• A sheet with a defined entry format and dropdowns, reachable in two taps
• Several historical or current real entries prove the capture flow and formulas
• A review tab computes the agreed measure and has a dated first-review reminder
• The person knows what to do after a missed entry: leave the gap, resume, and keep the record honest

Long-term success is assessed after the first weekly review, not claimed during setup. At that review, record what the data showed and one adjustment.

Then: chart-the-truth once a month of data exists, or simple-dashboard if the review tab deserves a URL.