All posts

Guide

Start with three columns

It is tempting to build an elaborate board on day one. Here is why we suggest starting with three columns and adding the rest later.

The most common mistake when setting up a new board is creating columns for problems you have not had yet. “In review”, “waiting for test”, “with the customer”, “ready to ship”: before the first week is over you have an eight-column board, and half the cards are in the wrong place.

Our advice is simple. Start with three columns, and add a fourth only when it hurts not to have it.

Why three columns are enough

To do, in progress, done. These three columns answer one question: who is working on what right now? In the first weeks that is the only thing you need to know.

Every new column asks the team to make a decision. Where does a card go next, who moves it, and how long may it sit there? A column opened before you can answer those questions turns into a quiet corner where work piles up.

When to add a fourth column

When you hit the same problem a second time. A few signs:

  • Cards sit in “in progress” for days because they are really waiting for someone else to review them.
  • In meetings people keep asking “is this done, or is just the code done?”
  • An issue reaches “done” and then comes back.

In that case the column you add makes a real waiting point visible. That is the difference from a column opened on a guess.

A limit before a column

Often a limit does the job better than a new column. Putting a WIP limit on “in progress”, a cap on how many issues can be underway at once, steers the team towards finishing instead of starting.

Starting something new is easy. The value comes from the work you finish.

A good rule to begin with: set the limit to one more than the number of people on the team. When the limit is reached, people help with the stuck issue instead of pulling a new card.

What to switch on as you grow

Once the board has settled, needs usually arrive in this order:

  1. A review column. The step where someone else looks over the work.
  2. Approval. Tying a particular change, such as going live, to sign-off from someone with authority.
  3. Automation. Repeated steps, such as moving the status forward when a PR is merged.
  4. Sprints. When you want to plan work at a fixed rhythm. Scrum or Kanban is chosen per project and can be changed later.

The order may differ on your team. What matters is that each addition answers a problem you have actually had.

In short

A board is not a process document; it is a photograph of the work as it stands. The simpler the photograph, the faster it reads. Start with three columns, set the limit, and let what your team runs into decide the rest.

All of the work. None of the clutter.

Try Orciss with your own work. Nothing to install; it opens in your browser.