Mandate the outcome and let teams choose the tool
Leaders assume a usage dashboard shows whether an AI mandate works. It shows who touched the tool, which engineers can perform. Team delivery and quality show whether work improved.
In brief
- Google's 2025 DORA (DevOps Research and Assessment) report, drawn from nearly 5,000 technology professionals, found AI adoption associated with higher delivery throughput but still with lower delivery stability.
- Once individual usage is watched, people optimise for visible use, and in some organisations the slow part of delivery was never the writing of code.
- Set one outcome per workflow, measure delivery and quality by team, keep usage as a diagnostic and let teams decline a tool with evidence.
Should a company require its engineers to use AI tools, and how would it know the requirement worked? Many leadership teams have answered the first half. In KPMG Canada's 2025 survey of 753 business leaders, 36% said their organisation has a policy mandating AI use in employees' roles. Another 39% agreed somewhat.
The second half is where programmes go wrong. Many track who uses the coding assistant and how often, and managers ask in stand-up whether the tool was tried first. The programme lead sees a dashboard trending up. The engineer sees a metric that can be satisfied without doing better work.
We think the push is defensible and the instrument is wrong. Mandate outcomes, not tools. Measure delivery and quality at team level, keep usage as a diagnostic, and give teams a documented way to show that a tool does not fit their work.
A usage mandate measures the tool; an outcome mandate measures the work
The decision rule is short: if a metric can be satisfied without the work improving, it cannot be the target.
| Usage mandate | Outcome mandate | |
|---|---|---|
| What is measured | Prompts, acceptance rate, hours or tokens per person | One outcome per workflow, such as lead time for changes |
| Level of reporting | Individual | Team |
| What it rewards | Visible use of the tool | Delivery and quality against a baseline |
| Role of usage data | The target | A diagnostic for training and access |
| Response to a skeptical team | A place on the list | A right to decline with documented evidence |
Source: Wennovate framework.
Leaders who mandate are answering real inertia
New tools face inertia, and a voluntary rollout often stalls at the enthusiasts. Gallup's survey of 19,043 US workers found only 28% of employees in AI-adopting organisations strongly agreed their manager actively supports their team's AI use.
Those who did were 2.1 times as likely to use AI a few times a week or more. They were 6.5 times as likely to strongly agree the tools were useful for their work. A visible push from leadership changes behaviour.
There is a learning argument too: nobody can judge a tool they have not used seriously, and some skepticism is unfamiliarity. A mandate forces the trial that produces informed opinions. A team that says "this does not work for us" after a week of half-hearted use has not earned an exemption. None of that requires counting anyone's prompts.
Watched usage becomes performed usage
Practitioners have described the pattern for a year. In an August 2025 r/sysadmin thread, commenters described AI use written into annual evaluation goals and leadership tracking weekly hours of use. In an October 2025 r/ExperiencedDevs thread, the most-upvoted reply described each person's AI use reported to leadership, with light users placed on a list.
A heavily discussed Hacker News post in May 2026 framed AI adoption pressure as a management signal. A third-party summary of the thread describes a developer facing high daily token quotas and repeated manager prompts. Its central split was between real gains on well-bounded tasks and usage itself being treated as proof of progress.
Canadian employers helped set the tone. Shopify's CEO wrote in an April 2025 memo that staff must show AI cannot do a task before requesting more headcount. OpenText made AI use a baseline expectation in May 2025, alongside 1,600 job cuts.
A usage target is easy to hit without improving anything. Accept the suggestion, then rewrite it. Open the chat window before every task. The Hacker News summary makes the same point: once usage is watched, people optimise for visible use, and the number stops telling anyone anything.
Higher usage can coincide with worse delivery
Google's DORA programme drew its 2025 report from nearly 5,000 technology professionals. It found AI adoption now associated with higher delivery throughput but still with lower delivery stability. Its authors describe AI as an amplifier: strong teams improve, while struggling teams see their problems intensify. Separately, 30% of respondents reported little or no trust in AI-generated code.
In some organisations the bottleneck sits downstream of the code. One engineer at a large enterprise illustrated it in the top comment on a May 2026 Hacker News thread: code there takes six to twelve months to reach production. The delay came from provisioning, testing, sign-offs and release scheduling. A usage dashboard in that organisation measures the part of the system that was never slow.
Middle managers carry the mandate with less confidence than executives
The frozen middle, the managers who must turn a mandate into daily practice, sits between the memo and the queue. A US survey by Careerminds, reported by HRD Canada in September 2026, found 66% of C-suite managers felt very ready to lead AI-driven change. Among senior and middle managers the figure was 42%.
The pressure is sharper in Canada. KPMG Canada's May 2026 survey of business leaders found 31% of Canadian employees showing resistance to agentic AI, meaning agents that act on their own, against 16% globally.
Asked why, 51% of leaders pointed to trust and ethical concerns, and nearly 40% to job security or low confidence in AI skills. A mandate tracked by individual usage lands on exactly those fears. It reads as surveillance ahead of a headcount decision, whatever leadership intends.
NAV CANADA offers one Canadian answer. It created a shadow board of 16 peer-elected employees to advise executives on issues including technology change. Friction gets a route upward that bypasses the line manager.
Six rules turn a mandate into an outcome
- Set an outcome per workflow. For example, cut median lead time for changes by a quarter, or halve first-response time on tier-one tickets. Teams choose the tools.
- Measure delivery and quality at team level. Use the four DORA measures: lead time, deployment frequency, change failure rate and recovery time. Add review load, since that is where much of the AI cost lands. Do not report these by individual.
- Keep usage as a diagnostic. Aggregated usage shows where training or access is missing. It belongs to the enablement team, not to performance reviews.
- Create a right to decline with evidence. A team that runs a real trial and documents why the tool does not fit has complied. Publish those findings; they are often the most useful data you will get.
- Say what stops. An "AI-first" memo that adds work without removing any is a mandate for overtime. Name the reports, approvals or meetings that end.
- Enable managers first. Managers should use the tools on their own work before their teams are asked to, and need a channel to report what breaks.
In practice this becomes a short quarterly review per team: the outcome against its baseline, and what the team tried, kept and dropped. Leadership asks about the outcome first and the tooling second. That ordering is the whole intervention, and it still surfaces teams that never tried at all.
Put it to work: Test your AI mandate before the next review cycle
- Can any manager see an individual's prompt count, acceptance rate or token spend, and does it reach a performance review?
- Can each team name the outcome its AI use should move, and show it against a baseline?
- What did the last "AI-first" memo stop, and how would a team decline a tool with evidence?
When usage becomes the target, it stops working as a diagnostic
The costliest mistake is ranking individuals by acceptance rate, prompts or token spend, which produces a leaderboard of performers rather than of improvement. Tying bonuses or ratings to usage is close behind: it turns the one useful diagnostic into a target and ruins it.
Treating evidence-based skepticism as disloyalty is the other expensive error; the engineer who shows the tool fails on a given codebase has saved money. Nor should adoption be reported as a return; whether AI pays is a separate question with its own method, covered in Part 1 of this series.
The choice is not between a mandate and leaving people alone. It is between measuring whether people touched the tool and measuring whether the work got better. Choose the second.
Next in this series: Token bills are cloud's 2015 problem, with a known fix
Running AI across your teams? Book a 30-minute discovery call with the Wennovate team. No pitch deck required. Start with a scoping call
Sources
- Canadian businesses adopting AI, but few are seeing ROI, KPMG Canada, November 2025.
- Is this push for AI as insane everywhere? (archived snapshot), r/sysadmin, August 2025.
- Is there still room for AI skepticism at your organizations? (archived snapshot), r/ExperiencedDevs, October 2025.
- AI adoption pressure is becoming a management signal, HN Radar (summary of Hacker News item 48153379), May 2026.
- StatsCan finds AI adoption has doubled in businesses, but hasn't yet affected headcounts, BetaKit, June 2025.
- Manager Support Drives Employee AI Adoption, Gallup, November 2025.
- Announcing the 2025 DORA Report: State of AI-assisted Software Development, Google Cloud, September 2025.
- When everyone has AI and the company still learns nothing (thread mirror), Hacker News, May 2026.
- Are middle managers being left behind in AI transformation?, HRD Canada, September 2026.
- The state of AI in 2026: On the road to ROI, McKinsey & Company, August 2026.
- Canadian business leaders expect agentic AI to reshape the workforce, KPMG Canada, May 2026.
