Establishing and maintaining good client relationships is probably one of the most fundamental issues when building a strong and lasting business. Partnership and transparency both are very important factors in a technological environment such as mobile app development.
But the truth is, some clients make it arduous to work on their ideas.
Not only they make your life more challenging, they also unknowingly ruin their own projects.
Here’s the top 6 clients’ characteristics that are bound to bring self-destruction and tear down any decent project:
1. They Know IT All
Design, coding, mutual funds, aerospace engineering, molecular biology… these clients just know it all.
If you offer professional services, you know our pain. We spent years in an industry, do countless courses and workshops, stay up with the latest trends, and learn from the best. We know what works and what doesn’t, because we’ve been there, we’ve done that. We have tons of professional experience working with other people and companies, and we know how to deliver results.
And it’s all for naught when he appears: A client that has a “gut feeling” about his project.
He just doesn’t want to listen. He doesn’t listen to your feedback and he doesn’t listen to common sense.
Design guidelines and principles? Redundant. Following coding conventions? Forget it. He just knows better.
2. They Are Like Freddy Mercury
They want to have it best, fast and cheap.
They want another Uber or Airbnb — a high-quality app with multiple features. But they want it three months from now and it shouldn’t cost too much.
3. They Put Their Princess In A Tower & Guard It With A Dragon
Their business is like a princess from a fairytale that gets locked up in a tower. They’re reluctant to share any information about their business and provide necessary domain knowledge.
They’re secretive about what they do, even though you need this information to perform your job. When you ask questions, you only get vague replies that can’t get you anywhere.
Also, forget about transparency and building trust. You’re their contractor, not a business and technological partner.
Here’s a spoiler to this tale: There is no happy ending.
4. “I don’t need marketing. I’m building something users will LOVE”
They think they have a great idea. They put all their effort into developing and releasing the app, but totally ignore marketing activities that would help the app get discovered. There is no campaign, no strategy, no promotional materials. They don’t generate any buzz and excitement about the app.
They launch their product and they hear crickets chirp.
5. They don’t let the bride choose her wedding dress
Ignoring beta tests and user feedback is like buying a wedding dress for your fiancee without letting her choose. No sane man would do that — that’s simply illogical.
The dress wouldn’t probably be her dream dress and it wouldn’t probably fit her if she’s never tried it on before. The exact same rule applies to apps.
You have to let potential customers test the app so that you can tailor it to their needs and eventually give them something they want and desire. And still, people do the wrong thing all the time — they ignore app users all the way and don’t involve them in the app development.
Sometimes this happens because clients think that the people behind the project know exactly what the users need. But we’re rarely the target market, and we can’t read minds or predict how the users will act.
And basing your app on assumptions that are not tested? It’s like building a car with square wheels without checking if these wheels are going to spin at all.
6. They Communicate So Bad, Even A Toddler Could Do A Better Job.
The headline is ironic and humorous, but there’s no fun when communication with a client is broken. Any successful project starts with effective communication on both ends. Please don’t be one of the people who seem to be disengaged and unresponsive about their own project. Help us & help yourself and don’t take forever to reply. Try to be clear about your objectives and inform us about everything that can impact our work, such as a planned demo with an investor.
Also, make sure you don’t create communication chaos. Too many people involved in the decision-making and no filtering of information that is passed to the development team can be harmful too.
Note: This post is not about any specific person or company. We wanted to bring light to the subject in an amusing way. We hope you have found this article both funny and insightful. If it’s personally relevant to you, please take the hint.