8 IoT History: Adoption and Cost

8.1 Start With the Decision

A useful device can stay niche until cost, trust, and supporting networks cross a threshold. Adoption curves expose why technical merit alone does not set the date.

8.2 Route Overview

This is part 2 of 3. Review IoT History: Paradigm Evidence for the preceding evidence.

8.3 Learning Objectives

• Explain paradigm blindness with adoption and cost-curve evidence.
• Use an S-curve to compare early, rapid, and mature adoption.

8.4 Chapter Roadmap

• The Anatomy of Paradigm Blindness
• Checkpoint: Blindness Mechanisms
• Historical Lesson Pitfalls
• Innovator’s Dilemma in IoT
• The IoT Adoption S-Curve
• Interactive: Technology Adoption S-Curve
• Today’s IoT Questions
• Cost Curve Calculator
• Checkpoint: Cost Trajectory
• Historical Context: Key Takeaways
• Smart Watch Journey
• Learning from History

8.5 The Anatomy of Paradigm Blindness

Understanding why experts consistently fail at predicting paradigm shifts reveals five cognitive mechanisms:

1. Anchoring to Existing Behavior

Forecasters assume people will continue behaving as they currently do. McKinsey asked “Who among current telephone users would pay $4,000 for a worse phone?” instead of asking “What would 100 million NEW users do with portable communication?”

2. Linear Extrapolation of Exponential Change

Technology costs drop exponentially (Moore’s Law), but human minds think linearly. A $4,000 phone in 1983 became a $200 phone by 1998 and a $50 phone by 2005. Each price point unlocked an entirely new market segment.

3. Measuring New Technology by Old Metrics

Sir William Preece measured the telephone against the telegraph — speed of message delivery. He didn’t measure what the telephone uniquely enabled: real-time conversation, emotional connection, immediate coordination. Similarly, IoT critics measure a “smart light bulb” against a regular light bulb’s ability to produce light, missing everything else it enables.

4. Ignoring Second-Order Effects

Mobile phones didn’t just enable mobile calling. They enabled SMS (not planned), which enabled mobile internet (not planned), which enabled app stores (not planned), which enabled ride-sharing, food delivery, mobile banking, and social media — none of which were imagined in 1983.

The revenue shift is a useful warning for IoT forecasts. Voice was the obvious paid service, but tiny text payloads could be priced, bundled, broadcast to many recipients, and later replaced or extended by Internet-native chat, feeds, video, and streaming services. Once phones became software platforms, value moved from the carrier’s voice minute to application ecosystems, operating systems, developer tools, content libraries, and user data. IoT platforms can follow the same pattern: the first connected feature may not be where the durable value or risk finally sits.

5. Survivorship Bias in Expert Selection

The experts consulted are always those who succeeded in the current paradigm. Their success makes them the least likely to see the next paradigm clearly, because they have the most to lose from it.

8.6 Historical Lesson Pitfalls

Learning from history is essential, but misapplying these lessons can be just as dangerous as ignoring them. Watch out for these traps:

Pitfall 1: “Everything is the next telephone” fallacy. Not every new technology is a paradigm shift. Some IoT products genuinely are solutions looking for a problem. History shows that paradigm shifts change fundamental human behavior — if a proposed IoT application does not enable a new behavior or solve a previously impossible problem, skepticism may be warranted.

Pitfall 2: Confusing technological possibility with market viability. Just because something can be connected does not mean it should be. A connected toothbrush that tracks brushing habits has technological merit, but the market may remain niche if the data it generates does not lead to meaningful health outcomes or behavior changes. Always ask: “What decision does this data enable that was not possible before?”

Pitfall 3: Ignoring the “hype cycle” timing problem. Even technologies that eventually succeed often go through a painful “trough of disillusionment” (Gartner’s term). Early IoT adopters in 2014-2016 faced real failures — unreliable connectivity, no interoperability standards, and poor security. Acknowledging these real challenges is not paradigm blindness; it is prudent engineering.

Pitfall 4: Assuming cost curves will solve everything. While costs do fall exponentially over time, some IoT applications face barriers that are not primarily about cost — regulatory approval, privacy concerns, infrastructure requirements, and user trust can delay adoption regardless of how cheap sensors become.

Pitfall 5: Overweighting individual anecdotes. The fact that one expert was wrong about telephones does not mean every expert dismissing a specific IoT application is wrong. Evaluate each case on its own merits using the five cognitive mechanisms above, rather than simply pointing to historical examples as proof that all skeptics are wrong.

8.7 Innovator’s Dilemma in IoT

Clayton Christensen’s “Innovator’s Dilemma” (1997) explains why successful companies fail to adopt disruptive technologies. His framework is directly applicable to IoT adoption challenges:

