Waves in Motion

Zooming Out & “Creative Destruction”

Just like the wind and gravitational pull of the Sun and Moon create constant waves, our Waves framework is also a constant exercise.

Up until now, we have described a single cycle: from discovery in W1, to prototyping in W2, and first verticalizing to then horizontalize into a platform in W3.

However, M2ML is not a static, single process. When a company hits a performance limit, it must ask itself: is our system fully optimized? If a new way to achieve greater efficiency (with meaningful ROI) is identified, then a new micro cycle begins. Though these cycles are constant, they are not necessarily continuous, since many times they depend on external shocks to initiate them.

This brings us back to our Rapid Robotics Case Study. Once Rapid achieves a minimum threshold of deployments, they will need a fleet management solution that doesn’t rely on human supervision. This is where the “learning” of M2ML comes in- and to get there, Rapid will inevitably cycle back to W2.

Any single iteration only gets a company so far. But if constant optimizations are made, building an M2ML solution begins to resemble the S curve above: micro cycles within a larger macro cycle of innovation and “creative destruction” (a term coined by economist Joseph Schumpeter in 1942) across business cycles.