Chapters

9 IoT History: SHIFT and Resistance

applications
iot
history
Listen
Uses your device's voice. Tap ▶ beside any paragraph to hear just that one.
  • Podcast audio coming soon
  • Character narration audio coming soon
Lecture
Video lecture coming soon. The slides are the lecture for now.
Ask AI
Pick a prompt. We copy it for you and open an AI service; paste it there. Nothing is sent to IoTClass.

A pump operator hears a proposal for another sensor and asks why the existing maintenance schedule is not enough. That resistance may expose a weak proposal rather than a lack of imagination. This chapter uses SHIFT, a five-question proposal framework, to distinguish a useful objection from a limiting assumption and turn an IoT promise into a testable decision.

The manufacturing company’s VP has a related objection: “Our customers have never asked for this.” The proposed vibration and temperature sensors would support cloud analytics and predictive-maintenance alerts, but the proposal has not yet explained what customers gain. Added cost and complexity are visible; a better maintenance outcome remains a claim. Both the operator and the VP have reasons to ask for evidence.

This is part 3 of 3; IoT History: Adoption and Cost supplies the preceding evidence. The applications module index places this decision alongside other application cases. Here, the problem is deciding whether resistance protects a sound operating practice or hides a new opportunity. We will identify the objection, apply SHIFT to the pump scenario, and bound a trial that can return an unfavourable result.

KEY CONCEPTS

  • Resistance

    An objection can expose a constraint or an assumption.

  • SHIFT questions

    Explore what changes after the first use succeeds.

  • Adoption evidence

    Behavior and incentives shape whether value arrives.

  • Bounded trial

    Name an outcome and evidence that could reject it.

9.1 Identify What the Objection Protects

Paradigm blindness means evaluating a new technology through an existing framework that misses what the change enables. It draws on cognitive biases and limits of expertise, and can lead to forecast errors and missed opportunities. Naming a bias does not establish that the proposed technology deserves investment. First ask what evidence would make the objection reasonable.

Separate technical, economic, social, and cognitive resistance. Can the pump’s signals support a useful warning? Does the avoided loss justify installation and operation? Will maintenance staff change their work? Is leadership treating the current workflow as the only possible one? These questions distinguish an operational constraint from an assumption that should be tested. A technician who cannot visit a pump in time has identified a response problem, even if the sensor detects a change correctly.

Five mechanisms help diagnose cognitive resistance. Anchoring to existing behavior assumes people will keep doing what they do today. Linear extrapolation extends present trends in a straight line and can miss exponential change. Old metrics judge a new offer only by the incumbent product’s strengths. Ignoring second-order effects overlooks uses that follow the first success. Survivorship bias selects experts who succeeded under the current model while missing people who see reasons to change it.

The VP’s “customers never asked” objection may anchor to current requests. The operator’s question about scheduled maintenance may instead reveal that no improvement has been demonstrated. User-centered design and design thinking help investigate what people need without treating either statement as the final answer. Requirements analysis then turns a desired outcome into something the team can observe.

The Innovator’s Dilemma, described in Clayton Christensen’s original framework, explains an incentive conflict: current customers, revenue streams, margins, and expertise reward the existing business, while a new category may initially look inferior on its metrics. Business strategy and disruption theory help explain this organizational resistance; lack of engineering talent, a legal prohibition, or trial price alone does not explain the dilemma. It is a risk to investigate, not proof that every disruption succeeds.

Adoption adds another uncertainty. An S-curve describes diffusion that begins slowly, accelerates, and eventually plateaus. Technology-adoption patterns connect market dynamics to investment timing and scaling. The source chapter characterizes IIoT and wearable health as accelerating, and smart agriculture and smart cities as moving from skepticism toward early adoption. Treat those as segment-specific characterizations requiring dated market evidence, rather than a universal current ranking. Use Market Analysis to examine that evidence; the Gartner Hype Cycle offers a separate lens on technology expectations and adoption phases.

These mechanisms can overlap, so identify the specific reasoning rather than attaching every label to the objection. Judging sensors only by their purchase price uses a different frame from asking whether a technician can respond. Likewise, missing a later spare-parts service is different from assuming quarterly inspections must always remain the maintenance model. The distinction matters because the team needs different evidence for each question: an operating comparison, a response assessment, or a customer-value test. Change management begins with understanding which part of the proposed change people are resisting.

Historical parallels can widen the questions without deciding the answer. The source invokes AT&T, mobile phones in 1983, and customers who had not requested a new category; its McKinsey link is a general insights resource rather than a specific forecast account. A numerical forecast comparison would need an identifiable account with matching geography and subscriber definitions. The lesson we can use here is narrower: today’s requests may miss tomorrow’s uses. We still need a method for exploring those uses without inventing demand.

