I've learned — slowly, and mostly through expensive mistakes — that bad projects go wrong in the first conversation. Not in the third week when the revisions pile up, not at handoff when expectations diverge, but in the first thirty minutes, when something is agreed to without being properly understood.

The moment you say yes to something you haven't fully unpacked, you've already set up the misalignment. Everything after that is just waiting for it to surface.

So now I'm very deliberate about the first call. I'm not trying to impress the client or sell the engagement. I'm trying to understand four things.

Do they know what they want, or what they need?

These are often different things, and not in an insulting way — it's just that people come to a designer knowing the symptom, not necessarily the diagnosis. A founder who says "we need a new website" might actually need clearer positioning first, because the reason the website isn't converting is that nobody knows what the product does when they arrive. A founder who says "we need a rebrand" might actually need better photography and a more consistent tone of voice — not a new logo.

My job in the first call is to figure out which problem we're actually solving. Not to take the brief at face value, and not to dismiss what the client thinks they need — but to ask enough questions to understand what's underneath it.

Is the deadline real or wished?

"We want to launch in two weeks" and "we have to launch in two weeks" are completely different projects. One has flex built in; the other doesn't. Both are workable, but they scope and price differently. A deadline with real consequences changes how I structure the work and what I tell the client about the tradeoffs.

I ask this directly. Not aggressively — just: is this a hard deadline or a target? It changes everything.

Who is the decision-maker?

This is probably the question I've learned the most from getting wrong. When I'm presenting to one person who can say yes or no on the spot, projects move quickly and cleanly. When I'm presenting to one person who then presents to three others who have separate opinions, I need to build that into the process — more checkpoints, more rationale documented, more time allocated for internal feedback loops.

I need to know this at the start, not after the second round of revisions.

What does success look like in six months?

This is the question that tells me more than the brief. "We want to close a Series A" means the brand needs to feel like something investors take seriously. "We want 10,000 paying users" means it needs to earn the trust of real people who are slightly skeptical. "We want to be acquired" is a completely different frame from "we want to build something for the long term."

These aren't the same brand. The same visual quality applied to different positioning strategies produces completely different outputs.

Thirty minutes. Four questions. That's the project.