Digital transformation after the transformation era
Why the next digital agenda is less about isolated programs and more about architecture, platforms, governance and measurable enterprise value.
Read article
2 min read
Author: WalsonParker
IoT creates value when connected assets change an decision
Connectivity is not an outcome. An IoT capability matters when data from equipment, products or environments lets the organisation detect, decide or act differently: prevent failure, verify condition, optimise flow or create a service. Start with the decision, delay, uncertainty and cost. Sensors without a defined response often create telemetry that is expensive to store and easy to ignore.
Design the information chain end to end. Specify what is measured, required accuracy, sampling rate, asset identity, time synchronisation and the action triggered by each threshold or model. Edge can support control or filtering; central platforms can support fleet learning. Missing, delayed and implausible readings need explicit states so absence is not mistaken for normal operation.
Cybersecurity is a product-lifecycle obligation. NIST IR 8259 Revision 1, finalised in April 2026, recommends foundational activities that make IoT products securable and give customers security information. Device identity, configuration, data protection, restricted interfaces, secure updates, vulnerability handling and support duration must be designed before deployment, not added after compromise.
Economics include hardware, connectivity, installation, calibration, platform, field service, security, data operations and retirement. Pilot where value can be measured against a baseline and test harsh physical and network conditions. Cheap sensors become costly when batteries, false alarms or truck rolls scale. Ownership must span technology and the operating process that responds.
Track decision lead time, detection quality, avoided downtime, service response, data completeness, device health, update success and cost per connected asset. Retire signals that do not support action. IoT adoption becomes strategic when physical context closes an operational loop and improves an outcome�not when more objects appear on a connectivity dashboard.
Related macro
Digital
Connect digital strategy, technology, products, operations and customer experience to enterprise priorities.
Discover the macroEditorial overview
Articles
The platformization of the enterprise
How modular platforms, APIs and modernized applications can reduce structural complexity while accelerating digital products and AI adoption.
Read articleFocus
Cloud security depends on how responsibility is distributed across the stack
Exposure emerges through configuration, identity, workloads, networks and unclear boundaries between teams and providers.
Zero trust replaces assumed access with continuous evidence of legitimate need
The model shifts control toward identity, device posture, context and explicit authorization across environments.
Strategic challenges
When does paid social create demand, and when does it merely rent attention?
The challenge is separating genuine incremental acquisition from platform-attributed activity with weak downstream economics.
Which digital channels genuinely matter for the customers the business needs?
The challenge is resisting channel proliferation and concentrating activity where audience behavior and economics support it.
POV
Confidential information is not trustworthy information if its integrity is uncertain
Digital trust must address whether information is authentic and reliable, not merely whether access was restricted.
If every initiative is digital, there is probably no digital strategy
Strategy requires concentration and trade-offs, not a broad inventory of technology-enabled activity.
Strategic impact
A use-case-led approach clarifies where immersive technology can support work
Assessing interaction needs, context and adoption barriers helps identify applications where spatial computing may improve performance.
Reusable platform capabilities reduce repeated infrastructure and data work
Standard services can improve consistency and delivery speed when consumption patterns and ownership are well defined.
What we observe
Commerce builds often optimize the storefront while neglecting operational integration
A fast checkout cannot compensate for inaccurate stock, broken fulfilment flows or inconsistent pricing behind the interface.
Platform programs often centralize technology without creating real reuse
A common stack does not become a platform when teams cannot consume services easily or must rebuild around its constraints.