A better way to organize product work

Organize work items and product conversationswithin a hierarchical tree of product featuresso everyone is on the same page and focused
The Nitty-Gritty Details
Why a tree of features?

Project management tools like Jira or GitHub issues are typical on product teams. Product conversations also happen on collaboration tools like Slack, Zoom, and email. But all these threads are separate and usually disorganized, and result in lots of lost context around features. A tree helps you capture all of these conversations and organize them in a way that pulls them all together.

What can I associate with each feature?

You can link to any external resource, such as a Jira issue, GitHub issue, or Google Doc. You can also add comments with markdown if there isn't an external resource that captures the conversation well enough.

How do I work with team members on building up the tree?

You can invite team members to your application. Team members can create new features and add comments and links to existing conversations.

How can I track a feature's evolution?

You can archive a feature to hide it from the tree. All archived features within a particular feature node are still accessible by clicking to expand the archive for that node. Archiving nodes and adding new features to replace them is a simple way to track the evolution of a feature.

Closed Preview

We're previewing DevelopmentKitchen with select teams

Join our preview and redefine how product work is organized