We write for those who have to decide: launch a project, stop it, choose an architecture, commit a budget. Our insights start from situations encountered on assignments and seek to answer a specific question, rather than to comment on the news.
What you will find here
In-depth analysis of artificial intelligence, data, cloud and platforms. Each article opens with a two-sentence summary and ends with links to the relevant areas of expertise and definitions.
We favour three types of topic: methods that have proven themselves, mistakes we see being repeated and the questions to ask before committing to a project.
Our editorial line
Three rules guide what we publish.
Accuracy first. A regulatory text is cited by its reference. A figure is sourced, or it is not published.
The decision-maker’s point of view. We explain what a choice implies in terms of cost, risk and organisation, not only how a technology works.
Restraint. No promises, no superlatives. If an approach has limits, we write them down.
How we choose our topics
Our topics come from three sources. First, the questions our clients ask us on assignments: when the same question comes up in several organisations, it deserves a written answer. Second, changes in the regulatory framework, because they alter what is possible and how to prove it. Finally, feedback from our consultants on what worked and what did not.
We do not publish to keep to a schedule. An article appears when we have something useful to say on a topic, and it is updated when the context changes.
Further reading
If you are looking for the definition of a term, the glossary is more direct. If you are looking for what we can do for you, see our expertise.