Skip to content

Phase 1: Adoption

Are developers using Copilot? How deeply? Where are the gaps?

Phase 1 focuses on understanding adoption breadth and depth before attempting to measure business impact. You need stable adoption data before correlating Copilot usage with delivery outcomes.

Where to Start

Your situation Start here
Just enabled Copilot, need basic visibility Quick Start — native dashboards, 30 min
Need custom reports, BI integration, or historical data Analytics-Ready — NDJSON + BI, half day
Want to understand what metrics exist and what they mean Metrics Guide — definitions, scope, limitations
Looking for tools to visualize adoption data Tools & Resources — Phase 1 tool catalog

Key Adoption Metrics at a Glance

Metric What It Tells You Target Signal
DAU/WAU/MAU How many developers use Copilot Steady growth
Acceptance Rate Are suggestions relevant and trusted Stable 25-35%+
Feature Mix Depth beyond completions (chat, agent) Broadening
Seat Utilization Are paid seats being used >70% active
Agent Adoption % Advanced feature uptake Growing

→ Full definitions and interpretation: Metrics Guide

Phase 1 Readiness Signals

You're ready to add Phase 2 (Impact & ROI) when:

  • DAU/WAU ratio ≥ 60% of licensed seats active weekly
  • Acceptance rate stable for 4+ weeks
  • At least 2 features used by >50% of active users
  • ≥ 30 days since broad enablement

Phase transition is additive

You don't stop measuring adoption when you enter Phase 2. You add outcome metrics on top.

What to do next: