mortgage-origination #6522hWork moves as people and agents move it. Outcome reads each change from the tools it happened in.
“We ship more often than last year. Can we show what that did for the business?”
Outcome reads pull requests and deployments from GitHub and calculates delivery measures by repository. Each can sit on a goal, beside the result it was for.
The work people and agents have under way, in rows by the goal it serves. Work that reaches no goal has its own row.
Deployment frequency and lead time by repository, and change failure rate where failed deployments are reported.
See pull request cycle time and size by repository, and how each has changed.
Use a delivery measure such as cycle time as a goal's measure, with a target and a date.
Engineers state the goal once in the pull request description and the link is made for them.
Each team sees its own pull requests and tickets week by week, without tagging anything by hand.
See early whether the current rate of improvement reaches the target on time.
Live In the product today. Preview Working, refined with customers.
Kestrel's mortgage platform team sets a goal to halve its lead time.
Kestrel Bank is a fictional example. The figures are calculated by the product.
If a system you rely on is not listed, ask for it. Outcome’s integration builder drafts the connection, and it is offered to you to try before it is switched on. How the agents work
Delivery measures are read from GitHub and judged against your own targets. Time to restore and time to acknowledge are read from PagerDuty, in preview.