Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt

Use this file to discover all available pages before exploring further.

Introduction

This page explains the metrics available in Team Insights and how to interpret them for your organization.

Assignment Metrics

Total Runs

The total number of times assignments have been executed in the selected time period. What it tells you:
  • Overall automation activity level
  • Whether usage is growing or declining
  • Comparison baseline for different periods

Completed Runs

Runs that finished successfully without errors or interruptions. What it tells you:
  • Reliability of your assignments
  • Success rate of your automation
  • Whether assignments are working as expected
Healthy target: Aim for 90%+ completion rate. Lower rates may indicate issues with Connections, SOPs, or edge cases.

Active Assignments

Assignments that have had at least one run in the selected period. What it tells you:
  • How many assignments are actually being used
  • Breadth of automation across your workflows
  • Whether some assignments are unused and could be retired

User Metrics

Active Users

Team members who have run at least one assignment in the period. What it tells you:
  • Adoption rate across your team
  • Whether automation is spreading or concentrated
  • Opportunities to improve adoption

Runs Per User

Average number of runs initiated by each active user. What it tells you:
  • Engagement depth with automation
  • Power users vs casual users
  • Potential for expanding usage

Source Metrics

Manual Runs

Runs triggered by users clicking the Run button. Typical patterns:
  • Higher for new assignments being tested
  • Common for ad-hoc tasks
  • May indicate scheduling opportunities

Scheduled Runs

Runs triggered automatically by schedules. Typical patterns:
  • Indicates mature, trusted assignments
  • Represents true automation value
  • Should grow as assignments prove reliable

Slack Runs

Jobs triggered through Slack connection. Typical patterns:
  • Shows collaboration and accessibility
  • Common for team-facing assignments
  • Indicates good connection with daily workflows

Growing Usage

Increasing runs and active users indicates:
  • Successful adoption of automation
  • Value being recognized by the team
  • Opportunity to expand to new use cases

Declining Usage

Decreasing activity might mean:
  • Initial excitement wearing off
  • Assignments not meeting needs
  • Process changes making assignments obsolete
  • Team members may need more support or better assignments

Steady Usage

Consistent activity suggests:
  • Stable, reliable automation
  • Assignments well-matched to workflows
  • Opportunity to optimize or expand

Benchmarking

While every organization is different, consider these general benchmarks:
MetricStarting OutMaturingAdvanced
Completion Rate70-80%85-95%95%+
Scheduled vs Manual20/8050/5070/30
Active Users<25% of team25-50%50%+

Things to Know

  • Metrics reflect activity within the selected time period
  • Compare similar time periods for meaningful trends
  • Seasonal variations may affect some metrics
  • Focus on trends rather than absolute numbers