KDnuggets Home » News » 2018 » Oct » Opinions » 3 Stages of Creating Smart ( 18:n38 )

3 Stages of Creating Smart

The technology is advancing at a pace that should enable any company to create “smart” products, things and spaces. But how does one go about actually creating smart?

Tomorrow’s market winners will win with the smartest products.  It’s not enough to just build insanely great products; winners must have the smartest products!”

– Bill Schmarzo

Okay, that’s a pretty bold statement on my part (especially to challenge the famous Steve Jobs statement about building insanely great products), but then again I’m an analytics dude and think that analytics should be a part of every product and space – smart cities, smart cars, smart vacuums, smart hospitals, smart Chipotle…

But it’s not just me that thinks this way.  Tesla’s forthcoming autonomous cars will be nothing more than an artificial intelligence machine on wheels.  Tesla is building its own “AI computer”, complete with Tesla-specific microprocessors (silicon), to power its autonomous vehicles (see “Tesla Earnings Bombshell Reminds Us That Tesla's a Tech Company” for more details).  And Google is creating the foundation for smart products with its new Edge TPU; a tiny AI accelerator that will carry out machine learning jobs “at the edge” of IoT (see “Google unveils tiny new AI chips for on-device machine learning” for more details).

The technology is advancing at a pace that should enable any company to create “smart” products, things and spaces. But how does one go about actually creating smart? How does one decide where and how to integrate the growing power of machine learning, deep learning and artificial intelligence capabilities to power these smart products?  

Here’s my three step recipe for “Getting Smart” (with images of Maxwell Smart dancing in my head).


Step 1: Identify, Validate, Value and Prioritize the Decisions that Power “Smart”

The first step in “Getting Smart” involves identifying, validating, vetting, valuing and prioritizing the decisions1 (or use cases) that the smart entity or product needs to make in support of its operational goals.  For example, a “smart” city initiative would need to optimize decisions around traffic congestion, local events, crime, safety, road maintenance, building permits and more (see Figure 1).


Figure 1: Key Decisions (Use Cases) That Support a “Smart” City Initiative


See the blog “The #1 IOT Challenge: Use Case Identification, Validation and Prioritization” for more details on how to identify, validate, value and prioritize your use cases.

While there are many decisions that city management and planning must make to create a smart city, the list is not infinite.  And it’s important to note that not all decisions are of equal value, which is why you’ll want to assemble the key constituents in a workshop to prioritize the decisions (use cases) on the basis of financial and operational value vis-à-vis implementation feasibility within some agreed upon timeframe (see Figure 2).


Figure 2: Graphic from “Thinking Like A Data Scientist” Exercise


This prioritization process will require your best design thinking, facilitation skills to:

  • Drive organizational consensus on the initial steps and the process going forward.
  • Capture comments on the drivers of business value and the impediments to success.

By the way, capturing the “Getting Smart” requirements is not a “show up and throw up” exercise.  Detailing the business and operational requirements is critical to your “smart” entity success which includes quantifying the financial ramifications (costs and benefits), identifying the measures or KPI’s against which progress and ultimately success will be measured, and calculating the financial and operational implications of false positives and false negatives.  This upfront requirement gathering process is necessary to gaining organizational alignment, consensus and adoption of the decisions/use case roadmap is critical to the success of the endeavor. The organization should NOT proceed unless everyone has bought into and committed to the plan forward, including enlisting the support of the rank-and-file workers who are the ones who actually do the work.

Note: if the build out of use cases is approached in a coordinated fashion, the data and analytics developed for the first few use cases can be re-used for subsequent use cases, which not only accelerates the development of future use cases, but also continuously improves the predictive accuracy of existing use cases.


Step 2: Create Product Self-Awareness

Second, we need to identify the data and analytics requirements necessary to create a “smart” entity that self-monitors, self-diagnoses and self-cures.  This is the heart of smart; to create a product or space that is self-aware in its ability to optimize and learn from each interaction and transaction (see Figure 3).


Figure 3:  Exploiting The Three Stages of “Smart”


The 3 stages necessary to creating a continuously learning, “Smart” entity include:

  • Self-monitoring:  An environment that continuously monitors operations for any unusual behaviors or outcomes (Analogy Detection, Performance Degradation)
  • Self-diagnosis:  Leverages Diagnostic Analytics to identify the variables and metrics that might be impacting performance, and Predictive Analytics to predict what is likely to happen and when it is likely to happen
  • Self-cure:  Applies Prescriptive Analytics to create actionable insights, and Preventative Analytics to recommend user or operator corrective actions to prevent problems such as unplanned operational downtime

We have created a workshop exercise and template for my University of San Francisco class to help our students understand how to go about creating a smart product or space (see Figure 4).


Figure 4: Creating “Smart” Products or Spaces Exercise Template


Step 3: Map Advanced Analytics to Your Smart-enabling Architecture

The final step in the Getting Smart process is to create a Digital Transformation Value Map that (see Figure 5):

  • Identifies the sources of customer and market value or wealth creation
  • Re-engineer or digitalize internal processes to capture sources of value or wealth


Figure 5:  Digital Transformation Value Map


Organizations then want to identify where and how to integrate the customer, product, service and operational insights teased out of the organization’s data sources to re-engineer, or digitalize, the organization’s key business and operational processes.

See the following blogs for an introduction into the Digital Transformation Value Map:

I wanted to include a case study in this blog, but my advisors said that at 6 pages, this blog was already too long.  So that case study will have to wait until my next blog, and heck, that even gives me a chance to assign homework then!


3 Stages of Smart Summary

Organizations are facing a business model disruption like they have never experienced before, fueled by rapid advances in sensor technologies, an out of control avalanche of sensor data and the rapid democratization of advanced machine learning, deep learning and artificial intelligence capabilities.  These are truly “weapons of business model mass destruction”.

Unfortunately, organization’s IOT strategy looks like a giant game of ‘Twister’ with random, uncoordinated investments in architecture, technology, data, analytics and governance (see the blog “Avoiding the IOT ‘Twister’ Business Strategy” for more on this giant game of IoT ‘Twister’).‬‬‬


To avoid the IoT ‘Twister’ game and avoid becoming a victim of these “weapons of business model mass destruction”, one needs a coherent, coordinated plan for identifying the sources of customer and market value creation and capturing those sources of value.  And more and more, those sources of customer and market value creation will be delivered via smart product and spaces that leverage these IoT and advanced analytic capabilities to create products and environments that self-monitor, self-diagnose, self-cure and continuously learn across every step in the process.

[1] For purposes of my papers and workshops, I define “use cases” as a cluster of decisions around a common subject area such as improving customer retention, reducing hospital readmissions or reducing unplanned operational downtime.


Sign Up