1. Expertise Becomes a Liability

• AT&T’s deep knowledge of landline infrastructure made wireless seem inferior
• Telecom engineers optimized for voice quality, not mobility
• Their expertise in the old paradigm blinded them to the new one
• IoT parallel: Manufacturing companies optimized for product reliability may dismiss sensor data as “unnecessary complexity”

2. Customers Don’t Ask for Disruption

• In 1983, no AT&T customer was asking for a mobile phone
• Customers rarely ask for paradigm-shifting products — they ask for better versions of what they already have
• “Faster horses, not automobiles” (attributed to Henry Ford)
• IoT parallel: Pump customers ask for more reliable pumps, not sensor-equipped pumps — until a competitor offers predictive maintenance

3. The Math Doesn’t Work (Initially)

• Early mobile phones: $4,000, poor quality, 30-minute battery
• Early IoT sensors: expensive, unreliable, no clear ROI
• Incumbents correctly calculate that the new technology is inferior — for existing use cases
• IoT parallel: A $50 sensor on a $500 pump seems like a 10% cost increase for uncertain benefit — until the sensor prevents a $50,000 production shutdown

4. New Use Cases Emerge Unexpectedly

• Mobile phones enabled SMS (unexpected killer app)
• Smartphones enabled ride-sharing, social media, mobile payments
• IoT is enabling predictive maintenance, precision agriculture, remote healthcare
• IoT parallel: Smart meters were deployed for billing accuracy, then became grid optimization tools, then enabled demand-response programs worth billions

The Lesson for IoT Professionals:

When evaluating IoT applications, ask not “Does this solve existing problems better?” but rather “What new problems can this solve that were previously impossible?”

The connected light bulb seems silly when compared to a regular light bulb. It becomes revolutionary when it enables:

• Automated circadian lighting that improves sleep quality by 23% (Harvard Medical School study)
• Occupancy-based energy savings of 30-60% across commercial buildings
• Emergency lighting that guides evacuation routes dynamically
• Health monitoring through light usage patterns for elderly care
• Li-Fi data communication at speeds up to 224 Gbps

8.8 The IoT Adoption S-Curve

Technology adoption follows a predictable S-curve pattern, but the timing and steepness of the curve are consistently underestimated. Understanding where IoT sits on this curve helps frame both opportunities and risks:

Use Figure 8.1 to prepare the decision in the iot adoption s-curve. The diagram names The IoT Adoption S-Curve and Segments mature at different speeds as standards, the two anchors needed to assess iot segments sit at different points on the adoption curve; integration, policy, and trust can slow even cheap technologies.

Within the diagram, The IoT Adoption S-Curve opens Figure 8.1; Segments mature at different speeds as standards provides the counterpoint, and and trust advance unevenly closes the inspection. This reading constrains iot segments sit at different points on the adoption curve; integration, policy, and trust can slow even cheap technologies and supplies the visual evidence for the iot adoption s-curve.

Where different IoT segments sit today (2026):

8.9 Interactive: Technology Adoption S-Curve

Explore how technologies move through adoption phases. Adjust the parameters to see how timing and steepness affect market penetration.

phaseColor = phase === "Innovators" ? colors.purple :
phase === "Early Adopters" ? colors.blue :
phase === "Early Majority" ? colors.teal :
phase === "Late Majority" ? colors.orange : colors.red

Plot.plot({
width: typeof width === "number" ? Math.min(640, width) : 640,
height: 400,
marginLeft: 60,
marginBottom: 50,
x: {
label: "Years since introduction →",
domain: [0, 30],
grid: true
},
y: {
label: "↑ Market penetration (%)",
domain: [0, 100],
grid: true
},
marks: [
// S-curve line
Plot.line(curveData, {
x: "year",
y: "adoption",
stroke: colors.navy,
strokeWidth: 3
}),
// Current position marker
Plot.dot([{year: yearsSinceIntro, adoption: currentAdoption}], {
x: "year",
y: "adoption",
fill: phaseColor,
r: 8,
stroke: colors.navy,
strokeWidth: 2
}),
// Phase regions (background)
Plot.rect([
{x1: 0, x2: 30, y1: 0, y2: 2.5, label: "Innovators"},
{x1: 0, x2: 30, y1: 2.5, y2: 16, label: "Early Adopters"},
{x1: 0, x2: 30, y1: 16, y2: 50, label: "Early Majority"},
{x1: 0, x2: 30, y1: 50, y2: 84, label: "Late Majority"},
{x1: 0, x2: 30, y1: 84, y2: 100, label: "Laggards"}
], {
x1: "x1",
x2: "x2",
y1: "y1",
y2: "y2",
fill: "label",
fillOpacity: 0.05
})
]
})

