File import + Outcome
Some work lives in an export, not an API. Outcome reads it like any other source. Together, a Jira export or a spreadsheet of initiatives sits under the goals it serves, and a fresh upload updates it.
File import brings the facts. Outcome turns them into decisions.
| Use | From File import | What Outcome does with it |
|---|---|---|
| Work |
| Placed under the goal it serves, so a goal with nothing behind it shows. |
File import + TeamForm + Google Sheets + Outcome
What it never reads
- Anything outside the file you upload
- Writes of any kind to File import
Status
Live 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, File import.
- 02Connect
Nothing to paste: start it in Settings.
- 03Read
Outcome reads it on the schedule you set, from the first day.
- 04Done
Nothing is ever written to File import.
- Portfolio managementStrategy to execution
- Funding and business casesStrategy to execution
- Quarterly planningStrategy to execution
- Technology ledgerOutcome costing
- Budget and planOutcome costing
- Cost per outcomeOutcome costing
- Spend watchOutcome costing
- Your operating modelPlatform
- Integration builderPlatform
Connect File import and see what it brings in on the first sync.
Also in engineering Atlassian · GitHub · Sentry · ServiceNow · PagerDuty · Azure DevOps · GitLab · Linear