The Kanban Method: How to Manage Projects with Cards

The concept is deceptively simple — a board with columns, cards with tasks, and one rule: don’t start something new until you finish what’s already on your plate. But behind that simplicity is a well-designed system for managing workflow.

Here’s how Kanban works, and why a method born on Japanese factory floors ended up being a favorite of software engineers, marketers, and designers worldwide.

• What Is the Kanban System: From the Factory Floor to Your Workflow
• Kanban Principles: Evolution, Not Revolution
• The Kanban Process: Work Must Flow
• Kanban Planning Step by Step: How to Get Started

What Is the Kanban System: From the Factory Floor to Your Workflow 

Kanban is a workflow management method that helps you visualize tasks and track project progress. In plain English, Kanban is about putting all your work on cards and organizing them into columns: “To Do,” “In Progress,” “Done.” As tasks get completed, cards move from left to right, one column to the next.

The biggest benefit? Problems become visible to everyone on the team. Instead of guesswork and assumptions, you see the real picture: where tasks pile up, what’s causing slowdowns, who’s overloaded. For example, if your dev team’s “Code Review” column is constantly packed with cards, the bottleneck clearly isn’t development speed. You either need to automate parts of the review process or bring in more senior engineers to help with code reviews.

Kanban is highly adaptable and works for any stage-based process — from software development and apparel manufacturing to recruiting and processing customer requests.

Elements of the Kanban System 

Kanban systems come in two flavors: physical and digital. Physical boards work great for teams sharing an office — everyone can see the board, and it doesn’t depend on the internet or devices.

Digital boards are essential for remote work and large teams — you can access them from anywhere, they automatically track metrics and task completion times, send notifications, and maintain a full change history.

Here are the core Kanban elements:

• Board — the main tool of the system, divided into columns representing work stages. The basic structure: “To Do” → “In Progress” → “Done.” More complex boards can include dozens of stage columns — from “Backlog” and “Analysis” to “Testing” and “Deploy.”
• Cards — individual tasks. Each card contains the work description, the person responsible, a deadline, and other important details. Cards move across the board to show progress.
• WIP limits — caps on the number of cards allowed in each column. Think of limits as the antidote to multitasking — they force teams to actually finish work before starting something new..
• Swimlanes — horizontal rows that divide the board by work type, project, or priority. They help keep tasks organized and prevent confusion.
• Commitment point — the moment when the team takes on a task and starts working on it.
• Delivery point — the moment when a task is considered fully complete.

Kanban Pros and Cons 

Kanban, like any other method, isn’t a silver bullet — it doesn’t work for everyone. Along with its strengths, it has limitations worth knowing before you commit.

What Kanban delivers: you see the team’s real workload (not just plans on paper), and bottlenecks surface fast. Teams that adopt Kanban often cut task completion times by two to four times — as documented in the Vanguard case study.

Where Kanban falls short: projects with hard deadlines and fixed scope, teams that aren’t ready for self-organization, and situations requiring detailed planning months in advance.

Kanban Principles: Evolution, Not Revolution 

Kanban isn’t about “move fast and break things” — it’s quite the opposite. The method says: first, understand your current processes, then improve them in small, manageable steps. The philosophy of Kanban is captured in six principles.

1. Start with what you do now. You don’t need to fire half the team and rewrite every process from scratch. Take what you’ve got and put it on a Kanban board. Already have approval and review procedures? Great. Kanban will show you where the bottlenecks are, and then you can decide what to do about them.
2. Pursue incremental change. Big changes scare people and often fail. Kanban works differently: you spot a problem, try a small fix, and see what happens. Tasks getting stuck in testing? Set a WIP limit of 7 cards in “In Progress” instead of 10. Didn’t help? Try a different approach.
3. Encourage leadership at every level. Great ideas can come from anyone, not just the boss. A developer notices that code review is bottlenecking the whole team? Let them propose a fix. In Kanban, anyone can be the one who drives improvement.
4. Focus on customer needs. Every card on the board should ultimately deliver value — to a customer, a colleague, or the business. If you can’t explain why you’re doing a task and who it benefits, maybe it shouldn’t be on the board at all.
5. Manage the work, not the people. Instead of micromanaging who’s doing what and when, Kanban tracks how tasks move through the system. People decide for themselves what to pick up and how to get it done. The manager’s job isn’t to breathe down everyone’s neck — it’s to remove obstacles and keep work flowing smoothly.
6. Review and adapt regularly. Your Kanban board isn’t set in stone — you can and should change it. Need a new column? Add it. WIP limits too tight? Adjust them. The system should evolve with the team, not become rigid dogma
   

   

The Kanban Process: Work Must Flow 

Kanban is built around seven core practices that help teams manage task flow and continuously improve their processes. While these practices work best together, you can roll them out gradually — start with visualization and WIP limits, then add more elements when your team is ready.

Here are the core Kanban practices:

• Visualization — create a Kanban board where every task is a card and columns represent workflow stages. Start with three basic columns (“New,” “In Progress,” “Done”). Each card should include what needs to be done, who’s responsible, and the deadline.
• WIP limits — set the maximum number of tasks allowed in each column. For example, write the limit right in the column name (“In Progress [3]”) so everyone sees the cap. Once it’s hit, no new tasks get pulled in until current ones are completed. Start with soft limits and adjust based on results.
• Flow management — track key metrics: cycle time (how long a task takes to complete), throughput (number of completed tasks per period), and lead time (time from request to delivery). Review these weekly to assess team performance.
• Spotting bottlenecks — watch where tasks pile up on the board. If a specific column is constantly overflowing with cards, that’s a red flag. Find the root cause and eliminate the bottleneck.
• Explicit policies — set clear criteria for when tasks move between columns. For example, “ready for testing” means the code is written, documented, and passes all automated tests. If your company has standards, use them. If not, document the rules right on the board: create a card with your team’s ground rules and pin it where everyone can see it.
• Feedback loops — run daily 10–15 minute standups to sync the team, weekly metric reviews to analyze effectiveness, and retrospectives every 1–2 weeks to plan improvements.
• Collaborative improvement — all process changes are discussed and tested as a team. Someone suggests changing the WIP limit? Try it for a week, then analyze the result together. Didn’t work? Roll it back. Did work? Keep it. Anyone can propose an improvement, but the decision is made by the team.

