The Ring: Why We Put Estimate Overrun on the Card

Most project management tools can track time.

Almost none will look you in the eye on the board and say this work already cost more than you said it would.

That is what the ring is for.

A small circle with a big opinion

On a Kiron card you see a number and a circular progress ring.

The number is effort logged. The ring compares that effort to the estimate.

While you are still inside the estimate, the ring stays calm. Neutral while the work is open, healthier once it lands clean. When you go past the estimate, it turns red.

No modal. No report. You do not have to open the issue and hunt for Work Ratio.

You glance the board the way you already do, and overrun is sitting there next to the assignee and the ticket ID.

That sounds like a UI detail. It is really a decision about what urgency means for us.

What other tools optimized for instead

Spend enough time in Linear, Jira, Asana, ClickUp, monday, Height, or Plane and a pattern shows up.

Time gets captured. Overrun gets deferred.

Linear keeps estimates and points close to the work. Logged time blowing past a budget is not really the board's language. Due dates exist. The board stays fast and thin.

Jira has serious time math: original estimate, remaining, Work Ratio, dashboards, Marketplace apps. On a default kanban card, almost none of that shows up. Power users color cards with JQL. Everyone else finds out in a report.

ClickUp is good at entering time. Timers, estimates, modals, expanded cards. The collapsed board still rarely screams overrun the way a red ring does.

Asana, Height, and Plane care more about workflow clarity. Calendar and status do more talking than spent-versus-estimate on every card.

Harvest and tools like it win at timesheets and budgets, often outside the board entirely.

The closest cousin we know is Kanban Tool. They put a bar on the card that turns red when tracked time exceeds the estimate. Same idea, different shape. We went with a ring so the signal stays small enough to live next to the other card chrome instead of eating the whole bottom edge.

The industry default, looking at real boards out in the wild, is roughly: log time somewhere, compare estimate to reality somewhere else.

Ours is: if it matters, put it on the card.

Why a ring, not another badge

A badge that says 33h is data.

A ring that fills toward an estimate and then flips color past 100% is data with a judgment call attached.

We meant that.

Boards are attention surfaces. Teams already scan for what the card is, who owns it, how important it is, and where it sits in the flow. We wanted a fifth glance question: is this still inside its time budget?

Due dates answer a different question. Are we late by the calendar? We do not use due dates in Kiron. That was not a forgotten Linear feature. It was a choice.

Estimates vs due dates

Due dates are great when the world runs on calendars. Launches, legal, clients, partners, events. "By Thursday" coordinates people who do not live in your board.

Estimates are better when the world runs on effort. Shipping teams, retainers, capacity, the quiet question behind a lot of slip: did we underprice this?

Knowledge work is messy. Due dates often turn into theater. Everything slips, gets renegotiated, gets ignored, or lands on Friday because Friday felt tidy. An estimate admits you are guessing, then measures how far the guess drifted once people actually log time.

Columns already handle sequence. Priority already handles pressure. The ring handles cost.

So our urgency is not red because a date passed. It is red because the hours did.

That will feel incomplete if your stakeholders only ask when. It will feel obvious if your pain is that you keep getting surprised by how long things took.

We built for the second group.

Linear having due dates does not make us wrong. They optimized for issue velocity and optional calendar metadata. We optimized for effort honesty showing up as a normal board state. Different priorities. If we copied their checklist just because they are Linear, we would end up a thinner Linear, not a clearer Kiron.

What changes on a real team

Overrun becomes something you talk about while the work is still movable. When red only lives in a report, the conversation happens after the sprint story. On the card, people can still split the work, ask for help, re-estimate, or cut scope.

Done does not wash the lesson away. We leave overrun visible on finished cards on purpose. Scan a Done column and you can see which wins were expensive. It is a cheap postmortem without opening analytics.

Estimates either get more honest or they get exposed. Some teams get better at estimating. Some start padding. Both outcomes tell you something. Empty rings tell you something too. If nobody logs time, a cost-based board is just decoration.

And the board stops lying by omission. A calm board full of invisible overruns looks healthier than it is. The ring makes things a little less comfortable and a lot more accurate.

What we cared about in the design

Keep it compact. Number plus ring, not a chart. Cards have to stay readable when the board is crowded.

Keep the meaning paired. Red sits next to the time number so it reads as over estimate, not blocked, not urgent, not overdue. Color alone is fuzzy. Color next to a quantity is clearer.

Make it default, not a power-user setup. Jira can get somewhere close with Work Ratio and card colors. We did not want "possible if you configure it." We wanted "visible if you estimate and log."

Accept that turning red is an opinion. Soft products dodge opinions. Boards that people rely on sometimes cannot.

The short version

Other tools ask whether you are late. Kiron asks whether you are over, in the same place your team already looks.

The ring is how that stops being optional.

Tracking time is not new. Closing the loop between estimate and reality on the kanban card still is, at least among the tools most teams actually use.

We put that in a circle on every card, and we let it turn red when the truth does.

Kiron: estimate, ship, see what it actually cost.