Linear + Outcome
Linear holds your issues, projects and what customers asked for. Outcome holds the goals they serve. Together, every project sits under a goal, a request counts once per customer asking, and a decision becomes a new Linear issue.
Linear brings the facts. Outcome turns them into decisions.
| Use | From Linear | What Outcome does with it |
|---|---|---|
| Structure |
| Each goal gets an owner, and each piece of work a team. |
| Measures |
| A goal's number is read on a schedule, with its history. |
| Goals |
| They arrive as proposals, and a person accepts each one. |
| Signals |
| Grouped into themes and put in front of the goal they bear on. |
| Work |
| Placed under the goal it serves, so a goal with nothing behind it shows. |
| Write-back |
| A decision becomes an item in the team's own tool, signed by whoever approved it. |
Linear + GitHub + PostHog + Salesforce + Outcome
What it never reads
- Private teams
- Comments, history and attachments
- Customers' names and revenue
- Changes to anything already in Linear
Status
Preview Engineering
Live In the product today. Preview Working, refined with customers.
Connected in minutes, by an admin.
- 01Open
An owner or admin opens Settings, Integrations, Linear.
- 02Connect
Paste: Personal API key.
- 03Read
Outcome reads it on the schedule you set, from the first day.
- 04Send
Work goes to Linear only when a person approves it.
Connect Linear and see what it brings in on the first sync.
Also in engineering Atlassian · GitHub · File import · Sentry · ServiceNow · PagerDuty · Azure DevOps · GitLab