What Ten Years of Issue Tracking Taught Us About Team Trust

We spent a decade building workflows for machines and forgot about people. Here is what changed when we finally flipped the priority.

In the spring of 2016, I joined a forty-person engineering team that had just migrated from spreadsheets to a proper issue tracker. The tool was powerful. The adoption was miserable. People filed tickets in vague shorthand, avoided updating statuses, and treated the backlog like a graveyard nobody wanted to visit.

The sprint that broke everything

By October we were running two-week sprints with seventy tickets each. Stand-ups lasted forty minutes. Engineers spent more time grooming the board than writing code. I remember one Tuesday when our lead backend developer, normally the calmest person in the room, pushed back his chair and said: In Progress "I have spent three hours today moving tickets between columns. I have not written a single line."

The tool was doing exactly what we asked of it. The problem was that we never stopped to ask whether our questions made sense for the humans answering them.

— Internal retrospective, October 2016

We had optimized for visibility at the cost of trust. Every status change felt like surveillance. Engineers stopped writing honest update notes because they knew a manager would read them within minutes and ask why a ticket moved from "In Progress" back to "To Do." The workflow punished vulnerability.

Rebuilding with trust as the default

The turning point came when we stripped the workflow down to four states and made every transition optional. If an engineer wanted to mark something done, they could. If they needed to keep a ticket quiet for a few days while they explored an alternative approach, that was fine too. We replaced burndown charts with weekly team-authored summaries, two paragraphs each, no metrics.

Shipping slower, shipping better

Within a quarter, cycle time dropped by thirty percent. Not because people worked faster, but because they stopped double-handling tasks to make the board look pretty. Our quarterly incident count fell from eleven to three. The team started pairing more, not because we mandated it, but because the psychological safety was finally there.