Uncomfortable question: when was the last time your hiring pipeline was actually up to date?
Not “more or less.” Not “most candidates.” Up to date — row by row, column by column, every candidate exactly where they should be. If the answer is “never” or “it’s been a while,” you’re not alone. That’s the rule, not the exception.
The hiring kanban is sold as the solution to process chaos. In practice, most teams abandon it within six weeks. It ends up living out of date, in parallel with a Sheet, a Slack thread, and one recruiter’s memory.
This post is about why that happens and what the 20% that actually works does differently.
Why a hiring kanban fails
There’s a very clear pattern when a pipeline gets abandoned. It’s not about lack of training or resistance to change. It’s that the recruiter feels updating it is bureaucracy, not work.
If I ask you to drag a card from “Interview 1” to “Interview 2” and you get nothing in return — no insight, no shortcut, no alert — your brain files it as administrative tax. And administrative tax is the first thing that gets dropped when real workload hits.
The broken kanban has five symptoms:
- Out-of-the-box stages. Generic stages that don’t match how the company actually hires.
- Manual moves with no added value. Moving a card doesn’t surface anything visible.
- No information on the card. The recruiter has to click in just to remember who that candidate is.
- Zero alerts. The system doesn’t tell you when something is stuck.
- Isolated from the rest of the flow. The kanban doesn’t connect to the assessment, the interviews, or sourcing.
A kanban that DOESN’T get used vs one that does
| Criterion | Kanban that doesn’t get used | Kanban that does |
|---|---|---|
| Stages | Generic, from a template | Configurable by company and by role |
| Moves | Drag & drop with no context | Drag & drop with fit score visible on each card |
| Bulk operations | One at a time | Bulk move to send 20 candidates to “rejected” or “next stage” |
| Card info | Name and an avatar | Name, fit score, source, days in stage, alerts |
| Alerts | None | Stalled vacancy, anomalous drop-off, candidates without feedback |
| Sourcing | Copy the LinkedIn URL by hand | Chrome extension adds candidates directly from LinkedIn |
| Approval workflows | By email, outside the system | Approval on the card, auditable log |
| Assessment integration | Manual: request the test separately | The test fires from the card |
The difference isn’t cosmetic. It’s that the second model saves the recruiter work instead of asking for extra work.
What makes a pipeline update itself
The right question isn’t “how do I get my team to update the pipeline?” It’s “how do I make updating the pipeline easier than not updating it?”
These are the levers we see working.
Stages configurable by company
Every company has its own process. A software scaleup runs “screening → technical → cultural → offer.” A BPO runs “screening → assessment → training → assignment.” A retailer runs “application → group → individual → offer.” A kanban with fixed stages loses against any of them.
The platform lets you define stages at the company level, with per-role adjustments inside that. This isn’t customization for customization’s sake — it’s the minimum condition for the team to see the kanban as their process, not one imposed on them.
Drag & drop with fit score visible
Moving a card shouldn’t be an act of faith. When the recruiter sees the candidate’s fit score against that specific role on the card, moving it becomes an informed decision. The score acts as an anchor: “this one is 87% fit, move it forward. This one is 42%, drop it.”
The fit score doesn’t replace the recruiter’s judgment. It accompanies it. And that accompaniment is what turns the kanban into an assistant instead of a task.
Bulk move
When a vacancy closes and you have to move 30 candidates to “rejected” with the same feedback email template, bulk move turns 30 minutes into 30 seconds. Adoption is won in details like this, not in the headline features.
Approval workflows inside the card
The hiring manager has to approve the candidate to move to offer. That approval can’t live in a lost email. It has to live on the card: the approver gets notified, approves or rejects with a comment, and everything gets logged. When legal or the CFO asks how that hire was approved, there’s an auditable answer.
Chrome extension for frictionless sourcing
The recruiter finds a candidate on LinkedIn. With the extension, that candidate gets added to the role with one click. The assessment invitation fires automatically. The card shows up in the kanban with the information already loaded. No copy-paste, no intermediate Sheet, no “I’ll load it later.”
That zero friction is what changes the mental economics of the process. If adding candidates is costly, candidates don’t get added. If it costs nothing, the pipeline fills itself.
The trap of “features” with no real usage
There’s a common bias when evaluating pipelines: comparing feature lists. “Mine has drag & drop, bulk move, Slack integration, AI suggestions, etc.” Features matter, but they matter less than actual usage.
A few more useful questions when choosing or auditing a pipeline:
| Question | If the answer is no… |
|---|---|
| Does the recruiter see immediate value when moving a card? | They’ll stop moving them |
| Are there alerts when something is stuck? | Abandonment won’t get detected |
| Can stages be customized without calling a consultant? | The real process will live outside the system |
| Does the card show fit score, source and days in stage? | The recruiter will be clicking in constantly |
| Is there a Chrome extension or way to add candidates without copy-paste? | The kanban will stay incomplete |
| Does hiring-manager approval stay inside the system? | You’ll depend on emails for audit trail |
If two or more answers are no, the pipeline will be used with discipline for the first 30 days and abandoned somewhere between day 60 and day 90. We’ve seen it in projects where we weren’t picked: the client comes back six months later asking us to migrate the Sheet that the real process ended up living in.
The pipeline as source of truth, not as a report
The second important mental shift: the pipeline is not a report. It’s the place where the process lives. If the process lives somewhere else — in Slack, in the recruiter’s head, in a Sheet — the pipeline is condemned to be out of date by definition.
This has concrete design implications:
- The assessment invitation gets sent from the card, not outside it.
- Interview feedback gets loaded on the card, not in a separate doc.
- Hiring-manager approval goes through the card.
- Notes and comments live on the card.
When all of that converges, updating the pipeline stops being a task — it becomes the side effect of doing the work.
How to migrate to a pipeline the team will actually use
If you’re coming from a broken process, these are the phases we see working:
Phase 1: define the real stages, not the template ones. Run a 90-minute workshop with recruiters and hiring managers. Map the process as it actually happens.
Phase 2: set up 2-3 minimum alerts. Stalled vacancy, anomalous drop-off, candidates without feedback for more than X days.
Phase 3: install the Chrome extension across the whole team. This is the piece that reduces friction on candidate entry. Without it, the pipeline starts empty.
Phase 4: kill the parallel Sheet. This is the most political step. If the team keeps its Sheet, the pipeline loses. There has to be an explicit decision: the source of truth is now the pipeline.
Phase 5: short weekly review. 15 minutes where the lead and the recruiter look at stalled candidates only, not all of them. If the tool is working, that review is fast.
How it fits with the rest
The pipeline doesn’t solve hiring on its own. It solves the coordination of the process. If you want to see how it connects with reporting, competency assessment and archetypes, here’s the hub post. And if you want to see the module in detail: /features/pipeline.
Implement this with us
If your team is living in a Sheet or in an ATS nobody updates, you don’t need another tool. You need a process that doesn’t feel like bureaucracy. We help you design the stages, configure the alerts and connect the Chrome extension to sourcing so the pipeline starts filling itself.
Questions? Email me at fran@talen.to.
Related OCEAN+ profiles
Discover which personality dimensions to look for in each role.
Related Articles
HR reporting that actually matters: what metrics to track beyond time-to-hire
Your CHRO doesn't want another dashboard. They want the dashboard to alert them when something breaks. A guide to the metrics that move the needle and the alert system that makes them actionable.
It's not a psychometric test, it's a hiring intelligence platform
Why Talen.to stopped being just an assessment and became ATS + assessment + reporting + workflows in a single platform. Pipeline, shortlists, interview panels, and reporting suite explained.
What Talen.to actually does (that you probably didn't know)
Our site communicates about 10% of what the platform actually does. Here's the full inventory: pipeline, reporting, multi-evaluator assessments, in-house calibration, and a lot more.