Answer: To measure sustained usage, use daily reports from the Copilot usage metrics API (used_cli and used_copilot_app) and count distinct day values per user per week, where a participant meets a three-day target when the count is at least three in each week. To measure team outcomes, compare the sprint period with your baseline using measures such as pull requests merged per developer, median time to merge pull requests, completion rate for maintenance or backlog work, defects/rework/review findings, and participant confidence and satisfaction from a short survey. Status: Confirmed Entry: tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes Revision: 3 Digest: sha256:9cfcf203965cd7dc (changes whenever the content changes) Timeline: Created: 2026-11-13T03:35:06Z Last changed: 2026-11-19T13:11:23Z (Team outcome measure: — → Pull requests merged per developer) Last verified: 2026-11-20T13:17:49Z Next check: 2026-11-21T13:17:49Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Sustained usage data source | used_cli and used_copilot_app | [1] | 2026-11-20 Activation target | three-day target | [1] | 2026-11-20 Team-level usage method | join the user-teams report with the per-user usage report | [1] | 2026-11-20 Impact dashboard window | trailing 28-day window | [1] | 2026-11-20 Team outcome measure | Pull requests merged per developer | [1] | 2026-11-20 Sources: [1] GitHub. "Driving team adoption of agentic GitHub Copilot - GitHub Docs". https://docs.github.com/en/copilot/tutorials/roll-out-at-scale/enable-developers/drive-team-agentic-adoption Role: primary. Accessed: 2026-11-20T13:17:49Z Quote: "used_cli and used_copilot_app show whether a person used each tool on a given day." (Supports: Sustained usage data source) Quote: "A participant meets a three-day target when the count is at least three in each week." (Supports: Activation target) Quote: "join the user-teams report with the per-user usage report" (Supports: Team-level usage method) Quote: "Adoption cohorts use a trailing 28-day window" (Supports: Impact dashboard window) Quote: "Pull requests merged per developer" (Supports: Team outcome measure) Snapshot SHA-256: faf666a62af48caf9f5eca9d2c366df9124de305c64498b2473bc37cde622de0 (captured 2026-11-18T13:14:39Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:14:39Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:17:49Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:17:49Z Last attempt: 2026-11-20T13:17:49Z Notes and limitations: Extracted automatically from a single official source (section "After the sprint"). Related: https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-copilot-impact How do I measure and demonstrate the impact of GitHub Copilot adoption? https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-copilot-success How do I measure success after adopting GitHub Copilot for reducing technical debt? https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-copilot-trial-success How do I measure the success of a GitHub Copilot trial? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-server-enterprise-prerequisites What are the prerequisites for configuring the GitHub MCP Server for GitHub Enterprise? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-server-usage-company How does GitHub Copilot control which MCP servers are used in my company? https://latestn.com/tool/github-copilot/admin-and-enterprise/mdm-file-based-settings-without-orgs How do I use MDM-managed or file-based settings for GitHub Copilot Business without organizations? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:11:23Z | changed | Team outcome measure: — → Pull requests merged per developer | [1] 2026-11-19T13:11:23Z | changed | Impact dashboard window: — → trailing 28-day window | [1] 2026-11-19T13:11:23Z | changed | Team-level usage method: — → join the user-teams report with the per-user usage report | [1] 2026-11-19T13:11:23Z | changed | Activation target: — → three-day target | [1] 2026-11-19T13:11:23Z | changed | Sustained usage data source: — → used_cli and used_copilot_app | [1] 2026-11-19T13:11:23Z | changed | impact dashboard window: trailing 28-day window → — | [1] 2026-11-19T13:11:23Z | changed | team outcome measure: Pull requests merged per developer → — | [1] 2026-11-19T13:11:23Z | changed | activation target: three-day target → — | [1] 2026-11-19T13:11:23Z | changed | usage fields: used_cli and used_copilot_app → — | [1] 2026-11-19T13:11:23Z | changed | sustained usage data source: Copilot usage metrics API → — | [1] 2026-11-17T13:38:30Z | changed | activation target: — → three-day target | [1] 2026-11-17T13:38:30Z | changed | usage fields: — → used_cli and used_copilot_app | [1] 2026-11-17T13:38:30Z | changed | sustained usage data source: — → Copilot usage metrics API | [1] 2026-11-17T13:38:30Z | changed | team-level view: join the user-teams report with the per-user usage report → — | [1] 2026-11-17T13:38:30Z | changed | deeper analysis fields: totals_by_cli and totals_by_copilot_app → — | [1] 2026-11-17T13:38:30Z | changed | usage API fields: used_cli and used_copilot_app → — | [1] 2026-11-17T13:38:30Z | changed | sustained usage target: three-day target → — | [1] 2026-11-13T03:35:06Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes POST: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I measure sustained usage and team outcomes after a GitHub Copilot adoption sprint? Revision 3, last verified 2026-11-20T13:17:49Z. https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes (accessed 2026-11-21T10:01:53Z). @misc{LatestN_tool_github_copilot_admin_and_enterprise_measure_adoption_outcomes_r3, title = {How do I measure sustained usage and team outcomes after a GitHub Copilot adoption sprint?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes}}, note = {Revision 3; digest sha256:9cfcf203965cd7dc; last verified 2026-11-20T13:17:49Z; accessed 2026-11-21T10:01:53Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes