Kanban View in an ATS: Useful, But Not Always Enough
The Kanban board is appealing in an ATS, but it hits its limits much faster than you'd think. That's why the list view often remains indispensable. We explain everything in this article.
Kanban is everywhere. In applicant tracking systems, it is often presented as the modern way to manage applications: cards, columns, a visual pipeline. It looks great. But after watching hundreds of recruiters work day-to-day, we have reached an uncomfortable conclusion: Kanban hits its limits much faster than anyone admits.
At Jobaffinity, we offer both: Kanban view and list view. This is not a coincidence, nor a luxury. It is because we understand that each view has its context, and that forcing a single way of working already shows a misunderstanding of recruiting.
What Kanban Does Really Well
Inspired by Trello or Jira, Kanban represents each candidate as a card moved from one column to the next (CV received, interview, offer…). In certain situations, this is exactly what you need:
- Visualize a pipeline at a glance: where do candidates stand? Kanban answers immediately.
- Manage low volumes: with around twenty applications, cards stay readable and drag-and-drop is intuitive.
- Track a single position: few stakeholders, simple process — Kanban is enough.
- Present the pipeline to managers: its readability makes it an excellent pedagogical tool for non-HR teams.
In these cases, it is an effective view. The problem arises when you ask more of it.
Where Kanban Becomes a Bottleneck
Kanban has a structural problem: it is not designed to scale. And recruiting scales very quickly.
- As volume increases, columns pile up, cards multiply, and readability collapses. At 50, 100, or 300 applications, the board becomes unmanageable.
- When you need to sort or filter, the list view is far more effective. Application date, score, source, priority: these dynamic sorts do not work well with a card-based board.
- When searching for a specific profile, finding a candidate in a loaded Kanban is slow and frustrating.
- When multiple recruiters collaborate, structured exchanges, validations, and feedback between HR, managers, and leadership are difficult to orchestrate on a simple card. This is especially true in organizations that structure their recruitment process with multiple stages and stakeholders.
- When you want to analyze, Kanban falls short. Conversion rates per stage, average time-to-hire, source performance: this is a visual view, not a management tool.
- When multiple positions are open simultaneously, maintaining multiple boards quickly becomes unmanageable.
The Reality: Kanban Is a View, Not a System
Recruiting is fundamentally about data management: CVs, notes, evaluations, exchanges, scoring, history. It looks much more like a CRM than a sticky-note board. Kanban lets you visualize part of this reality, but it is not enough to manage it.
What This Means for Your ATS
This observation guided our choices at Jobaffinity. Rather than highlighting a visually appealing interface that would quickly reach its limits, we chose to offer both views and let the recruiter decide based on context.
Visualize your pipeline in Kanban for a global overview? Done. Switch to list view to sort by date, score, or source? Instant. The tool adapts to the reality of recruiting, not the other way around.
An ATS that only offers Kanban forces you to work in a single way. That is not flexibility — it is a choice made for you.
Comparison: Kanban View vs. List View in JobAffinity
| Feature | Kanban View (Cards) | List View (Table) |
|---|---|---|
| Ideal use | Visual and global pipeline tracking | Technical sorting, filtering, and bulk actions |
| Data volume | Optimal for small volumes (< 30 candidates) | Built to scale (100+ applications) |
| Readability | Excellent for a quick look at pipeline stages | Superior for comparing precise data (score, date) |
| Search | Slow and difficult in a loaded board | Instant thanks to search functions and filters |
| Collaboration | Ideal for presenting the flow to managers | Essential for structured HR/leadership exchanges |
| Analysis (KPIs) | Limited: visual view, no management capability | Precise: enables comparison of key indicators |
| Flexibility | Rigid if it is the ATS's only option | Adaptable to high-productivity needs |
The Takeaway: Don't Let the Tool Dictate Your Method
Kanban is a great visual ally. It is the "quick glance" tool that reassures managers and simplifies tracking for low volumes. But recruiting is a living, fast-moving discipline: as soon as applications start flooding in, that beautiful clarity can turn into chaos.
That is where the list view comes into its own. It is not less "modern" — it is simply more robust when it comes to sorting, comparing, and processing dozens of profiles with precision.
In summary:
- Use Kanban for status checks and to bring operational teams into the recruiting process.
- Switch to the list view as soon as you need to dig into data, filter by score, or manage bulk actions.
Ultimately, the real question is not which view is better, but whether your ATS is flexible enough to offer both. The tool should adapt to your daily life as a recruiter — never the other way around.
