Blog
Why Taskora Kanban Stays Fast with Thousands of Cards
Written by Georgii Garanin, Founder, Taskora
A kanban board is easy to love at 40 cards. You see the work, you move the work, and the board remembers. Somewhere around the end of a first year, that same board holds a few thousand cards, and moving one starts to feel slow. The standard advice at that point is to archive aggressively and start each quarter with a clean slate.
We think that advice treats the symptom. Your board is the record of what your team did. Deleting the record to buy back speed is a strange trade, and with Taskora kanban you don't have to make it. The difference comes from one design decision about how cards are ordered, and it's why kanban board performance holds steady as the board grows instead of falling off a cliff.
Here's how that ordering works, what changes when you drag a card, and what it doesn't fix.
Why kanban board performance fades as a board grows
The textbook way to order a board is a straight line of whole numbers. The first card is 1, the second is 2, and so on down the column. It's simple, and it works fine on a board you rarely reorder.
It stops working once reordering becomes routine. Insert a card at position 400 and every card after it needs a new number. Drop a card at the top of a column holding 500 cards, and all 500 get rewritten. The cost of one drag grows with the size of the board.
That's the mechanism behind the sluggishness teams put up with. It shows up as the pause after a drop, and as the advice to archive half the board so it stops dragging. Both trace back to the same habit, renumbering on every move, and renumbering gets more expensive every time the board grows. When a tool behaves that way, "keep the board small" stops being advice and becomes a chore you can't skip.
How fractional ordering works
Taskora kanban boards order cards with fractional ordering. Every card carries an order value, and the only thing that matters is where that value sits between its neighbors.
Take a column with two cards. The top card has an order value of 1000. The next one has 2000. Drop a card between them, and it gets a value in between, say 1500. The neighbors keep their values. Nothing else on the board changes.
That's the whole idea, and it holds because between any two numbers there are always more numbers. There's room for the next card, and the one after that. A reorder touches one card. One card gets a new value, and the other cards on the board never hear about it.
Can the gaps run out? The values start far apart, and if one spot ever gets cramped, that one column gets re-spaced. That's one column of tidy-up, while the rest of the board stays untouched. Compare that with the straight-line version, where the same cramped spot means renumbering everything after it.
What a drag feels like at 3,000 cards
Mechanism is one thing. What you feel is another. Drag a card to the top of a long column. On the straight-line design, that drop renumbers every card below it, so the save gets heavier as the column grows. With fractional ordering, the drop writes one value, and the work is the same whether the column holds 30 cards or 3,000.
The card settles where you dropped it and stays there. Reordering stays cheap no matter how long the column gets. You move work, the board keeps up, and you get on with the day.
There's a quieter benefit too. A reorder that touches one card produces one small update, and small updates travel well. Teammates looking at the same board aren't absorbing a flood of renumbered cards after every move. On a busy board with several people working at once, this matters more. When a tool renumbers on every move, some of that sluggishness is the habit, not the size of your backlog.
What fractional ordering doesn't fix
Fractional ordering fixes the cost of reordering, which is the cost that compounds as a board grows. It doesn't make a ten-thousand-card board feel like forty cards, and we won't claim otherwise.
What it does mean is that board size stops being a maintenance problem. Archive what's genuinely done, when your team wants it out of sight. Don't archive as a maintenance chore to keep the tool quick. If a board has to be pruned every quarter to stay fast, that's the straight-line design showing through.
Why this matters more the longer your team runs
A growing team doesn't start with thousands of cards. It earns them, one sprint at a time. The board that held a two-week project in January holds a year of work by December, and the tool should treat that as success.
Taskora is built for growing teams, and its core unit is the stream. Streams are projects, and each stream has its own kanban board, so your product board can grow as long as it needs to while your hiring board stays lean. The longer case for streams, one board per project, is on our teams page.
Planning runs on sprints, and Taskora calls its own cycles waves. When a wave closes, unfinished tasks land in the Backlog, and the next sprint picks them up. Nothing vanishes, and nobody rebuilds the board by hand at the end of a cycle.
Documents with version history live next to the boards, so the decision behind an old card stays one click away. On a board with a long memory, that's what keeps the story readable.
Where your board lives
Taskora runs in the cloud for you, so there's nothing to operate. If your team wants the board on your own servers, self-hosting is available on request, and the ordering mechanism is the same either way. The longer case for running it yourself is on the data sovereignty page.
Put a big board through its paces
The test that matters is dragging your own backlog around for two weeks. Free, no credit card needed. After that, there's a 14-day free trial. Then it's one flat plan at $13 per seat per month billed monthly or $10 per seat per month billed yearly, with every feature included.
FAQ
What is fractional ordering in a kanban board?
It's a way of ordering cards where each card gets an order value between its neighbors. Reordering a card means writing that one card's value instead of renumbering everything after it, which is why a reorder stays quick on a large kanban board.
Will Taskora kanban stay fast with thousands of cards?
Drag and drop uses fractional ordering, so moving a card stays a small change even when the board has thousands of cards. That's the mechanism this article explains. Archiving for speed shouldn't be part of running your board.
How much does Taskora cost?
Free, no credit card needed. After that, there's a 14-day free trial, then one flat plan at $13 per seat per month billed monthly or $10 per seat per month billed yearly. Every feature is in that plan.
Can I self-host Taskora?
Yes, on request. Email hello@taskora.ai and we'll set you up with self-hosting on your own servers.
Related posts
- How to Choose a Task Management App for a Team of 5 to 20
How to choose a task management app for a team of 5 to 20. An 8-point checklist, what 10 and 20 seats really cost, and five contenders scored against it.
- Scrumban vs Scrum vs Kanban: Which to Pick and How to Switch
Scrumban vs Scrum vs Kanban with a plain answer up front. What you keep, what you drop, and how to move between them without losing your planning rhythm.
- What Is Project Management Software? A Plain-English Guide for Growing Teams
What project management software is, what it should include, and what it should cost a growing team, including why the advertised per-seat rate is rarely the one you pay.