9.2 Learning Objectives

  • Recognize technical, economic, social, and cognitive resistance.
  • Apply the SHIFT proposal framework to an IoT change.

9.3 Apply SHIFT to the Pump Proposal

SHIFT asks about Second-order effects, Human behavior, Impossible becomes possible, Forecast anchoring, and Technology cost. It connects critical thinking and proposal framing to requirements analysis and financial evaluation. Work through the questions before turning them into a sales pitch; each answer should expose an assumption the trial can challenge.

S — What happens after the first use succeeds? Second-order effects are applications and behaviors that emerge after an initial use succeeds. Systems thinking and emergent behavior connect them to new business models and unexpected applications. For the fictional pump case, suppose predictive maintenance might reduce downtime by 30%. Does recovered production capacity delay purchases, or enable expansion at an existing, brownfield site that later creates demand for more pumps? Neither outcome follows automatically. Better spare-parts planning is another candidate: an earlier warning might let a technician combine visits and avoid a rushed shipment.

Other examples show the same chain of reasoning. Smart meters can enable grid optimization and then demand-response programs. The chapter points to SMS, ride-sharing, and smart watch health monitoring as uses beyond the initial product pitch; they illustrate why the first use need not exhaust a technology’s value. They do not establish that the most valuable future IoT application can already be named. Edge Computing and data analytics offer related technical contexts for examining what new observations make possible.

H — How might people behave differently? In the pump scenario, customers currently schedule maintenance quarterly and hold spare parts “just in case.” A move to condition-based maintenance could change procurement to ordering parts when needed. Just-in-time parts delivery might then support a subscription service. These are behavior and revenue hypotheses, not consequences guaranteed by a sensor. Similarly, wearables can support continuous health awareness and preventive medicine, but the change depends on how people respond to the information.

I — What could not be done before? The pump proposal seeks visibility into health between quarterly inspections. Manual external inspection alone may not reveal bearing degradation; validated vibration and temperature signals can add warning evidence. The fictional business case assumes failures cost $50K–$500K per hour and hopes for 2–3 weeks of warning so maintenance can occur during planned shutdowns. Those figures are inputs to validate, not measured performance. Embedded concrete sensors supporting real-time structural-health monitoring illustrate the same question about a previously unavailable observation.

F — Are we anchoring to current behavior? “Customers don’t ask for sensors” describes requests under the current offer. Ask whether customers would value an improved outcome and what would count as evidence of demand. The historical mobile-phone analogy prompts that question; it cannot answer it. A competitor may introduce a new category first, but the pump team must examine customer behavior rather than assume that competitive pressure validates its own proposal. The opposite error is to assume every customer wants a subscription. Reframe both claims around a named outcome and test what the buyer values. A small site with spare capacity may value fewer visits more than a tiny increase in uptime.

T — What changes if technology becomes 10 times cheaper? Use $50 per sensor today and $5 in 5 years as a scenario, not a price forecast. At the lower price, sensing more components might become economical. Starting now might build integration expertise, data, and algorithm refinement over those 5 years. The proposed data moat and customer lock-in are business hypotheses; a head start does not establish an advantage competitors cannot match. Cost trajectories should change the questions asked about deployment, not remove the need to test operating value.

The IoT Introduction provides the Three Ingredients and Five Verbs framework for describing the system. Device Evolution distinguishes embedded, connected, and IoT products. Those descriptions help establish what changes technically; SHIFT asks what that change could mean for customers. The next task is to translate those possibilities into a proposal with explicit financial assumptions.

9.4 Make the Outcome and Trial Reviewable

The original pitch was “add vibration and temperature sensors.” A stronger pitch names the customer’s loss, the proposed response, and the evidence needed before expansion. In this fictional pump business case, annual unplanned-downtime costs of $2M–$20M are assumptions to investigate. The proposed offer has three possible revenue streams, each with a different obligation to the customer.

A sensor-equipped product might carry a 15% premium, with a proposed 3–6-month customer payback. Subscription analytics might charge $50 per month per pump for dashboards and failure alerts, equivalent to $600 per year. An outcome-based offer might charge $500 per month for “uptime-as-a-service,” proposing 99.5% availability. Pricing, margins, payback, availability, and willingness to pay remain fictional assumptions pending customer trials. An availability promise requires evidence about the delivered outcome; the presence of alerts alone cannot support it. Business Models and ROI Calculation help examine how the revenue streams relate to cost and responsibility.

Competitive claims deserve the same discipline. The source names Siemens and GE as industrial IoT competitors and Tesla’s over-the-air updates as a category-framing analogy. These are prompts for competitive investigation, not evidence that this pump offer will win. Its illustrative survey figure of 67% willing to pay is fictional, not an observed survey result. A proposed 5-year data lead also needs scrutiny: collecting data is different from showing that it improves a customer’s decision.

