The Algorithm Maturity Level can be very insightful when figuring out with a team where to start the AI transition and what goals to set.
|Time||± 30 minutes|
|Difficulty||3 / 5|
|People||3 - 5|
|Author||erik van der pluijm|
|License||CC BY SA 4.0|
The Algorithm Maturity Level is a simple tool that can be very insightful when figuring out with a team where to start the AI transition and what goals to set. One of the important things to understand when thinking about AI and business is that it is difficult, or even impossible, to start with the holy grail an ‘autonomous’ system. There are many steps that you need to take before you get to that point (and, in many cases, it’s really not what you want to go for, but that aside). Even Google can’t do it from scratch. Google has a lot of these prerequisites so firmly in place that they now made it relatively easy to create more and better algorithms. Chances are, your organization has not (yet). So it’s important to find the ‘minimum viable algorithm’ that will take you the first step. The Algorithm Maturity Level tool is one way to help bridge the gap between often lofty goals of autonomous systems back to what is needed today to take the first step. The tool classifies algorithms into five categories: Descriptive algorithms. These algorithms are able to accurately describe what is happening. For instance, accurately monitoring a system’s behaviour and describing what is happening to users. The users are the ones that make sense of the information and decide to take action.
Each level builds on the previous levels. That means a prescriptive algorithm also has the capabilities of a predictive algorithm.
Plot the different ideas you have come up with (e.g. as an answer to the question “where will algorithms and AI or Machine Learning impact our business?”) on the canvas.
In what category does each idea fall? What exactly does it need to describe, diagnose, predict, prescribe, or control? Are you able to define how that is done today? What data, processes, and domain knowledge do you need? What is the quality level needed for the output of the algorithm?
For each idea, map it back to the preceding level. Now you have defined a simplified version of the idea. What would that simpler version of the idea look like? Is that already in place? Or is it also new? Would that simpler version already be valuable for your customers or yourself? Keep mapping back to the previous stage until you reach the descriptive level, or until there already is an alternative in place.
Dive deeper into what is needed for the ‘simplest’ version of the idea. Again, ask yourself what data, processes, and domain knowledge you need. What is the minimum quality level needed for the output of the algorithm? When would it start to become useful? Now you have a candidate for your ‘minimum viable algorithm’.
Of course, reality is unforgiving. To see if that minimum viable algorithm would be feasible, other steps are needed. But at the very least you have a way to facilitate the discussion and simplifying a complex, amorphous conversation topic.
Sign up for free now and receive a weekly email with one new innovation tool straight to your inbox. 🚀