Kanban boards with Google tools: Sheets, Tasks, and what is missing

A team runs on Google Workspace. Documents, spreadsheets, mail and calendars are all there, everyone has an account, and the admin has already been through the security review. Putting the project board in the same place seems obvious. So someone searches for a Google kanban board and discovers something slightly awkward: Google does not ship one.

That is not the end of the story. There are three or four ways to get board style work tracking out of Google tools, and for some teams one of them is genuinely the right answer for a long time. There are also specific things none of them do, and those are worth knowing before a quarter of work goes into a spreadsheet. This article covers what each Google tool actually offers, how to build the best version of a board in Sheets, and the point where the approach stops paying off.

What Google actually ships

Four products come up in this search, and they do quite different things.

Google Tasks is a personal to do list. The help page describes capturing tasks from any device, adding details and subtasks, creating tasks from Gmail and Calendar, and staying on track with due dates and notifications. There is no board layout and no column grouping. It is a list, and it is a good one.

Google Keep is for notes. Labels and colours give a rough grouping, and the grid of notes looks a little like a board at a distance, but there are no stages and no way to move an item from one state to the next except by editing a label.

Google Sheets is the only one of the four flexible enough to become a board, because a spreadsheet can be shaped into anything. It is also the one that requires the most deliberate setup.

Google Calendar holds dates, not states. It answers when, never what stage.

Nothing here is a kanban board out of the box. Getting one means building it in Sheets, adopting the Google tools for what they are good at, or adding something else alongside them.

Building a workable board in Google Sheets

There are two layouts, and the choice between them decides everything that follows.

Layout one: a table with a status column

One row per item. Columns for the title, the owner, the due date, the status and any notes. The status column uses a dropdown with a fixed set of values, set through data validation, so nobody types Done, done and DONE in the same sheet.

This layout is not visually a board, but it behaves like one where it counts. Conditional formatting colours each row by status, so the state of the work is legible at a glance. Filter views, which are per person and do not disturb anyone else's screen, let each member look at only their own rows or only the current stage. A second tab with a pivot table gives a count per status, which is the fastest honest answer to how much is in flight.

This is the layout to choose if the team will ever want to sort, count, filter or report. It survives four hundred rows. It also survives someone opening it on a phone, which the other layout does not.

Layout two: one column per stage

Columns named To do, Doing, Review and Done, with card text typed into the cells beneath. This looks like a board and reads like one in a meeting.

The problem is that the text is just text. Moving an item means cutting a cell and pasting it into another column, which leaves a gap behind. Nothing is attached to the item: no owner field, no date, no history. Counting what is in each column means counting non empty cells. It photographs well and it degrades quickly, so it suits a short project with a fixed end date rather than a running board.

The setup that makes layout one hold up

Add a created date column and fill it automatically. Knowing how long something has sat in a stage is the single most useful piece of data a board produces, and a spreadsheet will not tell you unless the date is captured.

Protect the header row and the validation ranges through the protected ranges setting. On a sheet that five people edit, an accidental paste over the header is a common way to lose an afternoon.

Keep finished rows on a separate tab rather than deleting them. A completed item is often the quickest answer to how something was done last time.

Decide who is allowed to add a new status value. This sounds trivial. It is the thing that quietly breaks every shared spreadsheet, because the pivot table and the conditional formatting both stop matching the moment a sixth value appears.

Add-ons and scripts, and what they are worth

Two routes exist for pushing a Sheets board further. The Google Workspace Marketplace lists add-ons that draw a board interface on top of a sheet, and Apps Script can automate the sheet itself, for example stamping a date when the status cell changes or sending a mail when a row is assigned.

Both work. Both also create an owner. An add-on is another vendor with access to the data, which means another security review and another renewal to remember. A script is code that one person wrote, and when that person is away and the script stops firing, nobody else knows where to look. That is an acceptable trade when the script replaces an hour of manual work every week. It is a poor trade when the script exists to make a spreadsheet behave like a product that already exists.

The practical test is whether the automation would be missed if it vanished on a Friday. If not, it is decoration.

Timeline view: the closest Sheets gets to a Gantt chart

Sheets has a built in timeline view, which is worth knowing about because many teams reach for a board when what they actually need is dates on a bar chart. The help page on creating a timeline view states that it needs a column for the card title, a column of start dates and a column of end dates, all in a date format, and that the start date must be earlier than the end date or the card shows no length.

