Kanban for Planning: Roadmaps, Content Calendars, and How Many Boards You Need

Planning boards have a different job than execution boards. A sprint board answers "what am I doing today?" A roadmap answers "what are we doing this quarter, and what did we deliberately decide not to do?"

That second question is the one most planning tools handle badly. They produce a document that is accurate for about a week, then quietly becomes fiction that nobody wants to be the one to update.

This guide covers two planning boards — a product roadmap and an editorial calendar — plus the thing that determines whether either survives: a board map that tells you where work lives. You can build any of them on a kanban board without registration and keep it if it earns its place.

The Now / Next / Later roadmap

Dated roadmaps break. You commit to "Q3: mobile app," reality intervenes, and now the roadmap is either wrong or a source of arguments about whether you are behind.

Confidence-based lanes hold up better because they encode what you actually know:

Now → Next → Later

Now — actively building or about to ship. High confidence.
Next — highest-confidence items coming up. Committed in direction, not in date.
Later — real ideas, genuinely not committed.

A worked example for a small SaaS:

NOW NEXT LATER ────────────────────────────── ─────────────────────────── ───────────────────────── Fix onboarding drop-off, Improve drag & drop on Landing page copy test step 2 mobile layouts

Add password-protected Add CSV export for Explore voice capture share links client reporting for field notes

The goal is not completeness. It is that you can glance at it and explain your plan in 30 seconds. If you cannot, the board has too much on it.

Write cards a stakeholder understands

A roadmap card should answer "why does this matter?" without a meeting. The difference is small and it decides whether anyone outside the team can read the board:

Weak: "Refactor auth" Better: "Cut login failures on Safari (top support complaint)"

Weak: "Add webhooks" Better: "Let customers pipe board events into their own tools"

Write the outcome, not the implementation. The implementation belongs on the sprint board.

Keep Next honest

Next is where roadmaps go to rot. It fills up, nothing leaves, and within two months it is a wishlist with a misleading name.

Two rules that hold:

Cap Next at five cards. Adding a sixth means removing one. This forces the prioritization conversation to happen at the moment of the decision, rather than never.
Nothing enters Now until something leaves. If Now has four cards and everything is half-built, you do not have a roadmap problem, you have a WIP problem.

Review monthly, not weekly. A roadmap that changes weekly was never a roadmap.

The editorial calendar

Content workflows do not need ten stages. They need the few that reflect real progress and answer "where is this at?" without a message.

Ideas → Draft → Review → Publish

Review is optional. If you are solo and do not sit on your own drafts, three columns is better than four.

A solo creator planning a launch:

IDEAS                    DRAFT                REVIEW              PUBLISH
──────────────────────   ──────────────────   ─────────────────   ─────────────────────
Launch post outline      Launch post v1       Pricing page copy   Teaser tweet #1 (sched)
Pricing page refresh     Email #1 draft       Email #1 subjects   Launch post (live)
3 teaser tweets
Email #1: story
Email #2: offer

The board tells you things a calendar cannot. If Draft is overflowing, you are starting more than you finish. If Review is stacked, you either need faster feedback or smaller pieces.

Column rules that keep it clean

Ideas — one sentence per card, no essays. Add a short "why this matters" line so future-you knows what past-you meant. Draft — only what you will work on this week. If it is not happening this week, move it back to Ideas. This is the rule that does the work. Review — only things that need another set of eyes, or that you want to revisit cold. Publish — live, shipped, or sent. Clear it monthly so you can see the month's output in one place.

Why not a calendar?

Calendars are good at dates and bad at states. A post scheduled for the 14th tells you nothing about whether it is written.

Practical compromise: put the publish date in the card title (Aug 14 · Launch post) and let the board handle state. You get the deadline and the actual status in one view, without maintaining both a calendar and a task list that disagree.

The board map

This is the part that decides whether any of the above survives contact with a busy month.

The failure mode is not too many boards, it is boards with no defined purpose. You create "Stuff," then "Q3 Planning," then "Ideas 2," and three weeks later you are guessing where something lives.

A board map is a decision about what categories of board you allow:

One Home board — your command center. Next actions across projects. Stays small deliberately: it is where you choose what matters now, not where you dump everything.
One board per active project — Client A Website, Side Product Launch, and so on.
Optional: one Admin board — invoices, taxes, appointments.
Optional: one Someday board — ideas you do not want to lose but must not be distracted by.

When a new board has an obvious slot, creating it feels safe. When it does not, you have found a category you have not decided on yet.

How many boards do you actually need?

Fewer than you think. Most people who feel they need fifteen boards need three boards and a habit of archiving.

The free plan gives you three boards with unlimited cards, and that constraint is a useful forcing function: one Home board plus two active projects covers most solo work honestly. When you genuinely run several clients or products in parallel, that is the point where the limit becomes real, and Pro (€6/month or €60/year) removes it along with the team member cap.

Name boards so you can scan them

Use a consistent prefix so the list sorts into something readable:

Home
P · Client A Website
P · Side Product Launch
Admin
Someday

Small thing. It matters once you pass about five boards.

Key takeaways

Confidence lanes beat dates. Now / Next / Later survives reality; "Q3: mobile app" does not.
Cap Next at five. The cap forces prioritization to happen at the right moment.
Write outcomes on roadmap cards, implementation on sprint cards.
Draft means this week. Everything else goes back to Ideas.
Put the publish date in the card title so one board handles both deadline and state.
Decide board categories, not board counts. A board with no slot is future confusion.

Frequently asked questions

Can I build a roadmap without signing up? Yes. Start a kanban board with no signup and set up Now / Next / Later in about two minutes. Sign in with GitHub or Google only when you want to share it or keep it across devices. How many boards does the free plan include? Three, each with unlimited cards. A Home board plus two projects. Pro (€6/month or €60/year) removes the board limit. Can stakeholders see the roadmap without an account? Yes. Share a password-protected link with read-only access — useful for a roadmap you want visible but not editable. Free boards support up to 3 members with edit rights. Should the roadmap and the sprint board be the same board? No. They answer different questions on different time horizons. Mixing them means the roadmap fills with implementation detail and stops being readable by anyone outside the team. How often should I review a roadmap? Monthly. If it needs weekly changes, the items in Now are too large or Next was never really prioritized.

Kanban for Planning: Roadmaps, Content Calendars, and How Many Boards You Need