Design Thinking: The Lazy Way to Justify Losing an Argument
The Problem with Design Thinking
Design thinking was supposed to change everything. It was supposed to be the framework that finally got everyone—engineers, product managers, business leaders—to think the way designers think.
It didn't work. And here's why: we invented it because we lost the argument.
For decades, designers tried to convince organizations that their perspective matters. Every time we made the case directly, we lost. So we rebranded. "Design thinking" was supposed to be teachable, scalable, something consultants could sell. If we couldn't convince people that designers were smart, maybe we could convince them that thinking like a designer was smart.
It was the same losing argument in a fancy costume.
The core problem with design thinking is this: it assumes other people are broken and we're here to fix how they think. It assumes engineers would ship better products if they just thought about users more. That marketers would make better decisions if they just understood human behavior. That everyone would be better at their jobs if they just thought the way we think.
That's not the problem. That's not even close to the solution.
The Real Problem: We Don't Behave Well
When designers do get a seat at the table, we misbehave. We slow things down. We try to control everything. We treat projects like personal passion quests. We argue. We insist. We act like we're the only people in the room who understand what matters.
Then we're shocked when people stop listening to us.
Most resistance to design isn't because people don't understand it. It's because designers are hard to work with. We show up late to conversations, demand control over decisions we didn't help make, and present our ideas as the only rational way to think. We're not earning a seat at the table—we're demanding one. And when we don't get it, we invent a new term.
Design thinking included.
Ground Rule #1: Stop Assuming Everyone Else is Stupid
You are not smarter than the people you work with. Engineers are not dumb. Product managers are not dumb. They just have different lenses and different constraints.
Design thinking tried to solve this by teaching everyone to think like designers. But that's not the problem. The problem is that we approach conversations as if everyone else is broken and we're here to fix them.
You have a lens that is genuinely valuable, and it's not currently being included in decisions the way it should be. Not because people are stupid, but because your lens is different from theirs. That difference is the whole point. You don't need to make them think like you. You need to show them that your perspective solves problems they care about—and you need to learn their languages well enough to make that case.
For engineers, that's usually shipping without technical debt. For product managers, it's delivering the roadmap on time. For business leaders, it's hitting revenue targets. These aren't bad priorities. They're just different from yours. If you can show how understanding human problems first helps them hit their goals, they'll listen. Not because they think like designers. But because you've made the case in terms they care about.
Ground Rule #2: Learn Behavioral Economics and Incentives Instead of Trying to Win Arguments
Designers are not particularly great at arguing. We try to win arguments by being right. But being right doesn't change behavior. Incentives change behavior.
This is where behavioral economics comes in. It's the study of how people actually make decisions—not how they should make decisions, but how they actually do. And the answer is: almost never based on who has the best argument.
Most of the resistance you face when you try to introduce design thinking isn't resistance to the idea. It's resistance to the *work*. When an engineer says "I don't have time for user research," they're not saying user research is dumb. They're saying: "I have a deadline. I have feature work. I have bugs to fix. Adding research to my plate means something else doesn't get done."
That's not stupid. That's rational given their constraints.
So instead of arguing that they *should* do user research, change the incentives. Do the research yourself. Show them what you found. Don't ask them to validate your assumptions—give them validated assumptions to build on. Don't slow down their process—speed it up by removing guesswork.
This is the key insight that design thinking completely missed: you don't convince people by teaching them to think differently. You convince them by doing work that makes their lives easier.
And here's the trap designers fall into: we try to argue on other people's turf. We go into engineering meetings and try to convince engineers that user research matters. We go into product meetings and try to convince product managers that empathy is important. We're always playing away games.
Bring people to your home stadium instead. Do the work first. Show them the thing. Let them respond to something tangible instead of an argument.
Because here's what happens when you do that: the argument disappears. The argument was always "I don't have time for you to do that work." If you already did it, you skip that entire conversation. You're not asking for permission anymore. You're presenting a fait accompli: "Here's the design. Here's what I learned. Here's how it solves the problems we're trying to solve."
Now they can't argue about whether the work should happen. They can only respond to the work that already exists.
Ground Rule #3: Build Trust, Don't Convert
This is the hardest one, and it's the one that design thinking completely missed.
You don't need engineers to think like designers. You don't need them to have your lens on everything. You don't need them to care about design the way you do.
What you need is for them to trust that what you're doing is going to help all parties involved. Not just users. Not just design. All parties. Engineering included.
That trust is earned through consistency. Through showing up prepared. Through understanding their constraints. Through delivering work that makes their job easier, not harder. Through not wasting their time. Through not pretending to have all the answers.
It's earned by being useful.
And it's destroyed the moment you start acting like you know better than they do. The moment you insist on doing things your way. The moment you treat their concerns as obstacles instead of information.
Here's the difference: design thinking says "I need to teach you to think about users." Trust-based design says "I understand your constraints. I've done work that respects them. I trust you to make good decisions with better information. And I trust that you're trying to do right by users too—you just have different constraints than I do."
One approach tries to convert people. The other builds partnership.
And partnership is what actually moves the needle. Not because everyone suddenly understands design. But because you've built a relationship where people know that when you show up with a perspective, it's because you've done the homework and you're trying to solve a problem that matters to them too.
Why Design Thinking Got Popular (And Why It Failed)
Design thinking got popular because it was easier to sell than the real work. It was easier to say "let me teach you to think like a designer" than to say "I'm going to do a bunch of research and show you something that makes your job easier." It was easier to invent a methodology than to earn trust one project at a time.
And it failed because you can't teach people to care. You can only show them that caring works.
The companies and teams that actually integrated design weren't the ones that bought into design thinking as a methodology. They were the ones that had designers who did good work, understood constraints, made other people's jobs easier, and earned trust through consistency.
They weren't trying to convert anyone. They were just trying to solve problems.
What Design Actually Requires
Design doesn't require everyone to think like a designer. It requires designers who show up prepared, respect other people's expertise, do work that makes people's lives easier, and understand that their job is not to convert people.
Your job is to solve human problems well enough that people trust you to do it again. That's infinitely harder than inventing a new term. But it's the only thing that actually works.
—Bert