If the board is built as a table with a status column, the timeline needs only two extra date columns to work from the same rows. That is a genuinely good property of this approach: one set of data, two ways of looking at it, no duplication. The limitation is that the timeline is a view of the sheet, not a place to work. Dragging a bar does not move a card through stages, because Sheets has no concept of a stage.

Google Tasks and what shared means there

Teams often assume Tasks can be shared like a calendar. It cannot, in the sense most people mean.

Google's page on shared tasks sets out where sharing does exist: a task can be created in a space in Google Chat, or in Google Docs for eligible Google Workspace plans. An assigned shared task then appears in the assignee's own task list, in the space or document where it was created, and in Google Calendar if it has a date and time. The same page notes that a shared task cannot have a subtask and cannot repeat.

That is useful for action items coming out of a document or a chat thread, and it is genuinely well integrated. It is not a board. There are no columns, no view of everyone's work in one place, and no way to see what stage an item is at beyond done or not done.

What a Google setup does not give you

Capability	Sheets board	Google Tasks	Purpose built board tool
Drag a card between stages	No, cut and paste	No stages	Yes
Work in progress limits	Manual count	No	Usually built in
Notify the new owner on a move	No	Assignment only	Usually built in
Comment thread per item	Cell comments	No	Yes
Attachments on an item	Link to Drive	No	Yes
History of what changed	Version history of the file	No	Per item history
Same items as a calendar or Gantt	Timeline view	Calendar for dated tasks	Usually built in
Guest or client access to one board	Share the file	No	Per board permissions

Read the middle column honestly. Several of the No entries have workarounds. Cell comments do carry a conversation, and Drive links do attach files. The cost is that each workaround is a convention the team has to remember, and conventions decay when someone is busy.

The one that catches teams by surprise is history. Sheets keeps version history for the whole file, so it is possible to discover that a cell changed. Finding when a specific item moved from Review back to Doing, and who did it, means scrolling a file history rather than reading an item's own record. On a board used to answer questions about what happened, that difference shows up in the first difficult week.

When the Google setup is enough

It is enough when the work is mostly a list with states, the team is small enough that everyone sees the same sheet every day, and the important information is in the row rather than in a conversation. Editorial calendars, recruiting pipelines, inventory of small jobs and campaign trackers all run well this way for years.

It stops being enough at fairly predictable moments. When more than one project needs its own board and people want a single view of their own work across all of them. When clients or contractors need access to one board and nothing else. When the question of how long things take starts being asked seriously, because a spreadsheet will not answer it without a lot of manual date capture. And when the cut and paste of moving items starts producing rows in the wrong place.

At that point the useful comparison is not Google against a board tool in the abstract, but what the team would keep in Google either way. Documents, spreadsheets and mail stay where they are. The board moves. Most board tools connect back to Google Drive and Calendar, so the spreadsheet does not have to disappear, and the integrations page is the right place to check what a given tool connects to. For teams weighing up the shape of that move, the comparison pages set out how the common options differ.

What to change first

If the board is currently columns of typed text, rebuild it as one row per item with a validated status column, and add a created date. That single change makes counting, filtering and timelines possible and costs an hour. If the sheet already looks like that and the pain is multiple boards, client access, or the absence of per item history, Pinateca covers those and stays free for up to five people and ten boards.

Q1. Does Google have a kanban board of its own?

No. Google Tasks is a personal list, Keep is for notes, and Calendar handles dates. Sheets is the only Google tool flexible enough to be shaped into a board, and it has to be built by hand.

Q2. Can a Google Tasks list be shared with a team?

Not as a list. Shared tasks can be created in a Google Chat space, or in Google Docs on eligible Workspace plans, and an assigned task then shows up in the assignee's own list. There is no shared list that a whole team works from together.

Q3. Is a spreadsheet board better as rows or as columns per stage?

Rows, in nearly every case. A table with a validated status column can be sorted, filtered, counted and fed into a timeline view. Columns of typed text look more like a board but carry no owner, no date and no history.

Q4. Can a Sheets board show a Gantt chart of the same items?

Yes, through the built in timeline view, provided the sheet has a card title column and start and end dates in a date format. The timeline is a way of looking at the rows, not a place to move work between stages.

Q5. What usually breaks a shared spreadsheet board first?

Uncontrolled edits. A new status value that nobody agreed on, a paste over the header row, or a sort applied while someone else is typing. Protecting the header and the validation ranges, and agreeing who may add a status value, prevents most of it.