IoT Examples:

• Industrial IoT: Years 10-12, adoption ~60% (Late Majority)
• Smart Home: Years 8-10, adoption ~35% (Early Majority)
• Smart Agriculture: Years 4-6, adoption ~12% (Early Adopters)

8.10 Today’s IoT Questions

Just as “Why walk with a phone?” seemed reasonable in 1983, today’s skeptics ask:

• “Why does a refrigerator need Wi-Fi?” —> Automated grocery ordering, food waste reduction (saves 30% of household food waste), energy optimization, recall notifications, dietary tracking
• “Why connect a light bulb?” —> Circadian health, security presence simulation, energy savings (30-60%), accessibility for disabled users, Li-Fi communication
• “Why put sensors in concrete?” —> Structural health monitoring saves $500K+ per bridge annually, predictive maintenance prevents catastrophic failures, carbon curing optimization
• “Why track cows with GPS?” —> Precision grazing increases yield 15-20%, health monitoring detects illness 48 hours early, theft prevention, optimal breeding timing

Pattern Recognition:

The IoT applications that seem frivolous today may become essential infrastructure tomorrow. History teaches us that:

1. Connectivity changes behavior in ways we cannot predict
2. New use cases emerge that the technology’s inventors never imagined
3. The “silly” applications often lead to the serious ones (gaming —> graphics cards —> AI training)
4. Established players who dismiss new paradigms often become disrupted by them
5. Cost curves are exponential — what costs $100 today will cost $1 in 10 years

For IoT Students and Practitioners:

When you encounter an IoT application that seems pointless, pause and apply this framework:

• What new behaviors might this enable?
• What data could this generate that doesn’t exist today?
• Who might benefit in ways the current market doesn’t serve?
• What happens when this becomes 10x cheaper and 10x smaller?
• What second-order effects might emerge from widespread adoption?

The next “walking around with a phone” moment is happening right now in IoT. The question is: can you see it?

8.11 Cost Curve Calculator

Moore’s Law and manufacturing scale drive exponential cost reductions. See how “expensive today” becomes “trivially cheap tomorrow.”

Plot.plot({
width: typeof width === "number" ? Math.min(640, width) : 640,
height: 350,
marginLeft: 60,
marginBottom: 50,
x: {
label: "Years from now →",
domain: [0, 15],
grid: true
},
y: {
label: "↑ Cost ($)",
type: "log",
grid: true,
tickFormat: d => `$${d.toFixed(0)}`
},
marks: [
Plot.line(projectionData, {
x: "year",
y: "cost",
stroke: colors.navy,
strokeWidth: 3
}),
Plot.dot([{year: 0, cost: initialCost}], {
x: "year",
y: "cost",
fill: colors.teal,
r: 6
}),
Plot.dot([{year: yearsForward, cost: futureCost}], {
x: "year",
y: "cost",
fill: colors.orange,
r: 6
}),
Plot.ruleY([initialCost], {
stroke: colors.teal,
strokeDasharray: "4,4",
strokeOpacity: 0.5
}),
Plot.ruleY([futureCost], {
stroke: colors.orange,
strokeDasharray: "4,4",
strokeOpacity: 0.5
})
]
})

html`<div style="background: ${colors.navy}; color: white; padding: 20px; border-radius: 8px; margin-top: 20px;">
<div style="display: grid; grid-template-columns: repeat(auto-fit, minmax(135px, 1fr)); gap: 12px;">
<div style="min-width: 0; background: rgba(22,160,133,0.3); padding: 15px; border-radius: 6px; border: 2px solid ${colors.teal};">
<div style="font-size: 0.85em; opacity: 0.9;">Today</div>
<div style="font-size: clamp(1.2rem, 6vw, 1.8rem); font-weight: bold; margin: 5px 0; overflow-wrap: anywhere;">$${initialCost.toFixed(0)}</div>
</div>
<div style="min-width: 0; background: rgba(230,126,34,0.3); padding: 15px; border-radius: 6px; border: 2px solid ${colors.orange};">
<div style="font-size: 0.85em; opacity: 0.9;">In ${yearsForward} years</div>
<div style="font-size: clamp(1.2rem, 6vw, 1.8rem); font-weight: bold; margin: 5px 0; overflow-wrap: anywhere;">$${futureCost.toFixed(2)}</div>
</div>
<div style="min-width: 0; background: rgba(231,76,60,0.3); padding: 15px; border-radius: 6px; border: 2px solid ${colors.red};">
<div style="font-size: 0.85em; opacity: 0.9;">Cost Reduction</div>
<div style="font-size: clamp(1.2rem, 6vw, 1.8rem); font-weight: bold; margin: 5px 0; overflow-wrap: anywhere;">${totalReduction}%</div>
<div style="font-size: 0.85em; opacity: 0.8;">(${costRatio}x cheaper)</div>
</div>
</div>
<div style="margin-top: 15px; padding: 12px; background: rgba(255,255,255,0.1); border-radius: 4px; font-size: 0.9em;">
<strong>Business Impact:</strong> 
${costRatio > 10 ? `A ${costRatio}x cost reduction unlocks entirely new markets. Applications that seem economically absurd today become profitable.` : ''}
${costRatio >= 5 && costRatio <= 10 ? `A ${costRatio}x cost reduction makes previously premium features accessible to mass markets.` : ''}
${costRatio < 5 ? `Cost improvements of ${costRatio}x expand existing markets but may not create paradigm shifts.` : ''}
</div>
</div>`

