How to Set Kanban Columns for Beginners: Sample Boards for Sales, Hiring, Production, and Admin

Project & Development

How to Set Kanban Columns for Beginners: Sample Boards for Sales, Hiring, Production, and Admin

A beginner template for teams of 4 to 7 deciding kanban columns: pick the closest sample from sales, hiring, production, or admin, then set exit conditions and return columns. It has four pages: page 1 lists today's flow and jams so you can see the gap between your current columns and the ones you want, page 2 picks a close sample and rewrites it in your own words, page 3 tabulates each column's exit condition, return column, and reviewer to spot columns to add or cut, and page 4 sets the morning routine, the first work to run, and a review date two weeks out. The task board has five columns, from Write it out to Reviewed, with four parent tasks matching the four pages and three subtasks each. Use it when sticky notes pile up in the In progress column and you cannot tell which work is stuck. Your limited-visibility team can fill it in together. A return column is the column where work that fails the condition goes back. WIP limits are out of scope.

0 Likes 0 Copies Author: WeProcess
kanban kanban columns workflow task management for beginners
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode How to Set Kanban Columns for Beginners: Sample Boards for Sales, Hiring, Production, and Admin

Whiteboard preview

① Why You Are Rebuilding and Which Te... ② Today's Flow (from intake to done) ③ Where It Jams (steps where notes pi... ④ Waiting Time (waiting on someone's ... ⑤ Where Work Is Sent Back Often ⑦ Sample Columns by Use (pick the row... ⑧ Entry Column (receive) ⑨ Prep and Work Columns (plan, make) ⑩ Check Column (check, hand over) ⑪ Finish Column ⑫ Exit Conditions by Column (write th... ⑬ Which Columns to Add or Cut (place ... Clear condition x No pile-up Clear condition x Piles up Unclear condition x No pile-up Unclear condition x Piles up ⑭ Working Rules (decide from the retu... ⑯ Review in Two Weeks (the day you fi... Kanban Columns Sa... How to use (4 pag... Decided columns, ... Rules, conditions... Jams and send-backs Samples and insights 1/4 Map the current flow Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Pick a close sample ↙ 3/4 Reason for rebuildinge.g. 15 notes pile up in the In progress column and no one can tell which are stuck Team and worke.g. A production team of 5 handling about 20 flyer and document requests a month Current columnse.g. 3 columns - To do, In progress, Done(written by: ____) ReceiveA request arrivese.g. A request comes in by chat or email and the leader picks it up PlanSet owner and deadlinee.g. The owner is chosen at the morning meeting MakeDo the worke.g. Write a draft and gather materials CheckCheck the contente.g. The leader checks the text and numbers Hand overGive it to the requestere.g. Send it to the requester and wait for a reply DoneClose it oute.g. File it once an OK comes back e.g. 10 or more notes sit in the Make step e.g. Only one person checks, so nothing moves until they are free Add which step in ② it is e.g. Waiting on the requester stalls work for 3 days on average e.g. Work cannot start until materials arrive Write who you wait for and how many days e.g. The check finds typos and the work is redone e.g. The request changes after handover and work starts over Write which step it went back from and to ⑥ Gap Between Cur... As-Is (current state) e.g. Only 3 columns, so working, waiting for a check, and waiting for a reply are all mixed in the In progress column Gap / Issue e.g. You cannot tell why work is stuck from the columns, so split waiting and checking into their own columns. Write what was common in ③ to ⑤ and how to close the gap To-Be (target) e.g. You can see which step is stuck just by looking at the columns, and can move things along in 5 minutes each morning Entry column Prep column Work column Check column Finish column Sales Leads First contact made Proposing Quote check Won / Lost Hiring Applied Résumé screening Interviewing Offer check Hired / Not hired Production Request received Outline In production Internal check Delivered Admin Form received Content check Processing Manager approval Done / Filed Our team e.g. Request received e.g. Waiting for assets e.g. Drafting e.g. Requester's check e.g. Delivered e.g. Name the column "Request received" e.g. Work that goes in: requests that arrived with no owner yet Write which row of ⑦ you chose from e.g. Name the prep column "Waiting for assets" (the wait in ④ is long) e.g. Name the work column "Drafting" If you do not need a prep column, write only the work column e.g. Name the column "Requester's check" e.g. Work that goes in: items sent to the requester and awaiting a reply Put the steps with many send-backs in ⑤ here e.g. Name the column "Delivered" e.g. Work that goes in: items with an OK that are filed Write in one phrase what counts as done 3/4 Set exit conditions → 4/4 4/4 Start the new col... Ready for the nex... Send back to Checked by Common jam Entry column e.g. Owner and deadline are set e.g. Never sent back e.g. Leader e.g. No owner is set and it lingers Prep column e.g. All the materials have arrived e.g. Entry column e.g. The owner e.g. The reply about materials never comes Work column e.g. The draft passed the internal check e.g. Prep column e.g. The owner e.g. Holding it alone and stalling Check column e.g. The requester gave an OK e.g. Work column e.g. Leader e.g. No reply for 3 days Finish column e.g. The file is stored e.g. Check column e.g. Leader e.g. Forgetting to file it 縦軸: Can you state... Keep it as is. e.g. The entry column moves on once an owner is set, so leave it. Split it into two, or add a waiting column before it. e.g. If the requester's check piles up, add an internal check column before it. Merge it with a neighbor to cut it. e.g. A prep column you cannot tell apart from the entry column gets merged into it. Rewrite the condition first. If it still piles up, split the column like the top right. What to do Owner When Why we decided this When sending back e.g. Write the reason on the note in a few words and move it to the return column in ⑫ e.g. Whoever checked it e.g. Right when you notice e.g. Reasons were lost and the same fixes kept repeating Morning check e.g. Look for stuck notes, starting from the rightmost column e.g. One person on duty (weekly rotation) e.g. 5 minutes at 9 a.m. every day e.g. A stuck note went unnoticed for 3 days When stuck e.g. Discuss notes that stayed in one column for 3 days at the morning meeting e.g. Leader e.g. Morning of day 3 e.g. We want to spot work held alone sooner ⑮ First Work for ... First work for the new columns Move the In progress notes into the new columns e.g. Owner: leader / Due: Monday morning Nudge the requests waiting for a reply e.g. Owner: each owner / Due: by Tuesday Add the reason to notes that were sent back e.g. Owner: whoever checked / Due: by Wednesday Write each column's condition in its heading e.g. Owner: ____ / Due: __/__ Put this week's requests in the entry column e.g. Owner: person on duty / Due: 9 a.m. daily File the finished notes and tidy up e.g. Owner: ____ / Due: __/__ Review datee.g. Friday two weeks from now, 4 p.m., 30 minutes(facilitator: ____) Numbers to watche.g. Notes that stayed 3 days or more in one column, and the number of send-backs How to decidee.g. Place the columns that pile up again on ⑬, then rewrite the condition or split the column → 2/4 Pick a close sample ↙ 3/4 Set exit conditions → 4/4 Start the new col...
100%

Drag to move, scroll to zoom

Task board contents

Write it out 16 items

Map your flow
Pick a close sample
Set exit conditions
Run the new columns
Note the reason
Sketch the 6 steps
Log jams and gaps
Compare the samples
Name your columns
Fill the 4 frames
Write exit rules
Set return and owner
Decide add or cut
Set working rules
Pick the first work
Set the review date

Pick columns 0 items

Set conditions 0 items

Trial run 0 items

Reviewed 0 items

← Back to templates