Lessons Since 2006
What 20 Years in IT Taught Me About Trust
The leadership lessons I have learned about reliability, communication and accountability while building a managed technology business since 2006.
By Damir Grubisa, CEO of Group 4 Networks ยท Executive perspective
Trust is built during ordinary days
Customers notice how a technology partner behaves during a major incident, but trust is usually built much earlier. It grows through accurate updates, dependable follow-through, honest explanations and small commitments that are kept consistently.
Technical skill is only part of the promise
A provider can have strong technical knowledge and still create frustration if ownership is unclear or communication is weak. Customers need to know who is responsible, what happens next and when they will hear from us again. Clarity is part of service quality.
Say what you know and what you do not
Technology work involves uncertainty. I would rather explain what we have confirmed, what we are still investigating and what the next decision depends on than offer confidence that is not supported by evidence. Credibility is difficult to gain and easy to lose.
Documentation protects relationships
Good documentation is not bureaucracy. It allows another qualified person to understand the environment, continue the work and respond when the usual contact is unavailable. It reduces dependence on memory and makes accountability visible.
Long relationships require continued effort
Time in business does not automatically create trust. Every renewal, project and support request is another opportunity to earn it. My main lesson since 2006 is simple: customers may buy technology, but they stay when they believe the people responsible for it will be present, honest and accountable.
About the author
CEO of Group 4 Networks. I write about what I am learning while building and operating technology businesses across managed IT, cybersecurity, automation and practical AI.