Youno

Tasks in. Work done. youno.si

← All insights
Operations

A Simple Way to Track Daily Work: Why Jira and Asana Don't Fit

Jira and Asana are built for work that takes weeks. Most of what decides whether today went well was handed out after lunch and is due before the shift ends.

Anurag JoshiAnurag JoshiFounder, Youno4 Aug 20268 min read

There's a specific kind of work that almost no task tracking software serves well: daily work. It isn't strategic, it isn't planned, and it never appears on a roadmap. It is the sentence somebody says at 2 PM that has to be true by 5. And it is, in most operating businesses, the work that actually decides whether the day went well.

What Jira and Asana assume about your work

Jira, Asana, Monday and the rest are good software built on a coherent set of assumptions. Work is known in advance. It is big enough to be worth describing. It has an owner, an estimate and a place in a sequence. Someone plans it, someone works it, someone reviews it, and that cycle takes days or weeks.

Every one of those assumptions is false for daily operational work, and they're false in a way that compounds.

Project workDaily operational work
When it appearsPlanned in advanceMid-conversation, unplanned
How long it livesDays to monthsHours
Who describes itWhoever plans itNobody. It was just said out loud
UnitA ticket with fieldsA sentence
What failure looks likeA slipped sprintA truck leaves without the batch
Right toolJira, AsanaThe conversation it was made in
Two kinds of work that look similar and behave nothing alike

Why your team stops updating the task app

There's a simple ratio underneath every failed rollout of task software into an operations team. Call it the recording tax: the time it takes to log a piece of work, divided by the time the work itself takes.

The workDoing it takesLogging it takesTax
Rebuild the payment module3 days2 min0.1%
Write and review a client report2 hours2 min1.6%
Send the revised quote to Patil10 min2 min20%
Confirm the dispatch time with the driver3 min2 min67%
The recording tax, at two minutes per ticket

Above the line, logging is obviously worth it and people do it without being asked. Below the line, no amount of policy will make it happen, because the person can see that writing it down costs more than just doing it. They are not being undisciplined. They are being correct.

If recording the task takes longer than doing the task, the task will not be recorded. No training fixes arithmetic.

Backlogs are the wrong shape

There's a second mismatch that shows up a month in, once a team has tried hard to use a project tool for daily work. Project tools accumulate. That's a feature: a backlog is a considered list of things worth doing eventually, groomed and re-prioritised.

Daily commitments don't work like that. “Dispatch batch 3 by 4 PM” is either true by 4 PM or it is history. Carrying it forward for three weeks doesn't make it more likely to happen. It makes a list that nobody can look at without feeling behind. Teams that push daily work into a backlog end up with hundreds of stale items, and then they stop opening the tool at all, which takes the *real* project work down with it.

This is why the list should show what is open now, newest first, with how long ago each task was given. What matters is whether it happened, not that it sits in a backlog for weeks.

A simpler way to track daily tasks

  1. Keep your project tool for the planning horizon. Roadmaps, releases, audits, anything measured in weeks. It's good at that and replacing it would be a mistake.
  2. Stop trying to push daily work into it. You will lose that argument every busy week, quietly, and blame the team for it.
  3. Track daily tasks where they are handed out, in the conversation, with no extra step for the person giving or taking them.
  4. Close them, don't groom them. A task stays until somebody marks it done or not needed. If a task for Tuesday is still open in March, the list shows it plainly, and somebody closes it.
  5. Judge it on one number: how often does a human have to chase another human for a status update? That's the number a fix should move.

Doesn't this just mean two tools instead of one?

Practically, most teams already have two: a project tool that the managers keep updated, and a chat where the actual day happens. The choice isn't between one tool and two. It's between two tools where one of them quietly doesn't work, and two tools where each does a job somebody can name. The second one is cheaper, even when it costs more.

Anurag Joshi

Written by Anurag Joshi, Founder, Youno, Youno. General guidance on running a team, not professional or legal advice for a specific situation.

Youno: the work chat that remembers

Ready to stop holding everyone's work in your head?

Free to start · Ready in ten minutes · No card