Product & Culture08-01-20266 min read

What We Learned from Turning Bug Hunting into a Game at Blits.ai

In the first week of January we turned quality assurance into a Bug Hunt Game. This is what happened when we put Hunters, Fixers and a Judge on a shared leaderboard powered by Azure DevOps.

Len Debets
Len Debets
CTO & Co-Founder
What We Learned from Turning Bug Hunting into a Game at Blits.ai

In the first week of January we did something a bit unusual at Blits.ai and turned bug hunting into a game. Quality is normally one of those background things everybody agrees is important, so we made it explicit, visible and a little bit competitive. Our nontechnical colleagues became Hunters, the engineers became Fixers, and I got to play the Judge. Behind the scenes a Nuxt.js app pulled live data from Azure DevOps and kept score on a real time leaderboard.

How the Bug Hunt Game worked

There were three roles. Hunters (nontechnical) had to find bugs and document them well enough that someone else could reproduce and fix them. Fixers (technical) had to take a bug from "this is broken" to "this is fixed and tested". And the Judge, me, enforced the rules, checked quality and now and then stole points when somebody didn't follow the process.

Everything lived in Azure DevOps. Any bug with the Bug Hunt Game 2026 flag was part of the game, and the Nuxt leaderboard app pulled those bugs through the Azure DevOps API and calculated the points in real time:

  • +1 point for each valid bug report (Hunter).
  • +1 point if the original Hunter verified the fix themselves.
  • +1 point for adding a help center article or instructions.
  • +1 point for fixing a bug (Fixer).
  • +2 points for adding unit tests, e2e tests or recurring validation to prevent regressions.

Every game needs a bit of chaos, so the Judge could also invalidate, bonus or steal points whenever the process wasn't followed.

The actual numbers from week one

At the end of the first week of January we had 49 bugs identified and tracked with the game flag, and 32 of them resolved and verified as fixed. Another 8 bugs were still in validation, so fixed but waiting for final confirmation. 7 active players earned 85 points in total, and we added 15 new unit tests to the codebase.

Behind those numbers were bugs that would otherwise have stayed in someone's notes or chat history, nontechnical colleagues (people who never open a pull request) sitting inside the quality process, and "please add tests" turning into something you got rewarded for. Normally quality is a vague intention for "this quarter". For one week it was the only thing on the scoreboard, and you could watch it move.

The top three on the leaderboard:

  • 🥇 Player 1, 23 points (9 bugs reported, 11 fixed, 2 unit tests).
  • 🥈 Player 2, 22 points (15 bugs reported, clear top Hunter).
  • 🥉 Player 3, 14 points (3 bugs reported, 8 fixed, 2 unit tests).

People who both reported and fixed bugs climbed fastest, which makes sense, because the game naturally rewards doing both. Pure Hunters still mattered a lot though. Yuri didn't fix a single bug, but his reports kicked off a lot of downstream work. Unit tests made a bigger difference than the points suggest. They're "only" +2 points, yet in a tight ranking they were often what decided it.

I was on the leaderboard too, as the Judge, but permanently anchored to the bottom and excluded from winning. My job was to keep it fair.

Better bug reports, more tests

The points were fun, but what I cared about was the behavior they created.

The first change was in the bug reports from nontechnical teammates. Hunters found out pretty quickly that a vague "it doesn't work" ticket scored nothing. To get a point they needed a clear description, steps to reproduce, environment or device information, and evidence like screenshots or a video. After a few rounds of feedback the average report got dramatically better, and Fixers spent less time guessing and more time fixing.

Testing changed as well. Developers already know they should add tests, and the game just made that visible: add a test and you get rewarded, skip it and you can still fix the bug, but you leave points on the table. By the end of the week we had 15 new tests, each tied to a real bug that had caused a real problem. I'll take that over an abstract coverage target any day.

The third change was about language. Because everybody looked at the same leaderboard, business and engineering started talking about the same objects. You'd hear "this bug is in validation", or "you'll get the verification point once you confirm it's fixed", or "I've added a test, can you double check the behavior and close it?" The usual devs versus business thing faded into the background, and what was left was Hunters, Fixers and a Judge working through one backlog.

Why we built a custom app instead of a spreadsheet

We could have done all of this in a spreadsheet, and it would have felt like filling in timesheets. So we built a Nuxt.js leaderboard app styled like a real game dashboard, with server side endpoints that pull bugs and player stats straight from Azure DevOps. There's logic for the edge cases: judges stealing points, verification rules, states like "Tested, Ready for Prod", and date windows for which bugs count. There's also a bug list view that shows who reported what, who's working on it, and which tags (tests, articles) are attached.

The result was a live scoreboard that people could refresh all week to see themselves move up or down. Small thing, but it makes work that normally feels abstract look like progress, and people like seeing progress.

Next round, and a slightly evil Judge

A few things go on the list for the second edition. Fixers could still earn points for older bugs they happened to fix during the week, which wasn't really the idea, so we'll probably limit reporting and fixing to a stricter time window (proper seasons, basically). The prizes were very basic this time, and I'd like categories like "Best Bug Report", "Most Valuable Test" or "Most Impactful Fix". The game is also purely internal right now. Anonymized stats could go on internal dashboards or into company wide updates.

For an experiment it went pretty well. Nontechnical people got into the quality loop with an actual structure around it, testing and documentation got rewarded instead of only closing tickets, and we got hard numbers to talk about (bugs found, bugs fixed, tests added, players involved). People lean into quality by themselves once you make it visible and a bit fun.

At Blits.ai we spend most of our days helping enterprises build production grade AI and conversational systems, so it was funny to be reminded that some of the biggest quality wins need no new tooling whatsoever. People just had to look at the work a bit differently. If you can get them there with a leaderboard, medals and a slightly evil Judge, even better.

Updated on 12 October 2026.

Len Debets
Len Debets
CTO & Co-Founder
Writes about Enterprise Architecture, LLM, IT Security, RAG Systems
Len Debets on LinkedIn
Published on 08-01-2026

Related Articles

Most Enterprise AI Never Leaves the Pilot. Ours Goes Live.
AI Technology13-11-2026

Most Enterprise AI Never Leaves the Pilot. Ours Goes Live.

The line on our home page is a big claim, so here is what sits behind it. What the research says about enterprise AI pilots, the ten ways we see pilots die, and what we do differently so that a use case reaches production and stays there.

Read More →
AI Agency or AI Platform? How Enterprises Should Choose
AI Technology10-11-2026

AI Agency or AI Platform? How Enterprises Should Choose

Hire an AI agency, buy a SaaS tool, build it yourself, or work with a platform? Every enterprise faces that choice, and the data is starting to show which path reaches production. Why custom built AI so often gets abandoned, and the questions that tell you whether you're buying a project or a capability.

Read More →
AI Voice Agents for Enterprises: Latency, Dialects and Compliance
AI Technology06-11-2026

AI Voice Agents for Enterprises: Latency, Dialects and Compliance

An AI voice agent can answer every call at once, in many languages, at any hour. Whether customers accept it comes down to three things that rarely show up in a demo: how fast it answers, whether it understands the way they actually speak, and whether it follows the rules for disclosure, consent and authentication.

Read More →

Stay Updated

New posts on conversational AI, enterprise automation and customer experience, sent to your inbox when they go live

No spam, unsubscribe at any time