Real IoT Examples:

• BLE chips: $8 (2010) → $0.25 (2020) → $0.05 (2026) = 160x reduction
• LoRaWAN modules: $25 (2015) → $3 (2026) = 8x reduction
• Cellular IoT: $50 (2018) → $2 (2026) = 25x reduction

Each 10x cost reduction creates a new tier of viable applications.

8.12 Historical Context: Key Takeaways

8.13 Smart Watch Journey

The smart watch story perfectly illustrates how paradigm blindness works — and how it eventually gets overcome.

Phase 1: Dismissal (2013-2014)

When the first Android Wear and Samsung Galaxy Gear watches launched, industry experts declared:

• “Phones already tell time” (evaluating by old paradigm)
• “Battery life is terrible” (measuring by watch standards)
• “The screen is too small to be useful” (comparing to phone screens)

Phase 2: Apple Watch Launch and Skepticism (2015)

Even after Apple entered the market, critics focused on what smart watches did worse than existing products rather than what they uniquely enabled. Swiss watch executives declared Apple Watch would not affect their market.

Phase 3: The Unexpected Killer App (2018-2020)

The breakthrough wasn’t telling time, notifications, or even fitness tracking. It was health monitoring:

• Apple Watch detected atrial fibrillation, saving lives
• Fall detection automatically called emergency services for elderly users
• ECG capability received FDA clearance (first for a consumer device)

None of these use cases were in the original product pitch. They emerged from the combination of sensors + connectivity + processing that only a smart watch on a wrist could provide.

Phase 4: Essential Health Infrastructure (2022-2026)

By 2026, smart watches have become medical devices. Insurance companies offer discounts for wearers. Hospitals integrate smart watch data into patient records. The “silly watch that tells time worse than a Rolex” became a life-saving health monitor.

The IoT Lesson: The value of IoT devices rarely comes from doing existing things better. It comes from enabling entirely new capabilities that were impossible before connectivity.

8.14 Learning from History

Scenario: Your company manufactures traditional industrial pumps. A junior engineer proposes adding IoT sensors to monitor vibration, temperature, and flow rate. The VP of Sales dismisses the idea: “Our customers want reliable pumps, not gadgets. They’ve never asked for this.”

Questions to Consider:

1. Which historical pattern does the VP’s response mirror?

   • Answer: This mirrors both “We have messenger boys” (evaluating new technology by old paradigm standards) and “No customer asked for a mobile phone” (customers don’t ask for paradigm shifts). The VP is anchored to existing customer behavior.

2. What new use cases might emerge that aren’t obvious today?

   • Answer: Predictive maintenance (pump signals failure before it happens), usage-based billing (pay per gallon pumped), performance optimization (adjust pump settings based on conditions), fleet management (monitor hundreds of pumps remotely), warranty validation (prove operating conditions were within spec), energy optimization (pumps account for 20% of industrial electricity).

3. What would happen if a competitor added these sensors first?

   • Answer: They could offer predictive maintenance contracts, reduce customer downtime by 25-40%, build data moats that enable continuous improvement, and potentially shift from selling pumps to selling “pumping-as-a-service” — a recurring revenue model worth 3-5x the pump sale price.

4. How might you reframe the proposal to address the VP’s concerns?

   • Answer: Frame IoT not as a “gadget” but as a reliability enhancement — the sensors don’t replace pump quality, they protect the customer’s investment by predicting failures and optimizing performance. Start with a pilot program to generate data on actual benefits. Emphasize competitive threat: “If we don’t offer this, our competitors will.”

The History Lesson Applied: AT&T’s landline expertise made them dismiss mobile. Your pump expertise could make you dismiss IoT. The question isn’t whether your current customers are asking for IoT — it’s whether your future customers (or your competitors’ customers) will expect it.

8.15 Continue to the Next Part

Carry this evidence into IoT History: SHIFT and Resistance, which begins with Checkpoint: Reframing Resistance.