Published research
Practitioner research on why AI and technology work stalls, or sticks. Every report shows its method and limits, and every one has an open PDF you can pass around before a meeting.
Latest
Being found by buyers who research through AI assistants
How assistants reach, read and name a business, and a self-check for an afternoon.
Amit Govil · October 22, 2026
Read the report
About the reports
Why is a report so long?
We write a report when a problem needs documents opened, mechanisms pulled apart and a self-check you can run on your own organization. The length is deliberate. Numbered exhibits carry the argument, each a picture or table that makes a single point, and each comes with a written description. The open PDF lets you send it round before a meeting.
The other pieces do 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 beneath them, where the mechanism behind their claims is laid out in full.
What each report covers
Why AI pilots stall before production follows the moment a pilot passes from the people who proved it to the people who must run it. Live data, approvals, the working process and an owner all meet there, and nobody is assigned to any of them.
Who owns an AI system after launch shows how an owner's name in a register turns into a system that nobody can change, correct or switch off once the project team moves on.
When systems and data stop agreeing follows a single fact kept in more than one place, until a reconciling spreadsheet becomes the real system.
Being found by buyers who research through AI assistants covers what an assistant has to fetch, read and tell apart before it can name your business, with the fixes in the order to make them.
Where to look first in a report
Read a report 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 rest holds.
| Part of the report | What it holds | Read it when |
|---|---|---|
| In brief and key findings | The answer, with each finding as a sentence you can quote | You need the conclusion before a meeting |
| Method and limits | What we opened and read, and what the report can't show | You're deciding how far to trust a finding |
| Findings | One mechanism each: why it happens, what you see, what it costs | You're explaining the problem to colleagues |
| Response | The steps in order, with who does each and what exists at the end | You're ready to act |
| Self-check | Statements to test against your own organization | You want to check your own organization before talking to anyone |
How a report is made and checked
- 01
It begins where the usual explanation is thin.
We pick a problem from delivery work that the common story doesn't explain, so the report has to say something a reader can test.
- 02
We open public documents rather than remember them.
Laws, standards and official studies are read for the passage a claim needs, and the date of the reading goes in the sources.
- 03
Delivery experience enters as a pattern.
Engagements are under NDA, so what we have seen appears as a mechanism and not as a case. No client is named.
- 04
Numbers stay out of the prose.
A figure appears only in a chart drawn from a primary source, with its date. Everywhere else the report uses a diagram or a table.
- 05
A person answers for the result.
Drafting tools may help along the way. A named person checks every fact against its source before the report goes out.
How long does a report stay current, and where does it lead?
We reopen a report when a document it relies on changes, or when delivery work shows us a mechanism it missed. Fast-moving rules go to briefings instead. When a finding fits you, the free tools turn the 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 points 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 has an open PDF with no email form in front of it. The in-brief and key findings stand alone, so a colleague who reads only that still gets the argument, and each exhibit has 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 can't say how likely the failure is for you, and none states a rate. The self-check at the end lets you test the pattern on your own organization.
How do I know a report is still current?
Check the sources section, which records when each document was read. We reopen a report when a source changes or delivery work shows a gap, and fast-moving rules go to briefings, so go to the original text before acting on any rule.
Which of these failures is already at work in your organization?
Each report ends with a self-check, and the readiness assessment does the same for a single pilot. If a finding fits, tell us what you saw and we will suggest what to change first.