Connect Linear to recover why a direction was dropped, straight from the issues

Linear is where a product team writes down what it is building and why. The "why" is the valuable half, and it is the half that disappears: it lives in issue descriptions edited after a long discussion, in project updates, and above all in the issues that were cancelled — which is where the reasons a direction was rejected are kept. The Linear connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.

Ask why a direction was dropped

Cancelled and deprioritised issues are the cheapest institutional memory a team has, and nobody browses them. Connected, they answer questions — so the argument that was already had does not get had again.

Check a proposal against what was already agreed

Before you write the brief, ask whether the team has already settled the question. The answer names the issue or project update it came from, so you can quote it rather than paraphrase it.

Onboard without borrowing someone's afternoon

A new engineer can ask why a feature works the way it does in Chat and get the reasoning from the issues that preceded the build, instead of reconstructing it from someone's memory.