How I work

Jira

Making Jira reflect reality instead of becoming a second job.

The board should match the work

A Jira board only helps if it mirrors how the team actually works. I design workflows that fit the team, not a template someone imported in 2018, so updating a ticket takes seconds and the board is trusted at a glance.

Hygiene beats features

Jira's power is wasted without discipline: clear statuses, one owner per ticket, and no zombie issues lingering for months. I run light backlog hygiene so the tool stays a source of truth instead of a graveyard.

Dashboards for decisions, not decoration

I build dashboards and JQL filters that answer real questions, such as what is blocked, what is slipping, and where the bottleneck is, rather than vanity burndowns nobody reads. If a report does not change a decision, I delete it.

Automate the busywork

Transitions, notifications and cross team links are where teams waste time. I use Jira automation to remove the manual steps, so engineers spend effort on the work, not on feeding the tool.

Real example

Across delivery teams I have configured Jira to match real PDLC stages, with dashboards leadership could read without a translator. The result was standups about the work, not about fixing the board.