I never really understand the goal of comments like this. Since we don't have access to your entire work history, it is impossible for us to judge a claim that,

I never really understand the goal of comments like this. Since we don't have access to your entire work history, it is impossible for us to judge a claim that, literally, every single feature you've ever built in your entire career -- even that one about allowing people to export to CSV -- involved you following the steps of: "[On immersion] identify hidden needs by having the innovator live the customer’s experience." "The final stage in the discovery process is a series of workshops and seminar discussions" "In the next step, articulation, innovators surface and question their implicit assumptions." And so on. Design thinking isn't "building a prototype". That is but one small part among many. You have workshops for everything you build? You do contextual inquiries, sitting in a customer office all day to see what their interactions are like, for every feature you build? You sit down with paper prototypes (not even code yet) with actual customers? For every single feature you build? Even when a customer just wants a button to sort Column X? I guess I'm dubious but if you've managed to create a work environment where that's the expectation, then more power to you. Design thinking is time consuming and expensive. That is why it is rarely used.