Jobs to be Done (JTBD)
for Other telecommunications activities (ISIC 6190)
Shifting the focus from technical performance metrics to business outcomes is the primary way to differentiate in a market defined by parity of technical service.
What this industry needs to get done
When managing distributed IoT assets in remote field locations, I want to abstract away protocol complexity, so I can ensure seamless data telemetry without managing bespoke network integrations.
The market suffers from MD05 (Structural Intermediation) where too many layers between hardware and network cloud inhibit rapid deployment.
- Time to first data packet transmission
- Maintenance incident ticket volume per site
When a major network outage threatens mission-critical uptime, I want to guarantee resilient failover paths, so I can avoid the operational paralysis that comes with connectivity loss.
MD04 (Temporal Synchronization) constraints often mean that restoration times are too slow to avoid catastrophic business impacts.
- Mean Time to Recover (MTTR)
- Percentage of uptime during ISP outages
When reporting to regulatory bodies on data residency, I want to prove immutable transmission paths, so I can satisfy strict compliance audits without manual manual log reconciliation.
CS04 (Ethical/Regulatory Compliance) creates massive friction when current providers offer opaque routing paths.
- Audit preparation time
- Regulatory fine frequency
When presenting infrastructure capabilities to enterprise investors, I want to demonstrate structural market advantage, so I can justify premium valuation multiples for our network assets.
MD03 (Price Formation Architecture) is often transparent and well-analyzed by analysts, making this a standard expectation.
- Revenue per unit of capacity
- Net promoter score from investor group
When selecting a primary connectivity vendor, I want to feel a sense of 'black-box' security, so I can stop worrying about sophisticated cybersecurity threats infiltrating our OT environment.
CS06 (Structural Toxicity) and increasing threats make current off-the-shelf connectivity feel dangerously vulnerable.
- Number of security breaches per annum
- Internal perception of risk rating
When competing for high-value government contracts, I want to ensure my supply chain is free of labor integrity issues, so I can build a brand reputation as a responsible and ethical operator.
CS05 (Labor Integrity) is an increasing friction point for bidders when vetting complex, multi-tiered infrastructure supply chains.
- Supplier audit compliance score
- RFP win rate on ethical-weighted criteria
When calculating operational costs, I want to move to an outcome-based billing structure, so I can align my connectivity expenses directly with actual data-driven business performance.
PM01 (Unit Ambiguity) makes it difficult to transition away from legacy gigabyte-based pricing models.
- Cost of connectivity as a % of operating margin
- Variance between predicted and actual bill
When providing routine status updates to the executive leadership team, I want to confirm that connectivity SLAs were met, so I can satisfy the baseline requirement for ongoing service renewals.
MD08 (Structural Market Saturation) ensures that standard SLA reporting is a mature, commoditized feature expected by every buyer.
- Customer retention rate
- Renewal cycle time
When evaluating potential infrastructure partners, I want to ensure their network topology is future-proof, so I can signal to my stakeholders that our digital transformation roadmap will not be stalled by obsolete technology.
MD01 (Market Obsolescence) risk forces firms to constantly re-assess their tech stack compatibility.
- Technology refresh cycle frequency
- Market share of digitally-mature clients
Strategic Overview
The 'Jobs to be Done' framework is critical for transitioning 6190 providers from mere 'bandwidth suppliers' to 'outcome enablers.' Clients in this space are not buying connectivity for its own sake; they are buying the ability to monitor remote sensors, maintain operational uptime in hazardous environments, or ensure regulatory compliance in data transmission.
By reframing offerings around these functional and social jobs, providers can move away from the destructive pricing of simple throughput. This shift allows for the commoditization of generic data while highlighting the premium value of reliability, security, and integration, which are the real drivers of procurement decisions for industrial and enterprise clients.
3 strategic insights for this industry
Outcome-Based Pricing Models
Instead of charging for gigabytes, move toward subscription models based on service availability or sensor-data success rates.
Reliability as a 'Safety Job'
Many B2B clients purchase connectivity as a risk-mitigation tool; 'zero-downtime' is not just a spec, but an insurance policy for operations.
Prioritized actions for this industry
Map current service catalog to explicit customer business outcomes.
Identifies which services currently lack perceived value and which can be repositioned as premium outcomes.
From quick wins to long-term transformation
- Conduct qualitative interviews with top 10 clients to identify pain points
- Rebrand service documentation to focus on results over technical capacity
- Revise sales training to focus on outcome-based selling vs. technical specs
- Develop 'uptime guarantees' as an upsellable, premium tier
- Rebuild infrastructure management software to provide real-time outcome reporting to clients
- Shift investment toward service reliability over raw throughput expansion
- Over-complicating service offerings
- Failing to measure the correct outcome (i.e., measuring latency instead of sensor success rate)
Measuring strategic progress
| Metric | Description | Target Benchmark |
|---|---|---|
| Customer Net Promoter Score (NPS) by Outcome | Measuring satisfaction based on how well the job was completed | > 50 |
| Service Bundle Adoption Rate | Percentage of clients upgrading to outcome-linked service bundles | > 20% |
Other strategy analyses for Other telecommunications activities
Also see: Jobs to be Done (JTBD) Framework