Why Your Jira Board Is Lying to You

Every PM I know has a complicated relationship with Jira. We all use it. We all complain about it. And most of us are using it wrong.

I spent the last quarter rebuilding how my teams use Jira, and the biggest realization was this: the default setup actively hides problems.

The lies boards tell

"Everything is in progress." When your In Progress column has 15 tickets and your Done column has 3, that's not a busy team — that's a blocked team. But the board looks fine because stuff is "moving."

Story points completed per sprint. This metric is almost useless for cross-team comparison and barely useful within a team. Points inflate over time as teams learn to game the system. I've watched teams double their velocity in two sprints without shipping anything faster.

Status updates without context. A ticket marked "In Review" for 8 days tells you nothing. A ticket with a comment saying "blocked on API team, escalated Tuesday" tells you everything.

What I changed

WIP limits, enforced. No engineer carries more than 2 tickets in progress. This was controversial but immediately exposed our bottleneck: code review turnaround was killing us.

Added explicit blocked and waiting columns. Making blockers visible in the board layout — not buried in comments — changed how fast they got resolved.

Custom dashboards for leadership. Executives don't need to see tickets. They need to see cycle time trends, blocker aging, and deployment frequency. I built Jira dashboards that translate engineering work into business language.

Killed vanity metrics. We stopped reporting velocity to stakeholders and started reporting cycle time and throughput. These actually correlate with delivery predictability.

Jira is a tool. It reflects whatever discipline you bring to it. Bring none, and it'll happily show you a green dashboard while your project burns.