Effectiveness Dashboard

The Agent Effectiveness dashboard presents organization-level analysis across three views: Throughput, Output, and Attribution.

Accessing the dashboard

Navigate to Settings → Analytics → Agent Effectiveness in the Factory App.

The dashboard requires the Advanced Analytics enterprise control. If you do not see it, see Enable Agent Effectiveness.

Throughput

The Throughput view shows how delivery speed changes as agent spend is applied, and where the change is concentrated.

Cycle time trend

Project, issue, and pull request cycle times over the selected period.

Consumption breakdown

Which projects, pods, and users consume the most resources.

Target comparison

Consumption measured against your organization's targets for the period.

Use the Throughput view to check whether resource consumption matches organizational intent. Concentration in a small number of projects is not inherently a problem, but it should be a deliberate choice rather than a surprise.

Output

The Output view maps spend to intent, so you can see what the work actually was rather than only how much of it there was.

Sessions are classified by intent, such as feature development, maintenance, bug fixing, or exploration. The view compares the resulting split of engineer time and Factory Standard Credits against your planned allocation for the period.

Reviewing this view during the quarter, rather than at the end, is what makes it actionable: a drift between planned and actual allocation can still be corrected while the quarter is in progress.

Attribution

The Attribution view traces an individual session to the work stream it belongs to and the output it produced.

Session

The originating Factory session.

Work stream

The issue or project the session maps to in your connected tracker.

Artifacts

The pull requests and repository changes the session produced.

Attribution depends on local signals, which are included with Advanced Analytics. When Advanced Analytics is enabled, Factory automatically backfills effectiveness data to the start of the account.

Interpreting the data

Cycle time compression is a trend, not a single number. Compare periods of comparable length and account for release cadence, holidays, and headcount changes before attributing a shift to agent adoption.

Attribution coverage is bounded by your connected integrations. A work stream tracked in a system you have not connected will not appear, which can make coverage look lower than actual usage.