|
> All of the AI projects we have observed as a team are failing. Every single one – we have seen 0% success in a year and a half, not only amongst projects we have been asked to participate in, but even within projects that we have observed in passing while doing totally unrelated work. That's got to be hyperbole, which blows out their credibility. They chose to say 'AI' rather than, for example, LLM, or Transformer model, or Diffusion model. This means they are including a huge swathe of things dating back to Expert Systems in their claim. And who hasn't seen productivity gains from more established AI technology - at least things like semantic search? Who hasn't seen diffusion models generating content in roles that might have done the work by hand before? Who hasn't seen some kind of regression algorithm (even using linear regression in a supervised context counts as AI - so you can absolutely do AI even in tools like Excel) improve operation productivity? Even if they narrowed it to the Transformer model LLMs which re-ignited recent public interest in AI, less ambitious projects to give them to engineering staff to automate easy but boring tasks in the background generally have been a success. More ambitious ones that are beyond what you'd reasonably expect the models to be able to do - for sure, those tend to fail. For most of these, the failure is predictable in advance, while some are at the boundary of what's possible, and so it is harder to predict (these are rationally genuine R&D projects). |
Go to their home page and one of their consulting selling points is recovering struggling projects.
One of their front-page selling points is that they use "ancient techniques" from books written prior to the year 2000, because presumably everything newer than that is bad?
> For non-executive management who might be struggling to deliver things that feel beyond their control, we have ancient techniques (see: books written between 1986 and 1999) to turn your team into the envy of the organisation, and we can drop in directly to get your team the resources it needs to save a struggling project.
This is entirely a selection bias issue that they've created for themselves: Advertise a consulting service for saving failing projects to companies that don't have internal expertise to handle it, then write blog posts that 100% of the projects you see are failing. Also refuse to help them, to guarantee they can't be converted to successful projects to keep the success number at 0%.