← Back to Charter market Management

The helm is not delegated — not in the season, not outside it

Andreja Fazlić

Andreja Fazlić

Andreja Fazlić osnivačica je konzultantske agencije Astarta: Bit koja djeluje na sjecištu marketinga, prodaje i razvoja poslovanja putem Inbound metodologije. Bez obzira uvodi li poduzetnike početnike… Read more

https://www.linkedin.com/in/andreja-fazlic
March 18, 2026

When a leader launches a change and then disappears from the process, the consequences do not stay in the meeting room — they surface in the middle of the season. In this article, Andreja Fazlić analyses how much such a pattern costs the team, operations and the overall guest experience.

Why do leaders run away from transformation, and how much does it cost their team in the peak of the season?

There is a pattern I have seen in almost every digital transformation project I have worked on.

The director comes to the first meeting. Enthusiastic, engaged, full of vision. He talks about how he has been waiting years for the right moment for this change. How he is fed up with putting out fires. How he finally wants to build something that works without him. He signs, nods, says “you know this better than me” — and disappears.

He checks in the week the budget needs approving. He shows up at the kickoff because it would have been awkward not to come. He answers a few emails — with a week’s delay — when the questions become too concrete to ignore.

And the team works. It learns the new tool. It designs processes. It spends weeks on something it has never done before, without clear instructions, without priorities, without someone saying “yes, go in that direction”. It asks. It waits. It assumes. It makes a decision because it needs to move forward. And it does it well — within the limits of what it knows and what has been delegated to it.

And then the director appears. At the results presentation, at the end of the first phase, or — most often — only when something starts going wrong. He looks at what has been done. Frowns. And says: “this is not what I envisioned.”

The team goes quiet. Someone present looks at the table. Someone else looks into their laptop as if a very important email just arrived.

And everything stops. Not loudly, not dramatically. But quietly, like when you turn off the air conditioner and only then realise how much noise it was making the whole time.

Delegation as the most elegant form of avoidance

For a long time I tended to react to this pattern with frustration. Over time I understood that behind it there is neither indifference nor bad will, but something much deeper and much more human.

But before I continue — one clarification, because delegation itself is not the problem. On the contrary, delegation is one of the most important leadership skills. It frees the leader’s capacity for strategic decisions. It develops the team’s competencies. It builds trust and autonomy. Without delegation, every leader becomes the bottleneck of their own business.

The problem is not delegation. The problem is when delegation becomes an excuse for absence.

And the difference between the two is not always easily visible — neither to the employees nor to the leader themselves. Because from the outside they look the same. The project has been assigned to the team, the team is working, the leader is not interfering. Except that in one case the leader is not interfering because he trusts the team and follows from a distance, and in the other because it is uncomfortable for him to be present. And that discomfort has very concrete reasons.

Change is a threat. And not only to the employees learning a new tool — but perhaps especially to the leader who initiated the project. Because a leader who actively engages in the redesign of processes must be ready for several extremely uncomfortable things. He must sit at a table with people who know more than he does about details he should know. He must accept that the old way of working — which he supervised, defended, maybe even designed himself for years — is no longer enough. He must make decisions in situations where he does not have all the information and where there is no clearly right answer. He must be visible in a moment of uncertainty — and that is, for someone used to performing from a position of authority and knowledge, an extremely uncomfortable place.

None of us likes looking insecure in front of our team. Nobody likes being in a room and not knowing the answer. Nobody likes admitting, to themselves or others, that the way we have worked for years may not have been optimal.

Fleeing into delegation elegantly solves all of that. The project exists, activities are under way, it can be said that work on the transformation is happening — and the leader is not exposed to it. Not at risk. Not responsible for details that could turn out wrong. And able to keep the authority without having to test it again.

What the team learns while you are gone

A team working without clear and present leadership does not stagnate — it improvises.

And that improvising looks like progress from the outside. Meetings are held, tasks are closed, the system is being filled with data. But underneath the surface something else is happening. Every decision the team makes without your knowledge carries an unspoken question: will this pass? Every step forward carries the risk of being overturned when “he/she appears and looks.”

Over time the team develops a survival strategy. It does not do what is most efficient — it does what it thinks will be approved. It stops proposing. It stops initiating. It waits to be asked. Because an initiative that was not met with support once does not easily repeat a second time.

The problem culminates at the moment of return. The leader comes back and passes judgement on a result they did not watch being made. And then it is not the quality of the team’s work being assessed. What is assessed is the alignment of the result with a vision that was never articulated clearly enough — neither to the team, nor perhaps even to the leader themselves.

That is the moment that destroys trust. Not dramatically, not with raised voices — but quietly. The team learns that initiative is not safe. That it is better to wait than to start. That every step forward is temporary until someone “from above” sees it and confirms it.

And the culture that forms then — a culture of waiting and covering oneself — does not stay as a picture on the wall. It goes outside. It spills into the season. It spills into every contact with the guest at the moment when there is no one to ask and a decision needs to be made right away.

July does not lie

In July there is no time for refinements, aligning visions and repeated meetings. In July you only see what has actually been built — and what has not.

Teams whose leaders were not present in the process of building the system do one of two things in the peak of the season: they wait for instructions for every step, or they make decisions they are not sure they are authorised to make. One crew member does not know whether they may offer the guest an alternative period without asking. Another person answers an enquiry a day late because they are not sure what the correct answer is. A third improvises — and the improvisation ends as a bad review that does not describe the boat, but the experience.

And the leader who started it all, who signed the project, who was enthusiastic at the first meeting — sits down in September and does not understand what went wrong. The tool is there. The system is there. Why are the results not?

Because a tool does not know how to lead. A system does not know how to decide. And a team that did not have a real captain at the helm cannot sail out of the storm on its own.

The leaders who have exceptional seasons are not the ones with better applications. They are the ones who were present enough for their team to know what to do without them — and mature enough to actually let them.

That maturity is not a character trait you are born with. It is the result of work. Work on understanding your own psychology in the context of change — your own fears of losing control, your own discomfort in uncertainty, your own need for it to be “exactly as I envisioned.”

Personal development of the leader is not a soft skills topic and not a luxury for calm business periods. It is an operational prerequisite for every season.

Where this story continues

Next month I am giving a talk at the Adriatic Nautical Business Forum 2026, and I deliberately anchored it to the thesis: the peak of the season and the premium experience never test technology — they test processes and leadership.

Because after years of working on digital transformation projects in charter, hospitality and SaaS, I am convinced that the biggest unused lever of growth is exactly this — a leader who is developed enough to build a system that works without them, and a team with enough trust to run it.

In the talk I will go into the details of what that looks like in practice, through concrete examples, experiences and an understanding of what stands between good intention and real result.

Because technology can help. Processes can be perfect on paper. But change is always — really always — started by a person.

If you are coming to the forum — let’s connect and start conversations about changes that bring real results.