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.

That is a great way to frame it!

And yeah, the title was written in a way to be a bit provocative, but also pointing at that many (maybe most) teams use issue trackers for their product development flow.

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.

Thanks for sharing my article! :)

For something less task-focused and more customer-oriented, we built https://www.kitemaker.co :)

Thanks for the shoutout :)

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 :)

Thanks! Yes, still early days, but trying our best to build something that will help many teams work better together :)

Amazing! Looking forward to trying you out the next time we're hiring :)

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.

If you are looking for a fast alternative, we're building www.kitemaker.co (I'm one of the founders). We're part of the upcoming YC batch, and I'd be happy to help you onboard and import existing projects if needed.

I think this article is a pretty good description of good pm. I’ve both been pm myself and managed teams og pms, and anyone fitting this description would be a great hire.

I don't disagree that there could be a lot more context there, but as a PM myself, the tips are not bad. Just missing the whys.

Hi! Thanks for your comment!

Happy to answer questions about the issue screen! :)

To foster collaboration, we made the description huge (you can write anything from a line to 1 pager, to X pagers there). We also believe that communication contains persistent information and non-persistent information, so we have on the same screen an activity feed with comments (for non-persistent information), next to the description (for jotting down persistent information).

We also have a principle of hiding complexity, so there are not 15 fields to fill in for each issue, a title is enough.

You can also try Kitemaker yourself for free by signing up at www.kitemaker.co