3
3 Comments

Your mental model of how you spend your time is almost certainly wrong.

A while back I shared why I started building Focuser (https://lifefocuser.com/). This post is about Focus Metrics; the layer that closes the loop between the life you intend to live and the one you're actually living.

The gap nobody measures -

Ask someone how they're doing across the areas of life they care about and they'll give you a confident answer. Pretty consistent about my health. Staying on top of finances. Making time for family.

That answer is almost always wrong.

Not because people are dishonest with themselves; because without something to measure it, the mental model gets built from highlights, not averages. You remember the week you trained hard, the weekend you spent entirely with family, the month you made real progress on a personal project. Those moments feel representative because they stand out.

What doesn't register is the long median. The ordinary weeks where health got almost no real attention. Where the personal finance stuff hasn't actually been touched in three months. Where the personal project sat untouched for longer than you'd care to admit.

There are only so many hours in a day; that's just true. But the insight here isn't "rebalance the pie." It's that the gap between what you think you're doing and what you're actually doing can be enormous, and nothing in your current system is telling you. You think you're working out five days a week. It's been two days at most, and it's been that way for five months.

Highlights are not your life. Averages are.

Why task completion doesn't solve this -

Most productivity tracking looks great on paper and feels hollow in practice. You checked things off. The tool says you were productive. But if you look back on the week, were you intentional? Did any of it actually move you toward something that matters to you?

Task completion measures throughput, not alignment. It tells you how much you did; not whether what you did served the life you're trying to build.
Urgency makes this worse. Obligations and urgent things crowd out intentional ones; not because you're undisciplined, but because there's no signal telling you when a life area is being neglected. Urgency is loud. Intention is quiet. Without something that makes intention visible, urgency wins by default; not through any conscious choice, just through the path of least resistance.

By the time you notice, weeks or months may have passed. You've been productive by every conventional measure. You just haven't been building the life you said you wanted.

The measurement problem is harder than it looks -

Focus Metrics is the analytics layer in Focuser. The concept: take the attribution data the app accumulates over time and surface whether your effort distribution actually reflects your stated priorities.

The obvious implementation is to count finished items per Focus, divide, and show percentages. The problem is that produces a number that looks like insight but isn't. If your Career Focus has fifty items and your Family Focus has five, a raw completion count will always skew toward Career regardless of how intentionally you're living. You end up measuring the size of your checklists more than the quality of your attention.

So the model has to be opportunity-based. The question isn't how many items you finished for a given Focus; it's how many you finished relative to how many you had a real chance to finish. That means looking across every place a Focus shows up in the system: items completed directly on secondary checklists, effort items that were due and either got done or didn't, primary checklist items that came up and were either handled or left. And it has to be fair about timing; assigning something to this month shouldn't count against you until the month is actually over. Getting all of that to produce a balance score that reflects how you actually spent your time, rather than just how ambitious your checklists are, is the core challenge. The math runs and the number displays; whether that number is actually right is what real-world testing will tell me.

There's also the question of unassigned items. Not everything belongs to a Focus. Obligations exist. Administrative tasks exist. Things that genuinely don't fit anywhere. Ignoring them in the measurement would misrepresent how your time was actually spent; they compete for the same hours as everything else. A system that only accounts for the intentional parts of your life isn't measuring your life; it's measuring the parts you'd prefer to see.

What I learned from my own data -

I thought I was an active guy. At one point I was; making it a point to walk five miles a day. Then life shifted and that routine fell off. I assumed I'd just scaled back a bit.

The data said otherwise. I scaled back alright; way back, and for much longer than I thought. I hadn't noticed because my mental model was still running on the highlight reel.

That's not a resource allocation problem. I didn't need to take time from somewhere else to fix it. I just needed to see it clearly. Once it was visible, the path forward was obvious. Without visibility, nothing prompts you to change.
You can rationalize a feeling. You can't rationalize a number.

Where it stands -

If you've been following the build of Focuser (https://lifefocuser.com/), you'll remember that Focus Metrics is a working prototype. The math runs, the visualizations exist, the number displays. What I don't know yet is whether the number is right; and getting that right requires time living inside it, watching where the output diverges from reality, adjusting, repeating. That's not something you can shortcut.

The Kickstarter campaign launches March 17th, but the pre-launch page is live right now at https://www.kickstarter.com/projects/188713251/focuser?ref=3v5ytl. The campaign funds the Focus Metrics fine-tuning and real-world data qualification time, alongside native iOS and Android development and third-party integrations. If you've been following the build, this is the campaign I've been working toward.

If you've wrestled with how to measure something as subjective as effort alignment, or if you've run into the opportunity-weighting problem in a different context, I'd genuinely like to hear how you approached it.

Full post on the philosophy behind all of this: https://lifefocuser.com/building-focuser/you-think-you-know-where-your-time-goes-you-probably-dont

posted to Icon for group Startups
Startups
on March 5, 2026
  1. 1

    The first $500 MRR is the hardest milestone because everything is manual and nothing compounds yet. The founders who get through it are usually the ones with conviction about a specific problem rather than a general vision.

    What's the specific problem you're most confident about solving?

  2. 1

    The 'highlights vs. averages' insight is more broadly applicable than personal productivity — it's a general failure mode in any system where you're measuring yourself.

    SaaS founders have the same problem with payment failures. Ask most founders what their failed payment rate is and they'll say 'not that bad' or 'we handle it when it comes up.' What they're describing is the highlight: the time someone called in and they fixed it manually. The average is 5-9% of monthly subscription charges failing quietly at any given time, most without the customer even knowing, most without the founder noticing in the standard Stripe dashboard.

    The mental model says 'I would have seen it if it was a real problem.' The actual data says the opposite — it looks like regular churn, it doesn't fire an alert, and by the time you'd naturally notice, you've lost weeks of recovery window.

    Your framing of 'visibility prompts change' is exactly right. Once you can see the number, it becomes unmistakable. Without something to surface it, the highlight ('we fixed one last month') overrides the average ('we're losing 6% MRR to this every month').

  3. 1

    The gap between estimated and actual time is brutal — especially for founders who context-switch constantly. You think you spent the morning on product, but 40% of it was reactive Slack/email and the rest was shallow work that felt productive.

    One thing that's helped me: treating AI interactions the same way. Most people think they're 'prompting efficiently' but they spend 10 minutes iterating on a vague prompt when 2 minutes of upfront structure would get it right first time. That's the whole premise of flompt — a visual prompt builder that makes you define role, objective, constraints, and output format before sending anything to the AI. Turns out the discipline of structuring inputs saves far more time than it costs.

    A ⭐ on github.com/Nyrok/flompt would mean a lot — solo open-source founder here 🙏

Trending on Indie Hackers
AI runs 70% of my distribution. The exact stack. User Avatar 180 comments I'm a solo founder. It took me 9 months and at least 3 stack rewrites to ship my SaaS. User Avatar 143 comments I used $30,983 of AI tokens last month in Claude code on $200/mo plan User Avatar 45 comments We could see our AI bill, but not explain it — so I built AiKey User Avatar 25 comments AI coding should not turn software development into a black box User Avatar 24 comments my reddit post got 600K+ views. here's exactly what i did User Avatar 19 comments