It was early in my design career. After two years as a Junior Designer, I felt ready for something bigger. I was confident — perhaps too confident — that I had mastered everything I needed: problem-solving, collaborating with developers, and understanding the business side of things. I started applying to larger, more corporate companies, and soon, I was invited for interviews.
I sat staring at a glass of water on a massive wooden desk in a sleek, modern meeting room. The room was a bit cold, but I knew I'd be sweating soon enough. In my head, I rehearsed my answers — how I'd introduce myself, how I'd explain my past projects. Shortly after, one Product Manager and two designers walked in. After a bit of small talk, we got to the real questions.
"How do you resolve disagreements with stakeholders?" they asked.
"It really depends on the topic," I replied. "Sometimes it requires more discussion; other times, more research." That was it. No further explanation, no specific example — just a vague, catch-all response. There was an awkward silence.
The next question: "How do you typically hand off your designs?"
"Well, it depends on the size of the project. For smaller ones, I keep it minimal. For bigger ones, I make it more detailed."
Again, silence — this time longer.
They continued: "Which tools do you usually use?"
As you can guess, "It depends on the project. I usually use Sketch."
(For the love of God, just say the tools already!)
The interview dragged on awkwardly. A few days later, I received the inevitable rejection. Now, with five years of experience under my belt, I can see the problem: I had fallen into what I call the "it depends" trap.
Why 'It Depends' is a Trap
"It depends" has become a crutch for designers to avoid giving strong opinions or to dodge tough questions. While it's valid in some situations, overusing it — especially in interviews — can undermine your credibility and hinder your problem-solving abilities. In fact, how you use "it depends" might determine whether you succeed or fail in critical conversations.
Why and When 'It Depends' is a Bad Answer
It's not actionable: Talking about dependencies without diving deeper is just making a claim. Instead of saying, "Making X design depends on the available resources," you could ask, "What resources are available?" This is a question they can answer so you can resolve the dependency in your head and directly come up with a solution. Managers, with their packed schedules, will appreciate this approach because it shifts the conversation towards solutions.
It keeps designers in the safe zone: Design is all about making decisions. Regulating mixed signals, gathering input from all stakeholders and providing something meaningful as output. This requires by nature having some opinions, taking sides and some risks. Knowing when to have an opinion or when to stay skeptical is one of the things that defines seniority of a designer. Overusing "it depends" puts one into constant skepticalness which would make them look insecure with their work and this is the opposite of what they tried to look like by staying in the safe-zone.
It's unsatisfying: "It depends" rarely answers the actual question. When people hear this, they often feel like their question is being dodged, which can damage your credibility.
It's generic: In reality, almost everything depends on something. While it's true that dependencies exist in most decisions, the value lies in acknowledging them quietly and delivering solutions that account for them.
Should You Stop Using It Altogether?
No, but you need to be aware of when it's leading you into a trap. Next time you're tempted to say "it depends," ask yourself:
Are you dodging the question or buying time?
Don't be that person. Managers can spot this, and it will diminish your credibility.
Are there actual dependencies that could change the design?
Instead of simply saying "it depends," ask questions that help clarify the dependencies. This way, you can offer a more concrete response.
Do you already know the answer for each case?
If so, you can use "it depends" effectively. Follow it with: "If X happens, I'd do A; if Y happens, I'd do B." This makes your answer actionable and informative.
