# Why Kanban in Salesforce?

### What Is a Kanban?

A **Kanban** is a visual project management tool that organizes work into columns representing stages of a process. Each piece of work — whether a deal, a task, a support ticket, or any other record — appears as a card on the board. As work progresses, cards move from one column to the next, giving everyone on the team an immediate, at-a-glance understanding of where things stand.

The concept originates from lean manufacturing and has since become a cornerstone of modern workflows across sales, service, operations, and beyond. At its core, Kanban answers three simple questions:

* **What needs to be done?**
* **What is currently in progress?**
* **What has been completed?**

Rather than digging through lists, reports, or spreadsheets, teams can see the full picture in a single view — and act on it directly.

### Salesforce Is More Than a CRM

While it began with CRM use cases, today it is widely used as an application platform for building and customizing business-critical solutions. Organizations extend standard objects with custom fields, create entirely new custom objects, and assemble company-specific apps that support core operational processes.

As a result, the data stored in Salesforce often goes far beyond contacts and opportunities. Depending on the business, it may include manufacturing orders, loan applications, inspection reports, project milestones, onboarding tasks, service workflows, or other domain-specific records.

That data still often appears in structured, record-based interfaces such as list views and record pages. Those interfaces are effective for data entry and lookup, but as processes become more operational and multi-step, teams can lose visibility into status, bottlenecks, and next actions.

This is where **Kanban becomes especially valuable**. By turning Salesforce records from either standard or custom objects into a visual board, **teams get a clearer, more actionable view of work in progress**.

### What Kanban Solves in Salesforce

#### Visualize Any Business Process, Not Just Sales

Whether your team manages deals, service requests, loan approvals, job orders, or any other custom workflow, a Kanban board can represent it visually. Any object with a stage or status field is a candidate — standard or custom.

#### Prioritize and Triage Work at a Glance

Instead of reading rows in a list view, teams see cards in columns. Bottlenecks are obvious. What needs attention today is immediately visible. No report needed.

#### Take Action Directly on the Board

Moving a card from one column to the next updates the underlying Salesforce record in real time. Teams act on the board rather than just reading it — which means fewer clicks, less context switching, and faster execution.

#### Improve Team Coordination

When everyone works off the same board, miscommunication drops. Team leads can reassign work by dragging and dropping cards. Everyone knows what is blocked, what is moving, and what needs a decision.

#### Bring Clarity to Custom and Industry-Specific Apps

Custom Salesforce apps built for specific industries or company workflows often have data models that don't map neatly to standard list views. Kanban cuts through that complexity, giving users a clear visual interface that reflects how their actual work flows — not just how the data is structured.

### Where Kanban Adds the Most Value in Salesforce

Any object with a picklist field representing progression — standard or custom — is a candidate for a Kanban board. The table below shows just a sample of the scenarios where Kanban provides immediate value.

| Use Case                          | Object        | Kanban Columns     |
| --------------------------------- | ------------- | ------------------ |
| Pipeline management               | Opportunity   | Sales Stage        |
| Case management                   | Case          | Status             |
| Lead qualification                | Lead          | Lead Status        |
| Project tracking                  | Custom Object | Phase / Milestone  |
| Onboarding workflows              | Custom Object | Step / Stage       |
| Loan or application processing    | Custom Object | Application Status |
| Field service work orders         | Work Order    | Work Order Status  |
| Manufacturing or production steps | Custom Object | Production Stage   |
| Inspection or audit tracking      | Custom Object | Review Status      |

***

### What About Salesforce Kanban View?

Salesforce does include a built-in **Salesforce Kanban View** — a basic card-based interface available on standard list views. While it offers a simple visual overview, it comes with significant limitations that make it impractical for teams with more demanding or complex workflows:

* Cards can display a maximum of 4 fields
* Only up to 200 records can be shown at a time
* Columns are locked to a one-to-one mapping with individual picklist values, with no support for merging values, using other field types, or defining columns using conditional logic — see [Rigid Column Logic](https://claude.ai/chat/a15cae4f-0f4c-437a-8ab4-dd153a21f1ca#rigid-column-logic) below
* Filtering options are basic, with no support for complex or dynamic criteria
* Automation triggered by card movements is limited to backend operations only — invisible to the user and disconnected from their interaction with the board — see [Workflow Automation and Interactivity](https://claude.ai/chat/a15cae4f-0f4c-437a-8ab4-dd153a21f1ca#workflow-automation-and-interactivity) below
* Customization of card appearance and layout is not possible

For teams running straightforward processes on standard objects, Salesforce Kanban View may be sufficient. But for organizations that have extended Salesforce into a full business platform — with custom objects, complex workflows, and higher data volumes — these constraints quickly become a bottleneck.

That is the gap **Flexi Kanban** is built to fill. To learn more about how Flexi Kanban addresses these limitations, continue to [What is Flexi Kanban?](https://claude.ai/chat/02-what-is-flexi-kanban.md).

***

### Rigid Column Logic

The column constraint in Salesforce Kanban View deserves a closer look, because its impact goes beyond what a brief bullet point can convey.

Salesforce Kanban View columns are locked to a one-to-one mapping with individual picklist values — one value, one column, no exceptions. In practice, this creates three distinct problems.

**You cannot consolidate multiple picklist values into a single column.** If you want a unified "Closed" column on an Opportunity board, you cannot have one. Closed Won and Closed Lost will always appear as separate columns, whether or not that distinction is useful for how your team works.

**Columns can only be driven by a single picklist field.** No other field type can serve as the basis for grouping. If the field that best represents your workflow's progression is a formula field, a checkbox, a date, or any field other than a picklist, it cannot be used.

**There is no way to define a column using conditional logic.** Consider an "Attention Needed" column — one that surfaces any opportunity missing key fields, past a certain close date, or flagged by any combination of business criteria. That kind of column, which reflects how teams actually think about prioritization, is simply not possible in Salesforce Kanban View.

Flexi Kanban removes all three constraints. Columns can group any combination of picklist values, draw on different field types, and be defined using formula-based conditions — giving teams the flexibility to build boards that reflect their actual workflows rather than the shape of their data.

***

### Workflow Automation and Interactivity

Salesforce Kanban View does support a narrow form of automation: when a user moves a card to a new column, the underlying picklist field updates, and admins can build record-triggered flows on top of that — creating records, sending emails, or performing other backend actions. However, everything that follows happens invisibly. The user who moved the card sees nothing. There is no visual response, no confirmation, no connection between what they did on the board and what the automation did behind the scenes.

Flexi Kanban expands this in two directions.

**Handlers** make individual cards and card elements interactive. Admins can configure what happens when a user clicks on a card or on any specific element within it — such as a field, a button, or a label. Actions can include opening a modal, navigating to another page, or applying an on-the-fly filter to the board. That last capability — where clicking an element like an account name instantly filters the entire board to show only cards sharing that value — is what makes drill-down workflows possible directly within a session, without leaving the board or running a separate query.

**Kanban Workflow** gives admins control over how cards are allowed to move between columns. This includes defining which column transitions are permitted, requiring a user action or confirmation before a move is completed, triggering backend automation on move, and restricting which users are allowed to make which transitions.

Both capabilities are covered in detail in the [Features](https://claude.ai/features/) section.