Technician to leader: The art of letting go

Growing with the pace of the IT industry

Sharp traces his path in tech back to the earlier days of home computing, a time when enthusiasm for technology often clashed with scepticism about its future. He recalls working with ZX Spectrums and early tech in the 1980s, always knowing he wanted to work in the field, even if others weren’t convinced it would last. His parents were sceptical about computing as a long-term career, so he initially explored more traditional options before eventually being drawn back into technology.

That return wasn’t a straight line into engineering, but a shift in perspective. Rather than pure hands-on development, he re-entered the industry through project management, marking an early example of how his role would evolve alongside the sector itself. What followed was a business journey that began in 1995 with training and early software development using Microsoft Access, before gradually expanding into a value-added reseller model in the early 2000s. By around 2010, the company had again adapted, this time becoming an early adopter of the managed service provider model. This was a shift that reflected where the wider IT landscape was heading.

Today, Abussi remains deliberately lean but geographically distributed, with work spanning MSP management alongside software and workflow development. Sharp notes that this direction wasn’t accidental but aligned with market momentum, describing how “the vast majority of our work now is higher-level MSP management, workflow and software development, because that's where the market is going.”

His own role has transformed just as dramatically as the business itself. Where once he would be on-site, physically fixing issues and working directly with infrastructure, his day-to-day is now firmly rooted in leadership and oversight. Underlying this evolution is a mindset shaped by one influential idea from early in his career: Michael E. Gerber’s E-Myth. The core lesson, he explains, is about structure and growth. When you start out, your name appears in almost every box, but leadership is about steadily removing yourself from those boxes and replacing your role with capable people who can own them. It reflects both his own progression and the wider shift in tech from hands-on technical work to systems delegation and leadership at scale.

 Why letting go is the key to growth

Sharp describes delegation not as a management technique, but as a fundamental survival skill for any growing business. One of the earliest and most important shifts he made was removing himself entirely from financial operations, a decision he still sees as pivotal. He explains: “The first thing that I did, which was the best thing I ever did, was move all financial management, day-to-day bookkeeping, anything to do with finance, to an external company,” adding that this external support became essential to stability.

That experience set the tone for how he thinks about responsibility more broadly. For Sharp, growth only happens when ownership is genuinely transferred, not just shared in theory. He is explicit about the core principle that followed: “I think the big lesson to learn is if you're a business owner, you can't hold onto it all, you have to delegate and give responsibility to other people.” It’s not framed as optional, but as a necessary condition for scale.

He also acknowledges that this is not a clean or instinctive transition. Moving from being the person who does and fixes everything to someone who trusts others to do it better is, in his experience, uncomfortable and ongoing. Even when a team is fully capable and the business is running smoothly, the instinct to re-enter decisions can remain strong. What changes over time is not just structure, but identity, shifting from being embedded in day-to-day execution to operating above it.

That evolution is what separates early-stage operators from long-term leaders. The role stops being about controlling tasks and becomes about creating the conditions where others can take ownership and perform without constant intervention.

He also frames it as a question of perspective. Being in an industry for a long time can make it harder to see things clearly, as approaches evolve and people bring in newer skills, fresh thinking, and often better ways of doing things. At that point, strong leadership is about recognising you may not always be the best person for the job anymore, being willing to step back, and allowing others to lead where they are stronger.

Managing customer expectations and misconceptions

Sharp highlights that one of the most overlooked challenges in moving from a technical role into leadership lies not just internally, but in how customers and teams continue to perceive you.

In his experience, especially in a small-to-medium IT business that has grown over time, many long-standing clients still associate him with the hands-on technical work he once did. In his view, “the biggest problem that you have is the customer understanding that you're not that guy anymore. Or you're not that woman anymore. You are not the person to speak to about a day-to-day technical issue.”

Instead, the reality has shifted completely. He describes moving into a management role while former technical responsibilities are still associated with him by others in the business. That gap between how he is perceived and what he actually does has become one of the most persistent challenges in leadership.

The discipline is in deliberately stepping back and resisting the urge to get involved where it is no longer necessary. The real risk is that even a well-intentioned intervention can pull you straight back into the old perception of your role, undoing the shift you’ve made, and reinforcing the idea that you are still the person directly handling technical issues rather than the one leading the wider organisation. 

Burnout and decision fatigue

Burnout and decision fatigue often come from trying to hold onto too much for too long, especially in leadership roles where the number of small daily decisions never really stops growing. The way through it starts with people rather than processes: “find good people in your business. Trust them, give them a clear framework of operation, and let them get on with it.”

Once the right people are in place, a lot of the pressure naturally begins to ease. Strong teams, he argues, don’t just take on tasks, they take on responsibility when properly trusted. But even then, the challenge is internal. A key part of reducing that mental load is letting go of perfection as the standard. “Perfect is a relative activity,” he says, and chasing it can actually slow everything down. Instead, “good is acceptable, good is what most people want, good is fine. Perfect will get in the way of you providing good.” That shift alone removes a constant layer of pressure to step into every detail.

This can often mean being involved in only a fraction of a function, while the majority is handled elsewhere, allowing him to focus only on the more complex or high-stakes issues rather than the day-to-day noise. There will always be edge cases and problems that need senior input, but those should be the exception rather than the default. The goal is to avoid being pulled into everything, and instead focus energy where it genuinely adds value.

Building teams that understand people, not just tech

A big part of building the right team is realising that the best people are not always the ones with the most traditional technical backgrounds. In fact, some of the strongest hires can come from completely different industries. He points to two employees in particular at Abussi who came from customer service roles in a cinema.

What stood out, he explains, wasn’t their technical knowledge, but how well they translated skills like communication, patience, and empathy into a technical environment. Over time, they proved to be among the best people they had ever employed, because they grasped something fundamental about the industry: “it’s not about the tech. The tech is a secondary thing to what it is you’re trying to achieve for the customer.”

That shift in perspective reframes what good IT service actually means. It’s not just systems working, but outcomes for people. What customers really need is “reliability, safety, good advice, and for their IT systems each day to not metaphorically kick them in the head when they turn them on every morning.”

Because of that, he places huge value on interpersonal skills within his team. Being able to communicate clearly, listen properly, and avoid talking down to customers is just as important as technical ability. The goal is to have people who can empathise with a person’s problem rather than defaulting to technical jargon or superiority. The better outcome comes from keeping things simple, human, and honest, and treating it as a conversation rather than a demonstration of knowledge.

Ultimately, he argues that if customers already understood IT at a deep technical level, they wouldn’t need external support in the first place. The value of the service, therefore, lies not in showing how much you know, but in making things understandable and genuinely helpful. 

Stepping back to move forward

Overall, leadership in the IT channel isn’t what it used to be. It’s no longer about being the person who can fix everything, answer every question, or sit closest to the technical detail. For leaders like Sharp, the role moves away from day-to-day technical delivery and towards something far more difficult to define, and arguably harder to master.

It’s about translation. Between customers who don’t speak “tech” and engineers who live in it. Between what a business wants and what is actually possible. Between urgency, expectation, and reality. But it’s also about restraint. Knowing when not to get involved. Stepping back so others can step forward. Trusting people to do the work better than you do.

And underneath it all sits a consistent theme from Sharp’s experience: leadership is less about doing more, and more about doing less. Delegating properly. Building strong people around you. And accepting that success in the channel isn’t about holding everything together yourself, but making sure you no longer have to.