How to configure a Kanban board that stays readable
Good Kanban board configuration means each stage shows only the fields that matter at that stage, and colors distinguish cards without anyone tagging them by hand. In Jestor, both are configured per phase, so a negotiation card and a closing card can display completely different information.
Why boards get unreadable as they grow
A board usually starts clean and then accumulates. Someone adds a field that matters in one stage, and it appears on every card in every column, including the ones where it is meaningless.
Within a few months the cards are dense, the columns scroll and nobody can scan the board at a glance.
What clutters a board:
- The same fields displayed in every stage regardless of relevance
- Cards carrying information that only matters at the end
- Color used decoratively rather than to signal something
- Manual tags that people forget to apply
- Too much detail visible before a decision needs it
What to show at each stage
| Stage | What to display | What to hide |
|---|---|---|
| Qualification | Source, contact, potential value | Contract details |
| Negotiation | Full detail, next step, deadline | Post sale fields |
| Closing | Contract and signature status | Early qualification notes |
| Delivery | Owner and delivery date | Commercial history |
Step by step to configure it
- Create the board from the table holding the records.
- Define the stages so each one represents a real state of the work.
- Choose the fields per stage, showing only what a person needs to decide there.
- Set the conditional color rules, tying color to a field value rather than a manual tag.
- Configure sorting and filters so the most relevant cards surface first.
- Review after a month and remove any field nobody actually reads.
Why conditional color beats manual tagging
A color someone has to apply is a color that stops being applied. A color derived from a field value stays correct forever, because it reflects the data rather than someone's diligence.
- Color by rule: cards differentiate themselves based on their own values
- Fields per stage: relevance changes as work progresses, and the board follows
- Created in one click: a board can be generated from any table
- Customizable throughout: colors, displayed fields, sorting and filters
Frequently Asked Questions
Can different stages show different fields?
Yes. Each phase can display its own set of fields on the card. See jestor.com.
Do I have to color cards manually?
No. Conditional rules apply color based on the values in the record.
How do I create a board from existing data?
A Kanban can be created in one click from any table you already have.
Video Tutorial: Step by Step
With Jestor, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.