Thanks for your comment! Don't disagree, but issue trackers are mainly designed to make you track (individual) tasks. If you make your issue represent outcomes, we have found that teams often feel like they are trying to force a square peg into a round hole. Your mileage might vary, though :)
Thanks for good feedback! Noted! It's always hard to convey how you are different in a few words on a webpage. Teams that do try Kitemaker find us quite different, but getting the message across on a page that people (mostly) skim is not super easy.
Happy to have a chat when you start diving into real time collaboration, I worked on this with kevsim and we have some learnings we haven't blogged about yet :)
Thanks for mentioning us (I'm one of the founders of Kitemaker). Totally agree that keyboard shortcuts, a clean design, and simple navigation should be at the core of every productivity tool, which is why we did that as well.
FWIW, we built Kitemaker to tackle some of the points that the original articles highlights, but of course, our solution is a bit different from the authors. Our basic idea was that each work item should be a collaborative workspaces and allow you to track work at the level of deliverables (which basically is what many would say is the correct level, but AFAIK no issue tracker actually supports).
Also, always curious why you switched to Linear :)
Segment is a tracker that allows you to pipe the data to any tool that supports segment. That way you can change or add tools without touching the tracking code in your app or service.