You're caught in a clash between IT and operational teams on IoT security. How will you navigate the storm?

To navigate the storm, you need to first understand the needs. This is so that you would know what each team needs. You must then evaluate if the security measures would hinder the operations of the operational team or not. This is so that you would know if these strict security measures can be put in place or not when it comes to the IoT devices. You should then evaluate how much risk these devices could pose on your organization. This is so that you would know why the IT team needs that much security measures in place.

Step 1: Listen Actively and Without Biasness Needs of the IT Team: Data confidentiality and integrity. Network segmentation, access controls, and patch management. Compliance with cybersecurity standards (e.g., NIST, ISO 27001). Needs of the Operational Team: Continuous uptime and minimal disruption. Legacy system integration and safety. Real-time data access and latency-sensitive operations.

To achieve true success—whether in business, leadership, or personal growth—you must first understand the needs of those you serve. This means actively listening, asking thoughtful questions, and observing with empathy. When you take the time to uncover what people truly value and what challenges they face, you can design solutions that resonate deeply. Understanding needs builds trust, fosters loyalty, and helps you deliver meaningful impact. Remember: assumptions create gaps, but genuine understanding creates connections that last.

To manage the clash between vessel IT and operations, first understand each side’s needs. IT teams focus on safeguarding onboard networks and systems from cyber threats, often enforcing strict protocols that may slow performance or limit access. Operational crews, however, prioritise functionality, uptime, and ease of use—especially during critical operations. Bridging this gap starts with empathy: recognise that both cybersecurity and operational continuity are essential. With mutual understanding, you can implement protective measures that secure digital systems without disrupting vessel performance or safety.

Bring both IT and OT teams to the table. Clarify shared goals: safety, uptime, and security. Translate risks in terms each side understands. Propose a joint security framework that respects both uptime and cyber integrity. Be the bridge, not the barrier.

I'd bring both teams together to align on shared goals, listen to their concerns, and facilitate a solution that balances security and operational efficiency. Collaboration and clear communication are key.

Navigating a clash between IT and operational teams over IoT security requires diplomacy, technical understanding, and a shared vision. First, acknowledge the differing priorities—IT focuses on data integrity and cybersecurity, while operational teams prioritize uptime and performance. Begin by facilitating a joint discussion that reframes security as a shared responsibility, not a competing priority. Highlight how strong IoT security protects both data and operational continuity. Then, propose a collaborative risk assessment to identify vulnerabilities and agree on non-intrusive security measures that align with both teams' goals.

To navigate the clash between IT and operational teams on IoT security, I’d take a multi-pronged approach. I’d start with a controlled pilot that applies layered security to a small IoT segment, measuring performance and uptime impacts to prove viability. Simultaneously, I’d work on establishing clear security policies and SLAs that define ownership IT for security, operations for uptime to prevent future disputes. By adopting agile collaboration, both teams can co develop solutions in sprints with shared reviews, fostering transparency and trust. If tensions persist, I’d escalate with a joint executive proposal, presenting risks of inaction and pushing for top down alignment. Education would be key training operations on cybersecurity.

Listen first. Ask each side, “What breaks your day?” IT says breaches, Ops says downtime. Write both on the wall. Teach without jargon. Convert IT’s risk scores into Ops’ language: “A hacked sensor could stop Line 3 for 4 hours = £25k lost.” One conversation channel. A 15-minute weekly stand-up—no slides, just blockers and wins—keeps rumours at bay. Prototype, then scale. Secure one small line first; show latency and uptime numbers. Proof beats opinions. Blend maintenance windows. Patches ride alongside routine equipment checks—no extra shutdowns. Track two numbers, celebrate two numbers. Share a single dashboard with “% devices updated” and “days without unplanned stoppage.” Both teams see success in real time.

This clash is one of the most common and most overlooked: tensions in digital transformation. IT wants control, security, and standardization. OT needs speed, uptime, and flexibility. Both are right in their own context. The breakthrough comes when we stop treating this as a turf war and start designing systems that acknowledge both priorities. That means collaborative risk assessments, security-by-design principles that don’t cripple performance, and clear escalation paths when trade-offs are needed.

Educating teams is key to unlocking their full potential and driving lasting success. When you invest in team learning, you empower individuals with the knowledge, skills, and confidence to solve problems, innovate, and adapt to change. Education shouldn’t stop at formal training — foster a culture of continuous learning through mentorship, shared resources, and open discussions. By educating teams, you build alignment, boost morale, and create a workforce that’s ready to meet challenges and seize opportunities together. Knowledge shared is power multiplied.

Educating teams is key to unlocking their full potential and driving lasting success. When you invest in team learning, you empower individuals with the knowledge, skills, and confidence to solve problems, innovate, and adapt to change. Education shouldn’t stop at formal training — foster a culture of continuous learning through mentorship, shared resources, and open discussions. By educating teams, you build alignment, boost morale, and create a workforce that’s ready to meet challenges and seize opportunities together. Knowledge shared is power multiplied.