Kanban Project Management: Stages and Cycle 

Picture a typical workflow: Backlog → To Do → In Progress → In Review → Done. The Kanban cycle time starts at the “In Progress” stage and ends at “Done.” The full lead time runs from the moment a request appears to completion — from “Backlog” to “Done.” Lead time shows how long the customer waits for a result; cycle time shows how efficiently the team works.

Here are the standard Kanban stages:

• Backlog — the warehouse of ideas and requests that haven’t been prioritized yet.
• To Do — tasks that are ready for work, lined up by priority.
• In Progress — active work, usually with the strictest WIP limits.
• In Review — review, testing, approvals.
• Done — fully completed tasks.

Your Kanban board columns should reflect the real stages of your specific team’s workflow. A content team might break things down into research, writing, editing, and design. A dev team would add code review, testing, and deployment stages. An HR department would map out their hiring pipeline. The golden rule: every column should correspond to an actual work stage, not an abstract concept.

Kanban in Action: How the SingularityApp Team Ships Product

The SingularityApp team didn’t just add Kanban as a feature in the app — we use the Kanban methodology to build the product itself, so we know its ins and outs from hands-on experience.

Our process includes over 20 stages: from initial idea to updating the documentation on the website. In SingularityApp, this looks like a Kanban board with columns for every step: development → automated tests → code review → QA testing → build → smoke tests → app store release → moderation → production verification → knowledge base update.

A special feature of our workflow is a fast lane for priority improvements: important features move through the entire pipeline with high priority, and daily standups help us make sure “urgent” doesn’t take over the board. And yes, the Kanban board in SingularityApp supports that level of complexity: sections for task types, up to 25 columns, and flexible priority management.

The result: every feature goes through rigorous quality control, and the Kanban visualization lets us spot bottlenecks early.

Kanban Planning Step by Step: How to Get Started 

The most common beginner mistake when setting up a Kanban system is building an overly complex board with a million columns right out of the gate. The method never sticks, and the abandoned board joins the collection of “tried it, didn’t work.”

Successfully adopting Kanban takes a methodical approach: first, understand your processes, then gradually visualize and improve them. Here’s how to do it, step by step.

Step 1: Analyze your current workflow. Before building a board, pick one typical task and trace its path from start to finish. Write down every step: who does what, how long it takes, and where the task might get stuck. This information becomes the foundation for your future Kanban columns.

Step 2: Switch to Kanban mode in SingularityApp. Create a new project for your tasks or open an existing one in SingularityApp. Switch to Kanban mode by clicking the board icon in the upper right corner. Three default columns are created automatically: “New,” “In Progress,” “Done.” That’s a solid starting point for most workflows.

Step 3: Customize columns for your workflow. Rename the default columns or add new ones to reflect your real work stages. For a content team, that might be “Ideas,” “Research,” “Writing,” “Editing,” “Done.” For developers — “Backlog,” “Development,” “Code Review,” “Testing,” “Deploy.” You can add a column using the plus icon between existing columns or through the column menu.

Step 4: Move your tasks onto the board. Add all current tasks to the Kanban board. Create new tasks with the Cmd/Ctrl + N shortcut — they’ll automatically land in the “New” column. Drag existing tasks into the right columns based on their current status. In SingularityApp, tasks in Kanban mode keep all their properties: dates, deadlines, tags, and priorities.

Step 5: Set WIP limits. SingularityApp doesn’t enforce hard technical WIP limits that block you from pulling in more tasks. But you don’t need hard limits to follow the principle — soft methods work fine: add the number to your column name (“In Progress [3]”) or document it in your project guidelines. The key is actually respecting those limits — that’s what makes Kanban effective.

Step 6: Organize with sections. If you have multiple task types or projects, use sections to group them. In SingularityApp, sections are preserved when you switch to Kanban mode. You can create sections for different clients, work types, or team members.

Step 7: Set up your daily board routine. Start every day by reviewing your Kanban board. Move tasks between columns as they progress — in SingularityApp, it’s a simple drag-and-drop. When a task is done, move it to the “Done” column — it’ll automatically be marked as completed.

Step 8: Build in rituals and feedback. Run short daily standups at the board (if you’re working as a team) or do personal reviews (if you’re solo). Every 1–2 weeks, ask yourself: where are tasks getting stuck? Which columns are overflowing? What needs to change in the process?

Step 9: Continuously improve the system. Kanban is all about continuous improvement. Add new columns when you need more granularity in your process. Remove ones that aren’t being used. In SingularityApp, it’s easy to experiment with your board: columns can be renamed, moved, and deleted at any time.

Step 10: Scale to other projects. Once Kanban is working for one project, apply the same approach to other areas. In SingularityApp, you can create separate Kanban boards for work projects, personal tasks, learning goals, and anything else on your plate.

Kanban doesn’t click overnight — give yourself 2–3 weeks to get used to the system. Don’t bail if it feels awkward at first. Most teams don’t see the real payoff until about a month of regular use, once there’s enough data to analyze and improve. The key is to start simple and build from there.