The fictional rollout story includes a VP approving a $500K pilot on 200 pumps at one customer site, a claimed 28% downtime reduction, 3 upsell leads, and full product-line approval 9 months later. Keep every one of those as a scenario assumption or prospective milestone. None is a result achieved by this chapter’s technology. Clear framing lets a reviewer distinguish a proposed commercial path from the operational trial that must justify it.

For a smaller, falsifiable trial, use the illustrative fleet of 20 pumps. Suppose the baseline is 40 hours of unplanned downtime over a fixed observation window. The proposal aims to reduce that total to 30 hours in an equally long trial with comparable operating load. The predicted reduction is 40 hours minus 30 hours = 10 hours. Relative to the baseline, 10 divided by 40 gives 25%. This is a trial target, not a result already achieved by the technology; it is separate from the larger business-case assumptions above.

Now test the comparison itself. If the trial records 30 hours of downtime but pump operating hours fall by half, the raw total meets the target without demonstrating reduced failure exposure. Compare downtime against operating time before crediting the new approach. If false alarms create extra planned stops, include those stops when judging the operational outcome, even if the original proposal counted only unplanned losses.

The second-order spare-parts claim needs its own evidence. Record whether earlier warnings actually let a technician combine visits and avoid a rushed shipment. If nobody can reach the pump in time, the warning has exposed a real response constraint. Name who acts when the signal arrives. Count useful responses as well as warnings, and state the assumptions and the go, revise, or stop rule before the trial. If an early warning lets maintenance order a seal before a shutdown, the useful outcome reaches beyond the first alarm. Technicians may inspect an asset only when a warning arrives; missed warnings then matter more. The original inspection process cannot be removed merely because a live chart looks convincing.

The 25% target also helps keep the financial story honest. Ten fewer hours matter only in relation to the baseline, operating load, and costs included in the comparison. The assumed $50K–$500K hourly loss range is not a substitute for measuring the customer’s actual exposure. Nor does the $600 annual subscription revenue per pump establish the customer’s payback or the supplier’s margin. Keep the operational claim, customer benefit, and proposed revenue distinct while reviewing whether they support one another.

The VP can now evaluate a choice rather than a gadget. The proposal says which loss it aims to reduce, which maintenance response could produce that reduction, and which assumptions remain unresolved. A useful result might justify continuing, revising the offer, or stopping it. That preserves the purpose of the operator’s original objection: the existing maintenance schedule deserves comparison with the proposed approach, not dismissal merely because a new signal is available.

That gives the reasoning a clear sequence: separate the initial technical capability-and-cost forecast from adoption behavior, complements, regulation, and second-order uses; then reframe the outcome and run a bounded pilot. The revised proposal can quantify a financial opportunity while keeping an unfavourable result possible. Reframing should improve the decision rather than make the proposal impossible to reject.

Check knowledge

Reframing resistance: distinguish incentives and biases, match concepts, order the reasoning, and label the forecast-to-pilot path.

Check knowledge

The separate applied exercise takes this reasoning into a dismissed proposal from your own environment. It includes the original rental-equipment example and reflection questions; its fleet, utilization, revenue, savings, and cost figures are hypothetical exercise inputs to measure in a real pilot.

Practice

Detect Paradigm Blindness: complete the 45-minute intermediate SHIFT exercise and compare technology and outcome framing.

Apply SHIFT

Try it

Code Challenge: complete the original Python smart-home rule exercise for sensor values, conditions, and actions.

Open code challenge

Summary

Resistance can reveal technical limits, economic costs, social constraints, or cognitive anchoring. Paradigm blindness and the Innovator’s Dilemma explain ways a useful opportunity can be missed; neither proves that a particular proposal will succeed. Adoption patterns and historical parallels help frame questions that still require evidence.

SHIFT explores second-order effects, human behavior, new capabilities, forecast anchoring, and technology cost. In the pump case, those questions connect sensors to maintenance responses, spare-parts planning, and possible revenue streams. The trial then narrows the claims: compare operating exposure, include false-alarm costs, and distinguish fictional pricing and rollout assumptions from measured outcomes.

Reframe the outcome, then make it possible to reject the promise. A useful IoT proposal names what could change, who can act, and what evidence would justify continuing.

Next, IoT Systems Evolution examines computing evolution, Moore’s Law, and the technical foundations enabling IoT.

Hi, I’m Ada. What do you need?

Find help

Let’s find what you need

Find a lesson or return to your module guide.

Give feedback

Help improve this chapter

Tell us what helped or what needs fixing.

Tips

Try a small next step

A few ways to get more from this chapter.

Ask AI

Continue the conversation

Take the conversation further with your preferred assistant.

AI help is available in supported modules when enabled in Settings.

No live person answers on independent study. Feedback does not promise a personal reply.

For welfare or safety concerns, follow your school’s procedures outside IoTClass.