When IT and operations clash over IoT security, I don’t pick sides—I build bridges. First, I align both teams around a shared risk: unsecured IoT isn’t just an IT issue, it’s a business continuity threat. I facilitate a joint threat modeling session to surface concerns, then map responsibilities clearly—IT handles network controls, Ops owns device behavior. From there, we co-create security protocols that are both robust and operationally feasible. The key? Speak in impact, not blame. Collaboration beats silos—every time.

Many conflicts stem from information asymmetry. I organize training sessions or workshops to help teams understand the technical challenges and importance of IoT security, while emphasizing the importance of collaboration in solving problems.

Bridging the knowledge gap could ease tension. Translating technical terms into operational outcomes (and vice versa) may help teams better appreciate each other’s stakes.

Fostering dialogue is essential for building strong, collaborative teams and creating an inclusive environment where ideas can thrive. Open, respectful conversations encourage diverse perspectives, spark innovation, and help resolve conflicts before they escalate. When you foster dialogue, you show that every voice matters — creating a space where people feel safe to share, question, and contribute. Promote active listening, ask open-ended questions, and value feedback. In doing so, you build trust, strengthen relationships, and drive collective growth. Dialogue turns communication into connection.

It is particularly important to establish bridges of communication. I will organize cross-team meetings and design an open and safe environment where both sides can express their ideas and share their needs, while guiding the discussion to focus on problem solving.

Invite meaningful dialogue. Instead of defaulting to routine meetings, you might facilitate space for shared problem-solving. Storytelling or “what if” exercises could surface concerns without blame.

Compromise wisely by balancing your goals with the needs of others, ensuring solutions that benefit all without sacrificing core values. Wise compromise isn’t about giving in; it’s about finding common ground that drives progress and preserves relationships. It requires empathy, active listening, and clarity on what truly matters. Know where to stand firm and where flexibility can create win-win outcomes. When done thoughtfully, compromise builds trust, strengthens teamwork, and paves the way for sustainable success. Remember: smart compromise fuels collaboration, not concession.

I have learned that in conflict resolution, the customer needs are more important. If you compromise on security, the customer is affected, if you compromise of functionality, then customer experience is affected. But of this which poses a greater risk, to me it would be security because if is not managed, you open yourself to fines, law suits, data and customer loss and lastly reputational damage. This is something that the operational team should also own and not think it is only an IT risk. If it affects the whole organisation, then its a risk owned by every employee.

After fully understanding both parties' needs, I will strive to find a compromise solution that meets IT's high security requirements while taking into account the time or efficiency constraints of the operations team.

Look for principled compromises. True compromise doesn’t have to feel like surrender. Centering discussions on shared goals, like resilience or uptime, may reveal unexpected alignment.

Implementing solutions is where ideas turn into action and impact. It’s not just about having a great plan — it’s about executing it with clarity, focus, and commitment. Successful implementation requires clear roles, measurable goals, and ongoing communication to keep everyone aligned. Be ready to adapt as challenges arise, learning and adjusting along the way. When solutions are put into practice thoughtfully, they drive real change, build momentum, and inspire confidence in your team. Remember: solutions have power only when they are acted upon with purpose and persistence.

Through my experience of listening to both sides.. follow what IT states. They are technical and understand the risks involved but not implementing the proper security measures. Operations wants to ensure the budget and allocations of resources is properly managed. That doesn’t mean it’s in the best interest of the company as money isn’t everything.. remember if you have a breach in security at any level by any means, it’s going to cost you a lot more… so more often than not listen to your IT department. If you don’t they will seek an employer who will

Once a solution has been determined, I will promote joint implementation by both parties and verify the balance between security requirements and operational efficiency through active collaboration.

Pilot joint solutions. Small wins speak loudly. A shared dashboard or co-owned test run might reinforce that you’re one team solving one challenge.

In industrial design, integrating IoT into products adds value — but also increases vulnerability. A smart equipment line we worked on faced unexpected downtime due to a minor security gap in a connected control unit. The issue wasn’t poor design, but the lack of ongoing security updates post-deployment. The solution? We introduced a routine design-review checkpoint focused on IoT security — ensuring both designers and engineers reassess risks regularly. This cross-functional approach helped improve the product's resilience and trustworthiness in real-world use. Lesson: In industrial design, good form and function must now include security. IoT-connected products need ongoing vigilance as part of the design lifecycle.

Security and collaboration are long-term processes. After resolving issues, I will regularly monitor the status of IoT security and maintain ongoing communication between teams to ensure that no new conflicts arise.

Sustain the collaboration. Even when things feel aligned, continued vigilance can help. Regular check-ins or feedback rituals could keep trust intact before the next storm arrives.