When Technology Isn't Enough: Why Processes Become the Deciding Factor

Welcome to the latest edition of the Conntac Chronicles! 📰

This month, we take a closer look at a development that cuts across multiple areas: technology is available – but usage, service, and safety increasingly depend on processes.

Whether fiber rollout, customer service, or field operations: what matters is no longer whether something works – but how structured and traceable it is organized.

Our topics at a glance:

• 📌 Fiber: Why the critical phase begins after rollout
• 📌 Customer service: Why “best effort” is not a sustainable model
• 📌 Field service (1): Why safety must not depend on signal
• 📌 Field service (2): How TSM is changing requirements for organization and documentation

📡 Rollout completed – what comes next?

The fiber rollout is progressing – yet many providers observe a familiar pattern: usage falls short of expectations.

The reason is rarely technical. It lies in what happens afterward.

Especially in multi-dwelling units, a structural gap emerges:

• Connection available in the basement
• Usage in the apartment remains unclear
• Multiple stakeholders involved (owners, property managers, tenants)
• Lack of guidance after contract completion

The result: support becomes a substitute for missing onboarding.

Key insight: economic success is not determined during rollout – but in the phase between contract completion and actual usage.

What matters now:

• clear guidance on next steps
• understandable communication
• structured onboarding into usage

➡️ The full article shows why this phase holds the greatest leverage for take-up and service reduction.

📱 Best effort in customer service – a structural problem

Many service organizations effectively operate on a “best effort” basis – without explicitly calling it that.

This means:

• no clearly defined process steps
• unclear responsibilities
• missing status transparency
• communication depending on individual agents

From a customer perspective, it feels like:

• “What is happening right now?”
• “Who is taking care of this?”
• “What happens next?”

The result is not just frustration – but increased workload in service:

• repeated inquiries
• escalations
• duplicated work

Important clarification: the problem is not lack of effort – but lack of structure.

The solution lies in guided processes:

• clear status visibility
• defined next steps
• transparent responsibilities

Self-service plays a key role here – not as a replacement, but as a control layer for the service process.

➡️ The article explains how service can move from “best effort” to structured, predictable workflows.

🛰️ No signal, no safety? A critical misconception

In field service, safety is often tied to a technical assumption: mobile connectivity.

The issue: exactly where work happens, connectivity is often unreliable or unavailable:

• shafts
• basements
• technical rooms
• remote infrastructure sites

If safety processes depend on connectivity, this creates a structural risk.

The key is separating two layers:

• detection of an incident (must always work)
• transmission of the alert (can benefit from connectivity)

Many systems fail to distinguish between the two.

The consequence: safety only works under ideal conditions.

The correct approach:

• local logic (e.g. timers, motion detection)
• delayed alert transmission
• traceable documentation

Core statement: Safety begins where signal ends.

➡️ The article explains why offline capability is not a feature, but a fundamental principle.

🔒 TSM in field service – why processes become critical

At the same time, requirements in Technical Safety Management (TSM) are increasing.

The focus is shifting significantly:

No longer just: “Is there a safety measure?”

But: “Is the entire process traceable and documented?”

More and more, a complete operational chain is required:

• start confirmation
• status updates during the task
• completion confirmation
• in some cases, confirmation after returning home

Many organizations still rely on:

• phone calls
• Excel sheets
• manual notes

The result:

• increased coordination effort
• fragmented processes
• incomplete documentation
• growing liability risks

The key shift: safety becomes an organizational responsibility – not a technical feature.

Three elements become central:

• clear responsibilities
• automated escalation logic
• complete documentation

➡️ The article shows why these aspects are becoming decisive in audits and certifications.

Conclusion: Processes become the decisive factor

Across all topics, a clear pattern emerges:

• Fiber does not fail because of infrastructure, but because of missing guidance
• Customer service does not fail because of effort, but because of missing structure
• Field service does not fail because of technology, but because of unclear processes

The common denominator: structured and traceable workflows become the key success factor.

Final thoughts

Many of today’s challenges appear technical at first glance. In reality, they are organizational.

• How are customers guided after contract completion?
• How is service structured and made transparent?
• How is safety in field operations actually ensured?

Organizations that can clearly answer these questions create more stable processes, reduce operational effort, and improve transparency and control.

Digital solutions support this – not as an end in themselves, but as a way to reliably execute processes.

See you in the next edition 👋

Don’t want to miss future Conntac Chronicles? Subscribe to our newsletter or follow us on LinkedIn.