Notice: this article was originally published on our project QuickAdmin blog.

There are words and phrases you totally don’t want to hear or read during your web-project creation process. I’ve decided to take the most painful ones and make a list — would you recognize any of these happened to you?

Phase 1. Before the project

The first phase when things can go wrong is before the project even starts — when you get a brief from the client, or have first discussions.

1. Client: “I don’t know how to explain. I’m not a developer, You’re the professional here, you will figure it out.”

This usually happens when client isn’t an IT person. And that’s totally fine. What is horribly wrong is when the client refuses to take any part in any technical decision-making. This leads to guessing what the client actually wants and, believe me, it’s almost impossible to be right here.

How to fix: even if the client is not technical, get him involved in the technical part — they need to explain the things in their own words. Then you need to educate them on some basic technical things and make some decisions together. Alternatively, you might refuse to take the project, cause potentially it involves additional time to educate the client on technology.