Published research
Practitioner research on how AI and technology work succeeds or fails in the work. Each report states its method and its limits, and each comes with an open PDF.
Latest
Being found by buyers who research through AI assistants
How assistants reach, read and name a business, and a self-check you can run in an afternoon.
Amit Govil · October 22, 2026
Read the report
About the reports
What does a report do that a shorter piece cannot?
A report is the piece we write when a problem needs documents opened, mechanisms separated and a self-check a reader can run on their own organization. It is long on purpose. Numbered exhibits, pictures and tables that each make one point, carry the argument, and each has a written description so nothing depends on seeing the drawing. Every report comes as an open PDF you can circulate before a meeting.
The other pieces have other jobs. A white paper argues one question toward a decision, a perspective describes a pattern in one short sitting, and a briefing records what a rule says on a given date. The report sits underneath them, where the mechanism behind their claims is set out in full.
The problems on the shelf
Why AI pilots stall before production looks at the moment a pilot passes from the people who proved it to the people who must run it, and why live data, approvals, the working process and an owner all meet there with nobody assigned.
Who owns an AI system after launch shows how a name in a register decays into a system that nobody can change, correct or switch off once the project team has moved on.
When systems and data stop agreeing tracks one fact entered in more than one place, until a reconciling spreadsheet becomes the real system.
Being found by buyers who research through AI assistants sets out what an assistant must be able to fetch, read and tell apart before it can name a business, with the fixes in order.
Where to look first in a report
A report is built to be read in parts. The in-brief and key findings stand alone, so a leader who stops there still has the argument. The table shows what the other parts hold.
| Part of the report | What it holds | Read it when |
|---|---|---|
| In brief and key findings | The answer, and each finding as a sentence you can quote | You need the conclusion before a meeting |
| Method and limits | What was opened and read, and what the report cannot show | You are deciding how far to trust a finding |
| Findings | One mechanism each: why it happens, what you see, what it costs | You are explaining the problem to colleagues |
| Response | The steps in order, with who does each and what exists at the end | You are ready to act |
| Self-check | Statements you can test against your own organization | You want a first read on your own position |
How a report is made and checked
- 01
It starts with a question a leader would otherwise answer from opinion.
We choose a problem from delivery work where the usual explanation is thin, and the report has to say something a reader can test.
- 02
Public documents are opened, not remembered.
Laws, standards and official studies are read for the passage the claim needs, and the date of the reading goes in the sources.
- 03
Delivery experience enters as pattern.
Every engagement is under NDA, so what we have seen appears as a mechanism and never as a case. No client is named.
- 04
Figures stay out of the prose.
A number appears only in a chart drawn from a primary source, with its date. Elsewhere the report uses a diagram or a table.
- 05
A person answers for the result.
Drafting tools may help. A person checks each fact against its source and puts a name to the report.
How long does a report stay current, and where does it lead?
A report is reopened when a document it relies on changes or when delivery work shows a mechanism it missed. Rules that move quickly are left to briefings. From a report there are practical routes: the free tools turn its self-check into a scored read in your browser, and AI Consulting is where a finding about pilots or ownership becomes work with a named owner at the end of it.
What do readers ask before opening a report?
Which report should I read first?
Start with the problem you recognize. A pilot that worked and never reached daily use points to the report on stalled pilots, a system nobody can change or stop to the ownership report, figures that disagree to the systems report, and buyers who ask an assistant to the visibility report.
Can I share a report with colleagues before a meeting?
Yes. Every report comes with an open PDF you can circulate, with no email form in front of it. The in-brief and key findings stand alone, so a colleague who reads only that part still has the argument, and each exhibit carries a written description.
Does a report tell me how likely this failure is in my organization?
No. A report explains how a failure forms and what it looks like early, but it cannot say how likely the failure is for you, and none states a rate. The self-check at the end lets you test the pattern against your own organization.
How do I know a report is still current?
Check the sources section, which records when each document was read. A report is reopened when a document it relies on changes or when delivery work shows a mechanism it missed. Rules that move quickly are left to briefings, so read the primary text before you act on a rule.
Which of these failures is already at work in your organization?
The self-check at the end of each report is the quickest way to find out. If a finding fits, the next step is a conversation about what to change first.