The Kanban Method for Job Searching: Run Your Hunt Like a Project

Kanban was invented on Toyota factory floors in the 1940s to solve a problem that sounds nothing like job hunting: too much inventory piling up between workstations. The insight that fixed it — make work visible, limit how much is in progress, and pull new work only when there's capacity — turns out to fit a job search almost perfectly. A search is inventory flowing through stages, and the failure modes are the same: pile-ups, forgotten items, and no idea where the bottleneck is.

The board: five columns

A job-search Kanban board needs only five columns:

• Saved — roles you've found but haven't applied to. Your wishlist and staging area.
• Applied — submitted, waiting to hear back.
• Interviewing — any stage of live conversation, from recruiter screen to final round.
• Offer — the happy column.
• Rejected — closed applications. Don't delete them; they're data.

Each application is one card, and a card moves left to right as reality changes. That's the entire mechanism. Its power is that the board becomes a single glanceable picture of your whole search — which no list, folder of emails, or memory can offer.

Work-in-progress limits: the underrated part

Everyone copies Kanban's columns; almost nobody copies its best idea, the WIP limit — a cap on how many items may sit in a column at once. On a factory line it prevents pile-ups. In a job search it prevents the two classic collapses:

The Saved column hoard. Fifty saved roles and three applications sent is procrastination wearing a productivity costume. Cap Saved at ten. Adding an eleventh means applying to one or deleting one. The limit converts browsing into deciding.

The interview overload. Six simultaneous interview processes sounds like winning until you're doing live coding for one company an hour after a system-design round for another, prepping neither well. Most people do their best work with three or four live processes; past that, quality drops across all of them. If you're lucky enough to hit the cap, slow down new applications and pour the attention into converting what's live.

Reading the board as a diagnostic

After two or three weeks, your board starts talking:

This is the real payoff. Without a board, a struggling search feels like one undifferentiated wall of rejection. With a board, it becomes a specific, fixable stage — and specific problems have specific solutions.

Setting it up in two minutes

You can run this on a whiteboard with sticky notes, in Trello, or in a purpose-built tracker. Orbit ships the five columns ready-made, with drag-and-drop between stages, a follow-up date on every card, and an insights view that computes the stage-conversion diagnostics above automatically. It's free, needs no account, and stores everything in your own browser.