Skip to main content

Suns are learning precisely what the Hornets always knew about Mark Williams

Mark Williams is a liability in plenty of departments.
Feb 22, 2026; Phoenix, Arizona, USA; Phoenix Suns center Mark Williams (15) against the Portland Trail Blazers at Mortgage Matchup Center. Mandatory Credit: Mark J. Rebilas-Imagn Images
Feb 22, 2026; Phoenix, Arizona, USA; Phoenix Suns center Mark Williams (15) against the Portland Trail Blazers at Mortgage Matchup Center. Mandatory Credit: Mark J. Rebilas-Imagn Images | Mark J. Rebilas-Imagn Images

Mark Williams was once viewed as the long‑term anchor of the Charlotte Hornets’ frontcourt. The franchise effectively chose him over Jalen Duren in the 2022 NBA Draft, betting on his size, tools, and developmental upside. But in his first game against his former team, Williams delivered a performance that highlighted both the promise and the pitfalls that ultimately pushed Charlotte to move on.

The Hornets had long suspected this experiment wouldn’t pan out, largely because of durability concerns and a skill set that was never fully realized.

Williams has always flashed the ability to be a nightly double‑double threat, even in limited minutes. Yet the inconsistencies in his game, paired with a ceiling that now appears lower than once hoped, have become impossible to ignore. His archetype of a traditional center with limited offensive creation has grown increasingly rare in today’s NBA.

Williams posted 12 points, four rebounds, one assist, three steals, and one block in 20 minutes. On paper, that’s a respectable line for a player returning from injury. But the box score doesn’t capture the full story of what showed against Charlotte.

Suns are learning a harsh truth about Mark Williams

Despite tallying three blocks, Williams struggled mightily when he wasn’t getting his hands on the ball. The Hornets repeatedly attacked him at the rim, scoring with ease and exposing the volatility in his defensive game.

His rebounding is an area where a 7’1” center with a 9’9” standing reach should thrive, but that was also a glaring issue. Compared to Moussa Diabate, who is shorter with decreased length, outworked him on the glass. At one point, Williams had just one rebound in 10 minutes, while Diabate finished in double-digits in the boards department.

Rust from a foot injury is a fair argument, but it also underscores the biggest red flag on Williams’ resume: availability. Charlotte lived this reality for years.

If a big man isn’t going to stretch the floor or create offense, he must excel everywhere else. Williams’ limited offensive bag means he’s heavily dependent on teammates to generate his scoring opportunities. Combine that with chronic injuries, and it’s not crazy to think why he was a short-timer with the Hornets.

During his time in Charlotte, Williams averaged only 35 games per season—roughly 43 percent of the schedule. Jeff Peterson ultimately decided the franchise couldn’t continue building around a center who couldn’t stay on the court or adapt to the evolving demands of the position. His injury history was concerning enough that the Los Angeles Lakers voided a trade after he failed his physical.

Hornets dodged a bullet

The Suns still took a chance, banking on his physical tools and the upside that once made him a lottery‑caliber prospect. But the same concerns that pushed Charlotte to move on are already resurfacing.

In hindsight, the Hornets’ decision looks justified. The combination of lingering health issues, inconsistent defense, and a limited offensive profile made Williams a difficult long‑term fit. Meanwhile, Charlotte appears to have found a more reliable and impactful frontcourt piece in Diabate. He has the motor, strong rebounding skills, defensive versatility, and availability that align far better with the modern NBA.

The Suns may ultimately decide not to re-sign Williams this offseason. And if they don’t, it will simply reinforce what the Hornets realized earlier than anyone else. Some gambles don’t work out, no matter how enticing the physical tools may be.

Loading recommendations... Please wait while we load personalized content recommendations