SigKill9

Product management tools typically handle this. Jira Product Discovery and tools like Kitemaker keeps that information close to where the rest of the team works :)

I spent less than 5 seconds in the prompt. Dall-e is quite politically correct, I guess :)

Thanks for the comment. And I completely agree. Incentives shapes so much of how people work. I tried to capture that in the 3rd bullet, but your comment is more on-point :)

We honestly started this company because there is a big gap between best practice product development and the tools that were available. I hope that if you read the article that you'd at least find some interesting (maybe provocative) content there. It's not intended as clickbait.

Thanks for your feedback! What about task trackers do you think we fail to articulate very well?

We try to explain how the design of issue trackers fail to address the needs of how best practices of product development are described by certain authors (Marty Cagan, John Cutler, etc.). I think we support everything you mention here, but at the same time removing some of the hurdles that many teams experience in getting an empowered team to work well together.

Yeah, that is a great point!

I promise we know a great deal about what we're talking about in this case :)

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.

Thanks for the feedback! Great point!

Thanks for your comment! The main point we wanted to come across is that issue trackers are _not_ designed for best of practice product development practices. Still, teams use the for product development, and there are challenges to that.

Using issue trackers to track bugs is great.