Kanban in OneNote: a workaround that works until the team grows
The notebook already exists. Meeting notes, research, half-finished specs and screenshots are all in OneNote, and the tasks that come out of those notes are in there too, scattered across pages as checkboxes. Building a kanban board in the same place looks like the obvious move. No new tool, no new login, no argument with anyone about adopting software. The question is not whether it can be done. It can. The question is how far it carries a team before the maintenance cost of the workaround exceeds the cost of the thing it was avoiding.
This article covers the three ways people actually build kanban boards in OneNote, what the approach genuinely does well, the specific points where it starts to leak time, and how to tell which side of that line a given team is on.
Three ways a board gets built in OneNote
OneNote has no board view. There is no column object, no card object, and no drag target that changes a task's state. Everything below is built out of features designed for something else.
The table method
The most common approach. Insert a table with three columns, label them To Do, In Progress and Done, and type each task into a cell. Moving a task means selecting the text, cutting it, and pasting it into the next column. Some people add a fourth column for Blocked, or a row per person instead of per task.
This is the closest thing to a visual board that OneNote produces. It fits on one page, it prints, and anyone opening the notebook understands it in two seconds. It also breaks the moment a task needs more than a line of text. A cell can hold a paragraph, an image and a link, but a tall cell stretches its entire row, so one detailed task pushes every other column out of view.
The page per column method
The other common approach abandons the visual grid. Each column becomes a page inside a section: a To Do page, an In Progress page, a Done page. Tasks are bullet lines. Moving a task means cutting a line from one page and pasting it onto another.
This scales better than the table because a task can carry as much detail as it needs, including sub-bullets, embedded files and links to other pages. What it loses is the thing kanban exists for. Nobody can see the whole flow at once. Checking whether In Progress is overloaded requires opening a page and counting.
Tags as a status layer
The third approach keeps tasks where they were written, in the meeting notes and specs, and uses tags to mark state. Microsoft documents tags as a way to categorize and prioritize notes, and the Tags Summary pane collects every tagged line across a notebook into one list that links back to the source page.
For a team whose work is genuinely note-driven, this is the most honest fit. The task stays next to the context that produced it. The weakness is that a tag list is not a board. It is a filtered list, ordered by where the note lives rather than by workflow stage, and it has no notion of who owns a line or when it is due.
What the workaround handles well
It would be wrong to treat any of this as a hack that barely functions. For a specific shape of team, a OneNote board is the correct answer, and the reasons are worth being explicit about.
Context and task sit in the same file. This is the real advantage and it is not a small one. In most dedicated tools, the card says "rewrite the onboarding email" and the reasoning behind it lives in a document somewhere else. In OneNote the decision, the draft, the screenshot of the old version and the task are on the same page. Nothing has to be summarized into a card title.
There is no adoption cost. Nobody has to be convinced, nobody has to create an account, and nobody has to remember to check a second place. If the team already opens OneNote every morning, the board is already where they are.
The board is free-form in a way that structured tools are not. A column can be renamed to something that makes sense only to this team. A task can become a sketch, a table, an audio clip or a pasted email. Tools built around cards impose a schema, and a schema is exactly what some work does not have yet.
It also works offline and syncs later, which matters for teams that travel or work in places with unreliable connections.
Where it starts to cost time
The failure mode is not dramatic. Nothing breaks. The board just quietly becomes wrong, and being wrong is worse than not existing, because people stop trusting it and go back to asking each other in chat.
Moving a task is manual work
Cut and paste is not just slower than dragging a card. It is lossy. Cutting a cell that contains formatted text, a checkbox and a link, then pasting it into another cell, frequently changes the formatting. Over a few weeks, a board maintained this way develops inconsistent fonts, orphaned checkboxes and duplicated tasks where someone pasted without cutting.
Two people editing the same page
OneNote handles simultaneous editing by merging, and it is good at merging when two people type in different places. A kanban board is the worst case: two people editing the same table at the same time, both moving rows. The usual result is a duplicated row or a lost one, and because the change is small, nobody notices for days.
Dates are decoration
A due date typed into a cell is text. It does not sort, it does not trigger anything, and it does not appear on any calendar. The only way to know what is due this week is for a person to read every cell. A board whose dates are not queryable cannot answer the question a manager actually asks, which is what is at risk right now.
There is no history
When a task disappears from the Done column because someone cleaned up the page, there is no record of when it moved or who moved it. OneNote keeps page version history, so the text can be recovered, but reconstructing a workflow timeline from page versions is not something anyone does twice.
Nobody outside the notebook can see it
Sharing a notebook with a client or a contractor means sharing everything in it, including the pages that were never meant to leave the team. The alternative is a separate notebook, which means maintaining the same board in two places.
Side by side
| Board in OneNote | Dedicated kanban tool | |
|---|---|---|
| Moving a task | Cut and paste text | Drag the card |
| Task detail | Unlimited, in the page itself | Card description and attachments |
| Context with the task | On the same page | Usually linked from elsewhere |
| Due dates | Typed text, not queryable | A field that sorts and filters |
| Who is assigned | Typed text or a convention | A field with a person attached |
| Same view as a calendar or timeline | No | Common, though often on paid plans |
| Two people editing at once | Merge conflicts on the same table | Designed for it |
| Change history | Page versions only | Per card activity log |
| Sharing one board outward | Shares the whole notebook | Share one board |
| Cost | Included with OneNote | Free tiers are common, with limits |
The row that decides most cases is the due date row. A team that does not work to dates can live in OneNote for years. A team that does will spend more time keeping the board honest than it saves.
Signals that the workaround has expired
Four signs, in the order they usually appear.
The first is a second board. Someone starts keeping a private list because the shared table is out of date, and now there are two sources of truth. This is almost always the earliest signal and it is easy to miss, because the private list is usually in someone's own notebook.
The second is the status meeting getting longer. If the board were accurate, the meeting would be short. When it stretches, it is because people are reading their status out loud instead of reading it off the board.
The third is a question nobody can answer quickly. What is due Friday. What is Sam working on. How many things are sitting in review. If answering takes more than a few seconds of scrolling, the board has stopped being a board.
The fourth is a person outside the team asking for visibility. A client, a manager in another department, a contractor. At that point the notebook boundary becomes the problem, and no amount of table formatting solves it.
Moving without throwing away the notes
The mistake teams make when they move is treating it as a migration of everything. It is not. Notes should stay in OneNote. Notes are what OneNote is for, and no project tool will hold a pasted whiteboard photo and three pages of research as gracefully.
What moves is the task layer: the title, who owns it, what state it is in, and when it is due. That is a small amount of data, usually under a hundred rows even for a busy team, and it is faster to retype than to script. Each card then links back to the OneNote page that holds the detail, which preserves the one real advantage of the old setup.
Before picking a destination, two things are worth checking against the way the team actually works. The first is whether the same tasks can be seen as something other than a board without a plan upgrade. Trello's pricing page, checked in September 2026, lists Board and List views on the Free plan, with Calendar, Timeline, Table and Dashboard views starting on Premium at $10 per user per month billed annually. That is the sort of detail that decides whether a free tier is actually usable, and comparing a few options on that specific point is more useful than reading feature lists.
The second is the seat count at which the free tier stops. Most tools price per user per month, so a team of five crossing a threshold is a real monthly number, not a rounding error. Reading a few pricing pages side by side takes ten minutes and prevents a migration that has to happen twice.
For teams whose work needs boards, dates and a calendar at the same time rather than one at a time, look for a tool where all the board types are present on the free tier rather than gated behind an upgrade. That is the single condition that most often decides whether a small team can keep working the way it wants to without a budget conversation.
What to change first
Pick one project, not the whole notebook, and rebuild only its task layer somewhere the dates can be queried and two people can edit at once. Leave every note where it is and link the cards back to the pages. If the status meeting for that one project gets shorter within two weeks, move the rest, and if it does not, the OneNote board was doing its job and should be left alone. A free tier that covers a small team is enough to run that test, which is where Pinateca and most of its alternatives start.
Q1. Does OneNote have a built in kanban board view?
No. OneNote has no board view, no columns as objects, and no drag and drop between stages. Every kanban board in OneNote is built from something else, usually a table, a set of pages, or tags applied to lines of text.
Q2. Which method is best for a OneNote kanban board?
A table on a single page is best when tasks are short and the value is seeing everything at once. A page per column is better when tasks carry a lot of detail. Tags work best when tasks are written inside meeting notes and should stay next to the context that produced them.
Q3. Can two people update a OneNote kanban table at the same time?
They can, but a shared table is the case where OneNote merging is most likely to produce a duplicate or dropped row. Small errors of this kind are easy to miss for days. Teams that edit the board together throughout the day tend to hit this problem first.
Q4. Is there a way to get due date reminders from a OneNote board?
Not from the board itself, because a date typed into a cell is plain text. On Windows, tasks can be sent from OneNote to Outlook to get a reminder, but that creates a second copy of the task that has to be kept in sync by hand.
Q5. What should be moved out of OneNote and what should stay?
Move the task layer: the title, the owner, the state and the due date. Keep the notes, research, screenshots and drafts in OneNote and link each card back to its page. That keeps the one thing the OneNote approach does better than anything else, which is holding the task and its context together.
