Strong adoption. Uneven depth.
95% actively use AI, yet 30 of 127 report lower future-use intent. The expert design & deployment block scores 34.4/100.
BTS has already embraced AI. The strategic challenge is to convert widespread individual use into deeper, safer and measurable business value.
121 OF 127 EMPLOYEES
95% actively use AI, yet 30 of 127 report lower future-use intent. The expert design & deployment block scores 34.4/100.
The report calls for a formal AI usage policy, an approved-tools catalogue, and fast approval of advanced or new AI use cases.
Mobilise 43 / 37 / 48 assessed learners across three tracks, activate internal Champions, and follow the 30 / 90 / 180-day roadmap.
Hover or focus ⓘ beside each indicator to see what it measures · Score /100
No AI skeptics in the survey
Intent to use AI more, equally or less
Three signals that change the conversation
11 of 20 employees in Market Management anticipate reducing AI use. Purpose-built use cases are a priority.
The 15 critical exposure cases are concentrated among confident users, not inexperienced beginners.
Expert design and deployment scores 34.4/100 against 87.7/100 on fundamentals.
BTS AI Barometer • Executive Report • October 2026
AI adoption is widespread, but the findings reveal concentrated loss of momentum, uncontrolled use and uneven capability. These are leading indicators, not confirmed incidents.
Percentage of respondents by major department
15 individual critical-level classifications
Risk-level classification of 127 surveyed employees
Run a hands-on workshop to discover actual market-analysis use cases. The study hypothesizes a relevance problem, which should be validated with the team.
Start with Product & IT Operations, Sales and Software Development, which account for 12 of the 15 critical exposure cases.
The report flags a high-exposure individual case within Finance. Handle it privately through Security and the appropriate management channels.
Give technical leaders a secure fast lane, and those struggling or losing confidence role-specific coaching rather than generic messaging.
Explore every department, compare scores and uncover the actions specifically recommended for each team.
Highest depth among major departments · 82.6
55% losing momentum · 11 of 20
5 of 15 critical cases company-wide
| Department | n | AI maturity | Commitment | Depth | Momentum loss | Critical exposure |
|---|
Two self-reported indexes plus intent and depth
A separate 25-question technical assessment measures what employees actually know. It reveals where BTS can use AI comfortably, and where building advanced systems becomes difficult.
Correct-score index by domain, 0 to 100
128 assessed respondents
Beginner
10.9%
Basic
22.7%
Advanced
28.9%
Expert
37.5%
The technical assessment distribution is not the same as the later 149-person manually reviewed roster included in the report's annex.
Self-reported maturity versus tested knowledge
Different problems require different training
Incorrect belief that models search the web or reason like humans.
Incorrect understanding of the concept.
Admitted knowledge gap (“I don't know”).
Admitted knowledge gap (“I don't know”).
A recommended sequence over 30, 90 and 180 days. These are proposed actions in the October 2026 report, not a live implementation tracker.
Recommendations for sponsorship and validation, not decisions already taken.
15 critical Shadow AI exposure classifications; 12 across Product & IT Operations, Sales and Software Development.
Endorse an AI usage policy, approved-tools catalogue, accountable owners and a fast approval route for advanced use.
Published guardrails, maintained tool inventory and documented, proportionate approvals.
128 technical assessments identify 43 learners in Fundamentals, 37 in Application and 48 in Engineering.
Sponsor staged, practical training; use the four-level curriculum and role-specific exercises.
Training participation and verifiable improvement in applied skills and subsequent assessment results.
The depth-of-use index is 66/100, below overall AI maturity of 72/100.
Prioritise departmental use cases with clear owners, output-quality checks and measurable time or process benefits.
Progress towards the report's depth-of-use target of 75/100, plus verified pilot benefits.
30 people expect lower future use; 11 of 20 in Market Management. The survey identifies 21 potential Champions.
Co-design real use cases with Market Management; select and recognise Champions with time to support colleagues.
Reduced momentum-loss signal and an active, supported Champion network.
The October 2026 assessment provides a baseline; the report proposes eleven committee functions across four axes.
Validate the committee charter, quarterly reporting and six-month repeat of both surveys.
Comparable follow-up scores, clear ownership, documented use cases and visible open-risk reporting.
Present the programme as short, role-based practical sessions. For planning transparency, the October report suggests 4–6 hours for Track A and 8–12 hours plus a project for Track B; Track C has no fixed duration specified. Final scheduling and workload should be validated with the relevant teams before rollout.
Every level closes with practical verification, not just a knowledge quiz
LLM limits, hallucinations, safe data use, prompting and the 4 D's.
Projects, query/action connectors, Jira acceptance criteria, prompt injection.
Skills, multi-connector flows and, for technical roles, Claude Code and SDD.
Advanced governance, MCP, agent security, RAG, evaluation and SDD at scale.
Suggested timing from the report; current execution status has not been assessed.
Recommended activities for the first month
Rapid guardrails and a targeted response to disengagement establish a foundation for the next phase of value creation.
Targets in the report are future checkpoints, not current achievements.
3-month improvement target
Baseline depth index to proposed target.
6-month assessment target
Average technical test score.
6-month target in technical teams
34.4 is the company-wide baseline for B4; >50 applies to technical teams.
The proposed AI Committee coordinates secure and measurable use, prioritizes investment and keeps training active. It does not approve every everyday use of an authorized tool.
Select an axis to explore its responsibilities
Click a function to inspect its owner and cadence
Execution responsibilities proposed in the report
Simplified governance logic from the report's approval flow
Governance, risk and priority decisions
Protecting speed and team autonomy