COMMENT: It was like a sledgehammer. And perhaps it wasn't needed. But Manchester United's players received two messages this past week from their manager. Two messages that should leave them in no doubt who they're dealing with...

It was ruthless. Indeed, this column would say brutal. Even unnecessary. But he did it. Ten Hag taking the extraordinary step last week of banning Jadon Sancho from the club's annual season photoshoot. With this feud now running into it's second month. With no movement from either side. Ten Hag wasn't for budging. Even for the traditional team photo. Sancho, for season 2023/24, was written out...

Or in modern speak, Sancho was effectively canceled as a Manchester United player. He's still getting that £350,000-a-week wage. He still has himself being snapped around town. But as far as being a United player for '23/24, Jadon Sancho has been written out of the club's history books.

And as we say, for this column, this action by Ten Hag was unnecessary. Indeed, a step too far. Regulars will know we support Ten Hag in his approach towards Sancho. Given what he's inherited. Given what he's still trying to weed out. Such forceful action has been necessary to shake the dressing room from it's malaise and underachievement. And indeed, there is still work to be done.

But writing Sancho out of the annual team photo is the wrong call. This goes beyond personalities. This is about history. Tradition. Even family. Any fan. Any player's family. They can go into United's archives and pull out team photos dating back over a 100 years. The names. The families. It's a record. It's a source of pride. And for whatever the transgression of Sancho, his future kids and grandkids don't deserve this.

Indeed, the club don't deserve it. An asterisk for the first time in United's annual team photo? The club needs to be bigger than that. As does manager and player. This is bigger than them. It's bigger than any rift. The team photo transcends that. At least it should. Indeed, for the sake of the club, the squad and staff should be re-assembled to have the shot retaken with Sancho. These feuds will pass. But for everyone involved, they won't get this moment back. Someone needs to step in and uphold something which is a basic foundation stone in a club's history and culture. This cannot be so flippantly cast aside.

As we say, this was a brutal decision. Indeed, unnecessary. But with context, you can understand it. You can see Ten Hag's perspective. As ruthless as he has been with certain elements inside the United dressing room, the Dutchman is also a manager who will give his players everything - even at his own expense.

There were two messages for the players this past week. Sancho, of course, but also Antony and the backing he has received from Ten Hag. It's been unwavering. Steadfast. From the player's granted leave to his recall and Saturday's start at Sheffield United. Just as he was prepared to do for Mason Greenwood, it's been Ten Hag who has been the public face of Antony's defence. That's just how he is.

So the players know. If they do right by Ten Hag he'll defend them to the hilt. Even if it was to damage his own profile. His own brand. He will do so. It's an approach not so common in today's game. But it's a trait of Ten Hag's. As we've highlighted in past columns, his work at Ajax only reaffirms this. This is what United's players can expect. For better or worse, the manager will be behind you.

Which is perhaps why his treatment of Sancho has been so brutal. There's a sense of betrayal in all this. Maybe Sancho can't see it, but it's there. For a manager who goes so far down the line for his players, to have Sancho behave as he has is something that has cut Ten Hag. It's personal.

But that still shouldn't be enough for the manager to mess with traditions as he has this past week. The team photo needs to be redone with Sancho included. This is bigger than any two personalities. For a manager trying to re-connect this dressing room with the club's roots, disregarding the traditions of the annual team photo is simply the wrong call.