I've used a lot of productivity apps. Task managers, habit trackers, time loggers, spreadsheets with elaborate color-coding that I maintained religiously for about two weeks before abandoning them entirely.

The problem was never discipline. The problem was the apps themselves.
Most productivity tools are built around a simple promise: capture everything, and you'll feel in control. And they're not wrong — capturing is valuable. But somewhere between the input and the insight, something gets lost. You end up with a beautifully organized graveyard of tasks you never acted on, and metrics that tell you what happened without helping you understand why.

I ran into this problem while building a session management tool for poker players — a group who, it turns out, are obsessed with tracking and deeply frustrated by the tools available to them.

What Players Were Actually Doing

Before building anything, we talked to a lot of grinders. Here's what we found:

• Most were tracking sessions in spreadsheets they'd built themselves The spreadsheets captured results but couldn't answer questions like "which tournaments are actually worth my time?"
• There was no connection between planning a session and reviewing how it went
• Every tool they found was either too simple (just a results logger) or too complex (full hand history analysis software that required a CS degree to configure)

The gap wasn't in data collection. It was in the loop between planning, execution, and review.

The Three Layers Problem

Here's what I've come to think of as the core failure of most productivity apps:

Layer 1 — Input is usually well-designed. Adding a task, logging a result, recording a number — these flows get a lot of UX attention because they're the visible part.
Layer 2 — Storage is fine. SQLite, Supabase, whatever — the data goes somewhere.
Layer 3 — The feedback loop is where almost everything breaks.
Most apps treat layer 3 as a reporting afterthought: a stats page you visit once, go "huh, interesting," and then close. The data doesn't talk back to you. It doesn't shape your next decision. It just sits there, technically accessible.

In poker terms: imagine logging every hand you played for a year, but never being able to answer "am I actually profitable at $109 buy-ins, or am I just running hot?" The data exists. The insight doesn't.

What We Built Instead
We structured our app around three intentional phases:

1. The Session Builder
   Before a session starts, you plan it. You browse a tournament database, add events to your lineup, and see projected metrics — expected ROI, estimated hours, total buy-ins — before committing a dollar.
   This sounds obvious. Almost no tools do it. Most apps are reactive: you do the thing, then you log it. We wanted the planning phase to be a first-class feature, not an afterthought.

2. The Live Grind Panel
   During a session, you get a compressed real-time view: which tournaments are running, which are busted, what your current P&L looks like, one-tap result entry. It's designed to be glanceable in 2 seconds, not something you interact with for minutes at a time.
   The key insight here: during execution, the UI should get out of your way. Most productivity apps make you fill out forms when you're in the middle of doing the thing. We made the live view almost frictionless.

3. Session History + Statistics
   After the session ends, the data flows automatically into your history and stats. You can see ROI by game type, profit by buy-in level, hours played over time. But — and this is important — those stats link back to the session builder. If your $109 buy-in ROI is negative over 100 tournaments, that information is surfaced when you're planning your next session, not buried in a stats tab you have to go find.

The Insight We Kept Coming Back To

Productivity is a loop, not a list.

The tools that actually change behavior are the ones that close the feedback loop — where what you learn from past performance directly informs future decisions. Most apps are great at the list. Very few close the loop.

For us, that meant: the planning tool and the history tool had to be the same product, sharing the same data, designed to talk to each other. Not two separate features bolted together.

We're still iterating on this. The loop is never fully closed — there's always a better way to surface the right information at the right moment. But starting from "how do we close the loop" rather than "how do we capture more data" changed everything about how we designed the product.
If you're building something similar, I'd love to hear how you approached it.

The loop is closed. The data does something.

What I'd Apply Elsewhere
If you're building a productivity tool — or evaluating one for your team — I'd ask these questions:

Does planning exist as a feature, or is it assumed to happen outside the app?
Does historical data surface at decision time, or only in a reporting view?
How many taps does it take to log something during active use? (If it's more than 2–3, people will stop doing it)
Is the feedback loop explicit, or do users have to construct it manually?

The best productivity tools I've seen answer all four well. Most answer one or two.

We're still iterating on this. The loop is never fully closed — there's always a better way to surface the right information at the right moment. But starting from "how do we close the loop" rather than "how do we capture more data" changed everything about how we designed the product.
If you're building something similar, I'd love to hear how you approached it.