There is only one team – Why Collaboration Is the True Success Factor

This article is part of the series Futureproof HMIs.

In many organizations, silos still persist: design team, development team, application, PLC, service, documentation — each with its own priorities, perspectives, and workflows. The problem is not that these disciplines exist (they must), but how we organize them: as separate units that have to collaborate. This mentality creates friction, misunderstandings, and endless coordination loops.

The alternative: one HMI team. Not just a group of specialists delivering features on demand, but a long-term unit sharing responsibility for outcomes, operation, and customer value. Product decisions are made where expertise meets — not as last-minute compromises.

Cooperation is a fundamental human skill: we can work together flexibly in large groups — and that’s exactly what distinguishes successful product teams. Collaboration means more than meetings; it means shared experiences: on-site observations, pair prototyping, joint usability sessions, and debugging together in the field. These shared experiences create a common understanding of user problems and technical feasibility.

Research and practice show: the more time (“exposure hours”) team members spend in real usage contexts, the better they can identify needs and prioritize solutions. Empathy doesn’t arise from isolated interviews, but from repeated, direct exposure to real working conditions.

1. Long-lived, autonomous teams: The longer people work together, the stronger the trust. Trust is the foundation for quick, confident decisions.
2. Interdisciplinary team structure: Product managers, designers, developers, application engineers, service staff, and technical writers belong to the same team. Responsibility for outcomes is shared.
3. Practice-oriented work: Regular field visits, shadowing, and joint testing — not delegation, but participation.
4. Iterative prototyping: Small, fast experiments (MVPs) generate feedback early and reduce risks.
5. Clear definition of success: A shared vision and measurable goals — not just feature lists.
6. Roles with clear mandates: Empowered teams need decision-making authority — clear boundaries instead of diffuse responsibility.

Exposure can be uncomfortable: seeing criticism, being observed, admitting mistakes — it challenges our ego. It also requires time and discipline that project budgets often don’t allow for. Many organizations avoid this “pain,” resulting in misunderstood requirements, misplaced priorities, and costly rework.

In the short term, traditional silo thinking may feel more efficient. In the long term, it costs twice as much — in time, support, and user acceptance. The insight is simple but powerful: those who don’t truly feel user problems build solutions that only work on paper.

Tools can’t replace collaboration — but they can make it easier and more inclusive. HELIO provides an ideal ecosystem for a shared workspace: predefined controls, templates, theming, and a guided IDE that allows different roles to build, test, and iterate prototypes quickly. This reduces technical friction and makes exposure work more productive: designers can directly implement ideas, developers see technical limits early, and application engineers can adjust logic on-site.

The key is that tools should connect roles, not shift them. A good editor or design system creates shared language and structure so that decisions become faster, clearer, and repeatable.

Disagreement is inevitable — and valuable. Diverse perspectives prevent tunnel vision. What matters is having a framework in which conflicts can be handled constructively: clear success criteria, fact-based discussions, shared user observations, and transparent decision-making. In this way, conflict becomes a source of better solutions.

• Stable teams: Minimal rotation during critical phases.
• Management support: Leadership that institutionalizes interdisciplinary work and delegates authority.
• Measurable outcomes instead of outputs: Focus on usability, adoption, and operating costs.
• Rituals for exchange: Joint reviews, field days, pairing sessions.
• Training & coaching: Collaboration must be learned — not everyone brings that experience.

“There is only one team” is more than a slogan — it’s a shift in mindset. Product quality emerges where different areas of expertise interact, challenge each other, and share responsibility. Those who foster this attitude — through processes, rituals, and the right tools — reduce risks, accelerate learning, and create HMIs that work in practice and remain sustainable in the long term.

The HELIO Design System
The HELIO Design System is a set of elements that allow you to create future-proof user interfaces for industrial machines.
docs.helio-hmi.com/docs/reference/design-system

The HELIO SDK
Building on our highly extensible core architecture, we have carefully designed APIs that allow you to start quickly while also scaling for large teams and long product cycles.
docs.helio-hmi.com/releases/25.2.0

What makes HELIO unique
HELIO is a no-code tool for creating industrial HMIs that is different from others.
docs.helio-hmi.com/docs/getting-started/what-makes-helio-unique

Building HMIs Without a PLC
Begin user research, prototyping, and implementation before the PLC is available. More importantly, start a conversation with PLC engineers about the PLC API. What data is available, and what is its format?
docs.helio-hmi.com/docs/guides/building-hmis-without-plc-connection

Internationalization
HELIO was built from the ground up with Internationalization in mind. Onboard technical documentation specialists onto your team.
docs.helio-hmi.com/docs/guides/internationalization

There Is Only One Product Team — Gedankentank.
Why real product teams share responsibility — and how silos block innovation.
gedankentank.com/blog/2025/10/13/there-is-only-one-product-team

Increased Exposure Hours — Jared Spool.
Spending more time with users leads to better decisions and more sustainable design.
jmspool.medium.com/fast-path-to-a-great-ux-increased-exposure-hours-afde796f2e43

How to Get Along with Designers — Eleken.
Practical advice for designers and developers to communicate and create effectively together.
eleken.co/books/how-to-get-along-with-designers-and-work-well-together

Product vs Feature Teams — SVPG.
Why product teams create value — while feature teams merely deliver tasks.
svpg.com/product-vs-feature-teams

Simon Sinek — Cooperation Talk (Video).
Humans succeed through cooperation — not by competing alone.
youtube.com/watch

Shape Up — Making Teams Responsible (Basecamp).
How ownership and clear boundaries make teams more focused and productive.
basecamp.com/shapeup/0.3-chapter-01

This article is part of the series:

1. User-centered approach
Those who focus on people rather than products not only get more satisfied users, but also better products.
Read More

2. Technological future-proofing
Web technology is leading the way because it offers a huge user base, established standards, and open interfaces.
Read More

3. Process and resource efficiency
Efficient HMIs don't happen by chance—they happen through clear processes, the right tools, and good role distribution.
Read More

4. Independence & scalability
When creating industrial HMIs, you should not tie yourself to suppliers or hardware. Independence is key, and here's why:
Read More

5. There is only one team
Successful HMIs are not created by tools or technology alone—they are created through genuine collaboration.

6. Practical sense
This is our ultimate ingredient for building future-proof HMIs. The best part is that it is usually already built in at the factory.
Read More