Why We Stopped Tracking Bugs in Excel

One thing I’ve noticed over the years is that software projects often become harder to manage because the systems around them become unnecessarily complicated.

At the time, we were tracking bugs in spreadsheets, and it quickly became messy with multiple versions, email chains, and poor visibility across the team.

The Problem with Spreadsheet Tracking

I hate managing software faults with a spreadsheet. It normally ends in a mess, with multiple versions, poorly formatted, emailed here there, and everywhere.

The real issue wasn’t the spreadsheet itself—it was the lack of visibility, ownership, and workflow around the process.

To avoid this and not having access to a real software bug-tracking tool like fogbugz I quickly set up something in Trello.

Why Trello Worked Better

Trello is brilliant and I have many boards for various jobs on the go at one time. It is a simple free-to-use tool for managing simple tasks and workflows.

 

I set up 6 lists flowing from left to right. New bugs can be added by the team or by the customer. They can be entered directly as a new card or via email by links provided. The email to the board facility is brilliant and it will create a new card automatically.

Visual Workflows and Team Collaboration

The bug tracker board can be accessed by anyone who has access to the team. When connected to the team they can then take control of individual bugs and they can be assigned a bug. So at a glance, you can see John is working on bug #27, and Tom is testing #32. When John has completed the fix for bug #27 he can move the bug to the ready for test list and assign the bug to Tom. When Tom tests the bug and it passes the test Tom can move it to Done. If it is not fixed he can move it back to in progress and assign it back to John and add a comment as to why it did not pass the test.

What made the system effective wasn’t complexity—it was visibility. Everyone could immediately see what was happening, who owned what, and where bottlenecks were appearing.

Colors can be added to each bug indicating the criticality of the fault. So at a glance, you quickly see the red for critical and can concentrate on these first.

Bugs can include attachments, so you can take a screenshot of a fault and quickly add it to the bug to help with the resolution. You can add multiple items to a bug, so if there are a number of similar faults these can be grouped into one bug and make use of the checklist facility. Tick them off as they are resolved.

What Stayed With Me

So there you go. Trello as a bug tracker. It's not perfect, but I set up ours in under 10 minutes, you can have your whole team collaborating together working through problems or changes. It's much better than yet another Excel spreadsheet and you can see at a glance visually the status of the bugs.

Looking back, this probably reinforced something I still believe now: simple systems that people actually use are often more effective than complicated processes designed for perfection.

A surprising amount of software delivery problems are really workflow and communication problems underneath.

This also connects closely to my thoughts on overcomplication in systems and how unnecessary complexity often creates more problems than it solves.

It links naturally to my reflections on understanding systems properly rather than simply adding more layers around them.

A lot of the same thinking also appears in my posts about organisation and workflow simplification.

Good systems are often simpler and more visible than people expect.

I spend a lot of time helping simplify workflows, untangle technical problems, and make systems easier to manage and maintain.

You can take a look at my TechFix service if that sounds useful.