TL;DR
A kanban board is a visual board where tasks move through columns (e.g., To Do → In Progress → Done). Columns = workflow stages. Drag tasks between columns to update status. Start with 3–4 columns; add custom fields and labels as you need them.
Overview
Kanban boards are the foundation of work flow in Milestonea visual canvas where tasks move from start to finish. Columns = stages, tasks = work items, movement = progress. This guide covers how to make your board work for your team.
Prerequisites: A workspace and at least one board.
What Makes Kanban Boards Powerful
| Element | What It Represents |
|---|---|
| Columns | Workflow stages (e.g., To Do → In Progress → Done) |
| Tasks | Units of work that move through the pipeline |
| Movement | Progresseach drag signals "this moved forward" |
Why teams love it: Shared understanding across time zones, instant visibility (no "what's the status?"), and full customizationyour columns match how you actually work.
| Team | Typical Columns |
|---|---|
| Software | Backlog → In Progress → Code Review → Testing → Done |
| Marketing | Ideas → Planning → Creating → Review → Published |
| Support | New → In Progress → Waiting → Resolved |
Tasks and Their Journey
Each task is a trackable unit of work that carries context as it moves: descriptions, assignees, due dates, labels, checklists, attachments, and comments.
Moving a task signals progress: status updates, notifications, automations (e.g., assign to QA when moved to "Review"), and Slack/email updates. Keep the board current and your team stays aligned.
Visual Workflow Management
Kanban surfaces bottlenecks at a glancee.g., 15 tasks in "In Progress" vs 2 in "Testing." Distributed teams see the same board in real time; no status meetings needed.
Milestone adds AI insights: spots stuck tasks, suggests breaking down complex work, and recommends optimizations.
Customization and Flexibility
Add, remove, rename, or reorder columns as your workflow evolves. Custom fields add team-specific data; labels color-code by priority, project, or initiative for quick scanning.
| Team | Useful Custom Fields |
|---|---|
| Engineering | Story Points, Sprint, Tech Stack |
| Content | Word Count, Target Audience, Channel |
| Product | Priority Score, Customer Segment |
Getting Started
Start with 3–4 columns; add more as needed. Options: Create with AI (describe your workflow in plain language), use a template (Kanban, Scrum, Product Launch), or blank board (full control). Let real usage guide refinementsdo tasks get stuck? Are stages missing?
Best Practices
- Stay focused 4–7 columns max; more breaks visual clarity
- Limit WIP Cap "In Progress" tasks; Milestone can enforce this
- Make updates easy Drag and drop, shortcuts, or AI: "Move this to In Review"
- Use the board as communication Point people to the board instead of status meetings
Your board is your shared source of truth.
Advanced Features
| Feature | What It Does |
|---|---|
| Subtasks | Break complex work; parent stays visible |
| Dependencies | Show what blocks what |
| Milestones | Group tasks for project visibility |
AI assistant: Ask "What tasks are overdue?" or *"Who has the most work in progress?"*no filters to configure. Real-time collaboration: changes appear instantly for everyone.
Next steps
Create your first board, generate one with AI, or set up automations to move tasks automatically.