First thing I do when I join a new project is open the JIRA board.
Not to check the tickets. To check if the team actually trusts it.
You can tell within five minutes. If engineers are updating tickets without being asked, the board is working. If the PM is the only one touching it — the board is just decoration.
I inherited one of the broken kind a couple of years back.
750+ tickets. Statuses that hadn't been touched in weeks. A "Done" column full of things that weren't actually done. Custom fields nobody remembered creating. Workflows so complicated that moving a ticket felt like filling out a tax return.
The team had stopped using it — not because they were lazy, but because it had stopped reflecting reality a long time ago and nobody had fixed it.
So I didn't start with the backlog. I started with a conversation.
Asked each engineer one question: "What would make this board actually useful to you?" Not useful to the stakeholder. Not useful to me. Useful to them — the people who were supposed to be updating it every day.
The answers were pretty consistent. Too many statuses. Too many required fields on things that don't need them. No clear definition of what "In Progress" actually meant on this team.
So we simplified everything. Rebuilt the workflow around how the team actually worked, not how someone thought they should work six months ago. Killed the custom fields nobody used. Wrote a one-page "what each status means on this board" doc that lived in Confluence and got linked in the onboarding checklist.
Took about a week of cleanup and two sprints of reinforcement.
The moment I knew it had actually worked wasn't a metric. It was a Tuesday standup where an engineer updated three tickets before the call started — without being asked, without a reminder, without it being in anyone's job description to chase them.
That's when a JIRA board goes from a PM's tool to a team's tool. And that shift is honestly most of the battle.
Delivery visibility isn't about finding the perfect tool. It's about building something your team actually wants to use.
What's the state of your team's JIRA board right now — trusted or tolerated?
#JIRA #DeliveryVisibility #TechnicalProjectManager #SaaS