Kaizer Chiefs Management’s SERIOUS Meeting WITH Nabi after poor run.

Chiefs’ management held an urgent meeting with head coach Nasreddine Nabi. Why was this meeting held? Was it a scheduled one? Let’s find out.

Kaizer Chiefs hold an emergency meeting after poor run of games.

Chiefs’ management has taken decisive action, meeting with head coach Nasreddine Nabi and his technical team to address the club’s recent struggles. The move comes after a disappointing 2-0 defeat to Richards Bay, adding to previous losses against Mamelodi Sundowns (1-0) and a crushing 4-1 home loss to SuperSport United.

Urgent discussions on turning the season around

According to a source within the club, the meeting wasn’t a routine post-game analysis but a strategic session aimed at immediate improvements.

“It was a meeting about looking at how they can improve things. Everyone at the club knows and believes that the team is on the right track and can do better than the way things are. So, in this meeting, it was not the normal post-game technical team meeting. It was with the management who looked at the way forward on how to improve things with the remaining games in the league and the Nedbank Cup. It was like a brainstorming session,” the source revealed according to Soccer Laduma.

Top-eight finish and Nedbank Cup

The club’s leadership emphasized the need to secure a top-eight finish in the league while maintaining a strong push for the Nedbank Cup, where Amakhosi await the winner between Sundowns and Sekhukhune United in the semi-finals.

“They had the meeting to figure out how they can avoid what happened last season, where they finished 10th in the league and ended the season without a trophy. They talked about how they can finish in the top eight with eight games to go in the league as well as fight for the Nedbank Cup. It was a constructive meeting where all parties agreed that the team is not in a good space and things need to change,” the source added.

Can Chiefs turn their season around?

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.