Methodology · AI & productivity

Evidence-based methodology.

The way we train and transform teams is empirical: every practice we teach rests on what the studies show — and gets measured before and after. Here is the evidence we build on, study by study, with how we apply each one in our work.

Let's study your case

Tell us where your team is and we'll tell you which methodology we would apply — and the evidence behind it.

You don't have to take our word for it.

The reference studies on AI and team productivity, summarized in plain language, with their caveats and a link to each original.

We summarize and flag the limits of each study. Credit belongs to the authors — read the originals.

2026

+24%
Microsoft (arXiv) · 2026 · Murphy-Hill, Butler y Savelieva
Microsoft (arXiv) · 2026

Engineers who adopted command-line AI coding agents (Claude Code and GitHub Copilot CLI) merged roughly 24% more pull requests, with the effect sustained over the four months observed.

Study of Microsoft's early-2026 rollout of CLI coding agents across tens of thousands of engineers, using real telemetry and a synthetic counterfactual built from developers who never used the tools. One of the first at-scale studies of autonomous agents (not autocomplete) in production.

Caveat: It is observational (non-randomized adoption, synthetic counterfactual) and merged PRs are an imperfect proxy for delivered value, as the authors themselves acknowledge.

How we apply it: This is at-scale evidence for our thesis: the leap is from autocomplete to agents. We train teams in exactly that leap — from "using AI" to directing Claude Code with specs, context and loops.

Read the study
+26,08%
Management Science (MIT, Princeton, Microsoft) · 2026 · Cui, Demirer, Jaffe, Musolff, Peng y Salz
Management Science (MIT, Princeton, Microsoft) · 2026

Developers randomly given access to an AI coding assistant completed 26.08% more tasks than the control group.

Three RCTs at real companies (Microsoft, Accenture and a Fortune 100 firm) with 4,867 developers in total, published in Management Science in February 2026. Less experienced developers showed higher adoption and larger gains.

Caveat: The standard error is wide (10.3%), gains concentrate among junior developers, and the Accenture experiment is the same one GitHub publicized in 2024 — this paper is its peer-reviewed, pooled version.

How we apply it: The gain concentrates among the least experienced — when the system lends them judgment. We use this to design rollouts: first the system (specs, review, guardrails), then the licenses.

Read the study
+14% a +50%
Stanford HAI (AI Index 2026) · 2026 · AI Index Steering Committee
Stanford HAI (AI Index 2026) · 2026

Measured AI productivity gains range from 14–15% in customer support to 26% in software development and 50% in marketing output, and are largest in structured, measurable work rather than deep-reasoning tasks.

Economy chapter of Stanford's 2026 AI Index, the reference annual synthesis of empirical evidence. It also reports 88% organizational AI adoption and a nearly 20% drop since 2024 in employment of developers aged 22–25.

Caveat: It is a synthesis of third-party studies, not primary research — the 26% software figure comes from the Cui et al. RCT — and it warns of possible learning penalties from heavy AI reliance.

How we apply it: We use the AI Index as an expectations map by domain: where the gain is structural and where it is not yet. We tune each program and transformation to that map instead of promising the same multiple everywhere.

Read the study

2025

>80%
DORA / Google Cloud · 2025 · State of AI-assisted Software Development
DORA / Google Cloud · 2025

90% of technology professionals now use AI and over 80% say it has increased their productivity — but higher adoption is associated with both higher delivery throughput and higher delivery instability.

DORA's 2025 report (nearly 5,000 professionals surveyed plus over 100 hours of qualitative research). Its core conclusion: AI is an amplifier — it magnifies the strengths of well-run organizations and the dysfunctions of struggling ones.

Caveat: Productivity is self-reported (perception, not direct measurement) and 30% of respondents report little or no trust in AI-generated code.

How we apply it: "AI amplifies what you already are" is the line we use most with leadership: that is why we start not with the tool but with the foundations it amplifies — delivery flow, specs, review. On solid ground it multiplies; on chaos, it multiplies chaos.

Read the study
−2 h/semana
NBER (Microsoft Research / HBS) · 2025 · Dillon, Jaffe, Immorlica y Stanton
NBER (Microsoft Research / HBS) · 2025

Workers with a generative AI tool integrated into their apps spent two fewer hours per week on email and reduced out-of-hours work — but the quantity and composition of their tasks did not change.

A 6-month field experiment across 66 firms with 7,137 knowledge workers, randomly assigning access to AI integrated into email, meetings and writing. Effects were measured with real usage telemetry, not surveys.

Caveat: Giving AI to individuals without redesigning processes did not change what work gets done: the time saved did not translate into detectable extra output.

How we apply it: The study that explains why "handing out licenses" transforms nothing: without redesigning the process, saved time evaporates. Our transformations redesign the workflow so freed hours turn into delivery.

Read the study
-19%
METR · 2025 · Becker, Rush, Barnes, Rein
METR · 2025

Experienced open-source developers took 19% LONGER to complete real tasks when allowed to use AI tools, despite expecting to be 24% faster.

METR RCT with 16 experienced developers solving 246 real issues (~2h each) in mature open-source repositories they themselves maintain, with per-task random assignment of AI allowed or disallowed.

