Working between technology, communication and people

Working between technology, communication and people does not mean being an absolute expert in all three. It means understanding enough of each to preserve meaning as it moves between them, and knowing when to make room for someone with deeper expertise.

My path moved from technical school to communication, photography and audiovisual production, then to a digital agency, products and finally a tech company. Read as a list of sectors, it looks discontinuous. In practice, it brought me ever closer to the same point: where a need expressed by one person must become something another person can design, produce or sell.

Today I often work between salespeople, technical teams, customers and creatives. I do not own the outcome and cannot claim the work of those who build it. My contribution is to help the parties understand one another, surface constraints before they become conflicts and keep the original problem central even when the conversation fills with solutions.

Translate without oversimplifying

Every professional group develops a language. Technical teams discuss dependencies, architectures and implementation time; salespeople opportunities, value and decisions; creatives intention, tone and experience. Customers bring the language of their own context, often mixing symptoms, ambitions and constraints. Translation is not replacing difficult words with easy ones. It is preserving meaning while the audience changes.

Poor translation creates promises the product cannot keep or correct solutions the customer cannot recognise. Avoiding it requires questions in every direction. What practical consequence follows from this technical constraint? Which process would change if this feature existed? What result has sales promised? Which behaviour should the creative work make easier? The answers form a shared map.

Coordination does not deserve all the credit

Coordinators are highly visible because they take part in every conversation. That visibility can create the impression that they made everything happen. In reality, coordination creates value only when it enables other people's specialist work. Products work because people design and develop them; content works because people conceive and produce it; commercial relationships endure because several people keep the promise made.

The person in the middle must assign responsibility and credit correctly: not speak for technical colleagues when their voice is needed, not claim an insight that came from the customer, and not treat the creative team as an invisible service. Good coordination makes the system legible and people autonomous. If everything continues to depend on the coordinator, coordination has failed.

Technology always enters a human context

A technology product never enters an empty space. It enters established processes, habits, fears, objectives and power relationships. A technically impeccable feature may not be adopted because it requires an undiscussed behaviour change. A simpler solution may succeed because it respects how people actually make decisions.

Communication matters here not as final packaging but as a tool for understanding. It names the change, explains why it is needed and surfaces resistance before it becomes rejection. Work with people is not a stage after development; it is part of the technical problem because it determines whether what was built will be used as intended.

The value lies at the joins

A hybrid profile does not replace vertical expertise. It works at the joins between specialties, noticing when departments use the same word differently, a customer request hides operational risk, or an elegant solution merely moves the problem. This connective work is valuable only when it remains concrete and verifiable.

The thread connecting my experiences is not variety of sectors but a way of working: observe the context, clarify the question, connect people who hold different parts of the answer and accompany the promise through delivery. Sometimes that means guiding the conversation; sometimes it means stepping aside so the right people can speak directly.

Working between technology, communication and people is a boundary discipline. It requires curiosity to understand what you do not master, precision not to distort it and humility not to confuse connection with construction. Together, those qualities turn differences in language from obstacles into project material.

There is also a practical requirement: leave a trace. A clear summary, written decision and open question assigned to the right person prevent translation from depending on the memories of those in the room. Documentation does not replace relationships, but makes them less fragile and turns coordination into shared property rather than a chain of private conversations.