addorai

The workflow that many teams use (myself included) is to iterate on detailed requirements in a doc, often in a table. They do this so that they can iterate on them in a more collaborative place vs Jira/Linear. It's also more accessible to the broader team (sales, design, marketing, etc).

Then after aligning they copy + paste those requirements into the issue tracker. They often also include a link back to the doc. But then you have two places that show the same requirements, one for eng and one for others and they almost always get out of sync. Plus it's a bit annoying for eng to have to parse thru the spec to map requirements for a specific ticket.

This is the workflow we're solving for!

As for Linear + Notion or Jira integration, it's entirely possible they add it but our approach is to focus on a few product team focused integrations and go deep on them

This is a great point. It's particularly useful to have that context into how the thinking evolved when you're looking back at a feature built months or years ago, to help you avoid doing something that was skipped in good reason OR make the same mistakes again.

We agree our decision feed is just step one to get there, we're also exploring other ways to show the evolution of work.

Sorry, I should have been more clear. In Confluence you can highlight content and create a ticket - it just prefills the title of the ticket to be the highlighted content. You still have to fill in the description. Then after pushing it to Jira there's no ongoing sync.

Fable has a true push + sync, where the live content in the editor is continuously sync'ed with Jira. This means you can keep editing product requirements in the place that your whole team lives (marketing, design, sales, of course eng) and not worry about tickets going stale

Thanks! We're exploring additional integrations with tools like Asana, ClickUp, and also Github to track features thru code complete.

Interestingly, Confluence doesn't have a 2 way sync with Jira. You can embed Jira tickets but you can't push content from Confluence to Jira and automatically create tickets.

Aside from that, we've designed Fable to be customized for the product team workflow - with features like the decision feed, zippy content editing, etc.

We also work with Linear, which has a fast growing user base

Our team is across several time zones and we're all well versed in the product of course :)

Haha yes, it was quite the challenge! Most of the time it just works, but in rare situations we'll ask the user to pick b/w the Fable version and the version on their issue tracker.

Productboard does a great job helping prioritize features based on customer feedback. Fable comes in when you want to define how that feature should work. We let teams collaborate on rich product specs for those features, then sync it over to issue trackers. We also have a decision feed that integrates with Slack and doc comments to make sure decisions made during product development aren't lost.

We have companies that use ProductBoard + Fable in conjunction.

Thanks for the feedback! We're excited about the 2 way sync as well since we want to prevent divergent sources of truth.

We've used Confluence in the past. We're designing Fable specifically for the use cases that product teams have - we're hyper focused on two for now. One is the workflow of collaborating on user stories/requirements and the other is tracking decisions made during the product development process.

Thanks! That's a great suggestion, we'll keep it in mind.