Caveat: Small sample (16 developers) and a very specific context — experts who know their codebase deeply, using early-2025 tools — so it does not generalize to all teams or later tooling.

How we apply it: AI without method slows down even the best. It is the study we cite most when starting a transformation: we do not install tools, we change how the team works — context, harness, loops — which is where the gain lives.

Read the study

2024

+8,69%
GitHub / Accenture · 2024 · GitHub + Accenture
GitHub / Accenture · 2024

In the randomized trial with Accenture developers, Copilot yielded 8.69% more pull requests per developer, a 15% higher merge rate, and 84% more successful builds.

Randomized controlled trial in a real enterprise setting: Accenture developers assigned to Copilot or control, measuring objective workflow metrics (PRs, merges, builds) plus perception surveys.

Caveat: It is vendor research (GitHub sells Copilot), several key metrics are self-reported, and the post does not disclose the number of participants.

How we apply it: From the lab to the enterprise the number drops from +55% to single digits: the difference is the system around the tool. Our transformation work targets exactly that — the workflow (specs, CI, review) that turns individual speed into delivery.

Read the study
-7,2%
DORA / Google Cloud · 2024 · Accelerate State of DevOps
DORA / Google Cloud · 2024

A 25% increase in AI adoption is associated with an estimated 7.2% reduction in software delivery stability and 1.5% in delivery throughput, even as individual productivity (+2.1%) and code and documentation quality improve.

Tenth annual Accelerate State of DevOps report, based on DORA's global survey of technical professionals (over 39,000 across a decade of research). It models estimated change in delivery outcomes as a function of AI adoption.

Caveat: These are correlational survey estimates, not an experiment; DORA hypothesizes the cause is larger change batch sizes as AI makes it easy to produce more code — a method problem, not a tool problem.

How we apply it: This is why we teach agentic development with specs and small changes: more code is not more delivery. We instrument delivery — small PRs, CI, observability — so individual speed is not paid for in stability.

Read the study

2023

+55,8%
GitHub / Microsoft Research · 2023 · Peng, Kalliamvakou, Cihon, Demirer
GitHub / Microsoft Research · 2023

The group with access to GitHub Copilot completed the task 55.8% faster than the control group.

Controlled experiment (RCT) with recruited software developers asked to implement an HTTP server in JavaScript as quickly as possible. Completion time was measured for the Copilot group versus the control group.

Caveat: It is a single well-scoped lab task, not real work in a production codebase, and the authors work at GitHub/Microsoft, the tool's vendor.

How we apply it: The big gain shows up on well-scoped tasks. That is why we teach teams to slice work into small, bounded specs before handing it to agents: the lab speedup only transfers to production when the task looks like the lab's.

Read the study
+25,1%
Harvard Business School / BCG · 2023 · Dell'Acqua et al. (Organization Science)
Harvard Business School / BCG · 2023

Across 18 tasks within the AI capability frontier, consultants using GPT-4 completed 12.2% more tasks, 25.1% faster, with 32% higher quality on average.

Preregistered field experiment with 758 BCG consultants randomly assigned to no AI, GPT-4, or GPT-4 plus a prompt-engineering overview, on realistic consulting tasks (creative and analytical) with a prior performance baseline.

Caveat: On a complex task chosen to sit outside the AI frontier, subjects using AI were 19% less likely to produce correct solutions than those without it.

How we apply it: We train exactly that frontier: the judgment of what to delegate to AI and what not to. In our programs, people practice recognizing when a task sits within AI's capabilities and when it will confidently walk you to the wrong place.

Read the study
+14%
NBER · 2023 · Brynjolfsson, Li, Raymond
NBER · 2023

Access to a generative AI assistant increased issues resolved per hour in customer support by 14% on average, with +34% for novice and low-skilled agents.

Study of the staggered rollout of a generative-AI conversational assistant using data from 5,179 customer support agents. Productivity was measured as issues resolved per hour.

Caveat: The average effect hides strong heterogeneity: almost all the benefit accrues to novices, with minimal impact on experienced, highly skilled agents.

How we apply it: AI performs best when it carries the judgment of your best people. In transformations we codify the team's senior know-how — specs, context, guardrails — so the tool lifts the whole team instead of just assisting those who already knew.

Read the study
hasta 2x
McKinsey Digital · 2023 · Karaci Deniz, Gnanasambandam, Harrysson et al.
McKinsey Digital · 2023

With generative AI, code documentation was completed in half the time, new code in nearly half the time, and refactoring in nearly two-thirds the time — up to twice as fast on common tasks.

McKinsey lab study with more than 40 of its own developers across the US and Asia, performing code generation, refactoring, and documentation tasks over several weeks, crossing over between a two-AI-tool group and a control group.

Caveat: On high-complexity tasks savings shrank below 10%, and developers with under a year of experience took 7-10% LONGER on some tasks with the tools; it is also internal consulting research, not peer-reviewed.

How we apply it: The return depends on the task and the starting level — that is why we measure Tech Fluency and AI Fluency before and after training, and prioritize the tasks where the return is real instead of promising 2x on everything.

Read the study