Jira Journal

The Calm Work Issue — A journal for teams who inhabit Jira

A pair of hands gesturing over a table during a quiet conversation

Rooms of the House

Room Study

The Team Board

What a team board should and should not hold, and how to make it feel like a clear shared workspace.

A team board is a working surface, not a scrapbook. It should show what is active, who is responsible, and what is blocked, at a glance.

Columns that mean something

Make the board readable

  • Use column names that describe state, not process ceremony.
  • Ensure every card in In Progress belongs to exactly one person.
  • Keep Done empty by the end of each sprint.
  • Remove swimlanes that no one uses to make a decision.
A readable surface earns attention.

Fit on one screen

If the board requires horizontal scrolling, reduce columns or widen the screen layout. Legibility beats completeness.

Reduce sprawl

  • Merge near duplicate states with the same responsibility.
  • Move rare paths to a separate workflow or project.
  • Hide fields that are not needed on the board.

Standup choreography

Read the board left to right. Touch only cards that changed or need attention. End with blockers and explicit asks.