Kanban Board with Time Tracking: How to See Where Your Team's Hours Actually Go

Most small teams run two tools that never talk to each other: a kanban board that shows what is being worked on, and a time tracker that shows how long someone worked. The result is familiar — timers left running overnight, hours logged against the wrong project, and a Friday afternoon spent reconstructing the week from memory. A kanban board with time tracking built into every card removes that gap: the task and its hours live in one place, so the data is accurate without extra effort.

Why a separate time tracker usually fails

A standalone timer asks people to do two things at once: move a card on the board, then switch to another app and start a clock with the same name. Every context switch is a chance to forget. In practice this leads to three predictable problems:

1. Gaps. Short tasks — a quick fix, a call, a review — never get logged because starting a timer feels like more work than the task itself.
2. Mismatched names. The board says "Checkout redesign", the timesheet says "website stuff". Nobody can connect the two a month later.
3. After-the-fact guessing. When tracking is a chore, people fill in timesheets at the end of the week. Those numbers are estimates, not measurements.

When the timer lives on the card, starting work and starting the clock become the same action. You open the task, press start, and the hours are attached to the exact item on the board.

What "time tracking on a kanban board" actually means

There are three common ways tools combine the two ideas:

For a team of 3–30 people, the built-in option is usually enough. You don't need invoicing, payroll exports or approval chains — you need to see how long things take.

How to set it up in 15 minutes

Here is the setup we use ourselves for client projects at our studio. It works in any tool with a board and per-card timers; the examples use Teamflows because that's what we build.

1. Keep the columns simple

Four statuses cover almost every small-team workflow:

• Assigned — the task exists and has an owner, but nobody has started.
• In progress — someone is actively working on it. This is where timers run.
• In review — the work is done and waiting for a check by someone else.
• Done — accepted and closed.

Resist adding "Blocked", "Waiting for client" and "QA" on day one. Every extra column is a place where cards get lost. You can add nuance later with comments.

2. One task, one timer, one owner

Each card should have exactly one assignee. If two people work on something, split it into two cards. That way the time on each card belongs to one person, and the totals mean something.

3. Agree on start and stop rules

Write down three sentences and pin them in the team chat:

• Start the timer when you move a card to "In progress" and actually begin.
• Pause it when you switch to another task, go to lunch or join a meeting unrelated to the card.
• Stop it when you move the card to "In review".

That's it. The rule matters more than the tool — without it, half the team tracks and the other half doesn't.

4. Invite the team

In Teamflows, you create a team, share an invite code or link, and assign roles: the owner manages the team, admins create and assign tasks, members work on tasks and track time. People can join from the iPhone app or the browser.

What to do with the numbers

Tracked time is only useful if someone looks at it. Once a week, spend ten minutes on these questions:

• Which tasks took much longer than expected? Look for patterns: is it always the same type of work, the same client, the same stage?
• Where does time go that isn't on the board? If a person worked a full week but their cards show 20 hours, the missing hours are meetings, support or interruptions — worth making visible as cards.
• How long do cards wait in "In review"? Waiting time doesn't show up on a timer, but it's often the biggest delay in a small team.

After a month you'll have real data for estimates. "A landing page takes about two days" becomes "our last five landing pages took 11–14 hours of work and three days calendar time". That's the kind of number clients and managers trust.

Common mistakes

• Tracking everything to the minute. The goal is visibility, not surveillance. Rounded, honest numbers are more useful than precise but resented ones.
• Using time as a performance score. The moment hours become a ranking, people start gaming them. Use time to improve estimates and find bottlenecks, not to compare colleagues.
• Too many columns. A board with nine statuses looks thorough and gets ignored. Start with four.
• Forgetting personal tasks. Not everything belongs on the team board. A separate personal list — for example, an Eisenhower matrix — keeps private to-dos out of the shared space.

Frequently asked questions