Luka Doncic has been everything the Los Angeles Lakers hoped for this season — elite scoring, creative playmaking, and nightly superstar production. But on Monday night, even a 38-point performance wasn’t enough to mask the issues that unraveled the Lakers in their 125–108 loss to the Phoenix Suns at Crypto.com Arena.
And Doncic didn’t shy away from the blame.
The Lakers committed 22 turnovers, with nine coming from their All-Star guard alone. Even with his massive usage rate, that number was far out of sync for someone who normally dictates the game with precision and control.
Phoenix made them pay for every mistake, turning L.A.’s giveaways into 32 points, the kind of swing that shifts an entire game. By comparison, the Lakers generated just 13 points off the Suns’ 11 turnovers.
After the loss, Doncic broke down what threw him off.
“It was definitely a different defense than other teams play,” Doncic said via ESPN.
“They kind of tried to let me go score instead of creating for others. It was confusing. But still — I just can’t have that.”
🧩 Suns Flip the Script with Unusual Defensive Approach
The Suns’ plan was simple but disruptive:
force Doncic to be a scorer, not a creator.
By staying home on shooters and cutters while funneling drives, Phoenix took away the passing windows that usually fuel the Lakers’ flow. Doncic still produced on the scoreboard, but the offensive rhythm around him broke down — and the turnovers mounted.
With LA’s seven-game win streak broken, the performance highlighted a potential blueprint other teams may try to copy.
🚀 What’s Next for the Lakers?
Now sitting at 15–5, the Lakers head into a three-game road trip starting Thursday against the Toronto Raptors. For Doncic and the team, the message is clear:
Clean up the mistakes, recalibrate the offense, and don’t let one bad night snowball.
Even in defeat, Doncic showed accountability — a trait that usually leads to quick corrections, especially for a star who rarely makes the same mistake twice.
Join the Discussion
0 Comment(s)
Login to join the discussion: