Tracker design decisions
I can’t help but to enjoy reading 37Signals’ design decisions. For those who don’t know, they’re just posts that provide a small insight into 37Signals’ design process and why they chose to do a particular something, a particular way. I’m sure most people who do the type of work that I do would agree that it’s interesting to peak inside of someone else’s design reasoning.
Garrett Dimon is an Information Architect who is working on a bug tracking system that he has appropriately named, Tracker. I’ve been keeping up with posts on the issue tracker, and I’m really impressed with some of the concepts and ideas. To save some hunting, here are the posts thus far:
- (8/14/2007) Bug & Issue Tracking
- (8/20/2007) The Tracker Status Bar
- (8/20/2007) Tracker Status & Comments
- (8/21/2007) Linking Issues in Tracker
- (8/22/2007) The Tracker Dashboard
Looking into other designs often help me to think outside of the box a little more, which I believe is important to keep that fresh, creative edge (assuming that I already had it, of course).