Why Issue Trackers Can’t Help You Develop Products

The road to shipping anything that isn’t a bug fix is filled with distractions, diversions, and speed bumps.

“That’s why there’s Agile!”

So what’s the problem with using issue trackers for product development?

  1. Steps to reproduce,
  2. What you expected to see, and
  3. What you saw instead.

It’s one thing to track and fix issues, but it’s a whole different ball game when you want to build products.

An illustration by Intercom on communication and its complexity.
  1. Who is doing what and when,
  2. What are the different disciplines involved in building the feature,
  3. Where the work stands in each of these disciplines, and
  4. How all of this connects to the overall progress of the entire feature, across disciplines, in real-time.
The pyramid of development tracking needs

The greatest trick issue trackers ever pulled was convincing the world you could do all of this and streamline your entire product development process.

So, how do you capture and track this non-linear nature of product development?

1. Spec, plan, and capture in seconds

Zepel’s document-like interface to help you quickly plan a feature.

2. Track progress in each discipline

Track progress in each discipline involved in building the feature using multiple Boards.

3. Align everyone on the big picture

Keep everyone aligned on the same goals and watch your feature come to life.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store