The difference is Design Thinking requires extensive documentation for each step.
You don't just empathize, you create characters with backstory.
You don't just define, you create a story outline with plot, protagonists, and antagonists.
You don't just ideate, you write novellas of your greatest achievements: deciding on the right color for error messages, the perils of rounded corners, and how you overcame the adversity of outdated stereotypes to make buttons that are fair and equitable to all people.
At least for new products. But I think some of these steps can be forgotten in established products. Many teams find themselves building features stakeholders asked, and DT can help going back to discovering what users actually want
However this can also backfire and good independent ideas can be shut down because they weren't found in the first 2 steps of the Design Thinking process.
With DT thinking "solution first" is kind of forbidden.
The magic sauce is the empathy part. Which is different than what was done back then in male-dominated, boomer-centric work places. It's equivalent of making a safe space before embarking on the rest of the standard design/dev processes.
How you feel about safe spaces will be analogous about how you feel of design thinking. A lot of consultants cashed in on this trend to sell all kinds of stupid things. That's also what he's talking about.
Now with new generation coming in, empathy is by default. Therefore, if you really think about it, design thinking is fizzling out because it's now the standard.