3 ms·

I'm honestly a little confused here. For starters, the "X considered harmful" clickbait title that doesn't actually talk about X but about a certain use of X to

I'm honestly a little confused here. For starters, the "X considered harmful" clickbait title that doesn't actually talk about X but about a certain use of X to sell you an alternative tool feels weird. I also don't think that "focusing on tasks or issues daily" is different from "not getting the right stuff out the door". That's just a problem of how you use the tool, isn't it? But I honestly don't see the fundamental difference between this tool and, say, my Gitlab issue tracker. Not just from the home page but even going into the guide. You have work items, Gitlab has issues (funnily enough, I was just reading before that Gitlab is migrating under the hood to "work items" to integrate issues/epics/incidents into a single entity), both can break down a single item into multiple ones, have a collaborative document at the top, an activity feed, roadmaps, labels... I don't what's the feature that would make me migrate development workflow to yet another tool (with more costs possibly, because 100 work items doesn't look like much if you deal with multiple projects).

kevsim 4y ago
Thank you for the thoughtful feedback! Easy one first - pricing. It's always a challenge but we try to find something that's reasonable when compared to the competition. We're not big fans of tools that do limited time feature stuff (this feature only works for the first two weeks unless you pay) so this is what we're trying for now. We're very flexible with teams as well. If they don't feel like they've gotten a fair chance to try it out, we raise the limit and let them keep trying for free. We'll gladly take your money once you're satisfied. With regards to GitLab or any other traditional issue tracking tool - if you're able to get this sort of a workflow where your team is really focused on the outcomes and not mechanically processing tickets, then that's great! We're not building the only tool in which this is possible, just building a tool that we feel does a great job of nudging people in the right direction.
SigKill9 4y ago
Thanks for you comment! Gitlabs issue tracker is one I'm not super familiar with. There are definitely other popular and well-known issue trackers which would, by design, make it harder than it should be.

kevsim 4y ago

Thank you for the thoughtful feedback! Easy one first - pricing. It's always a challenge but we try to find something that's reasonable when compared to the competition. We're not big fans of tools that do limited time feature stuff (this feature only works for the first two weeks unless you pay) so this is what we're trying for now. We're very flexible with teams as well. If they don't feel like they've gotten a fair chance to try it out, we raise the limit and let them keep trying for free. We'll gladly take your money once you're satisfied. With regards to GitLab or any other traditional issue tracking tool - if you're able to get this sort of a workflow where your team is really focused on the outcomes and not mechanically processing tickets, then that's great! We're not building the only tool in which this is possible, just building a tool that we feel does a great job of nudging people in the right direction.

SigKill9 4y ago

Thanks for you comment! Gitlabs issue tracker is one I'm not super familiar with. There are definitely other popular and well-known issue trackers which would, by design, make it harder than it should be.