You’ve learned the basics to responsive typography and you’re ready to implement what you’ve learned into a real project. Now what?
At this point, you might get stuck.
Even though you love the ideas presented here, how do you get your designers and developers to try it out? How do you convince your team that responsive typography is the way to go?
As a freelance developer, I get to interact with different designers, developers and project managers whenever I take on a new project. These experiences have shown me how to present myself and my ideas in ways that allow the team to take me seriously.
In this lesson, I want to share with you a few pointers I’ve discovered. As I go through these pointers, bear in mind that the principles that I’m sharing here works with any team, no matter how sucky the team turns out to be for you.
Communication begins with you
Many designers and developers dislike talking to people. We’re introverts at heart. We’re happy facing our computer, designing and coding, all day long without talking anyone else. That’s why we get into our roles in the first place.
(Kudos to you if you love to talk. Just skip right ahead then).
Unfortunately, I hate to break it to you, but communications is a two-way street. It has to begin with you. You have to be ready to get out of the comfort zone you’ve built for yourself over the years.
It’s going to be hard. You’re going to feel awkward. You’ll want to run away from tensed meeting situations.
But I want you to know that communication is skill. It’s something you can get good at. To be completely honest, I used to suck at communication. I’m not perfect today, but I’m getting better.
So, first of all, you want to open yourself up and be ready to communicate. Stop hiding behind labels like “I’m an introvert”. Stop saying you’re bad with words. Stop saying your ideas don’t matter.
Your opinions are valuable.
It might be hard to believe at first, but your opinions are valuable to your team. That was the first lesson I learned whenever I finally stepped out of my shell and began talking with others.
Chances are, you’re employed in your job because you have something unique to offer. You are knowledgeable in your field, in design, in development or whatever it may be. You have skills that others don’t. And so, you add your unique voice to your team.
Your team needs to hear from you. Step up and talk about your ideas. Share how it will benefit the team. Share why it is important for you. Share how your idea bring your team to a better place.
Some people will agree. Some may disagree. If they agree, that’s great. You get your ideas through. If they don’t, that’s great too, because people get a chance to think through what you’ve just said. This is when communication happens.
If speaking up is too hard for you, think about this: How will you be able to share your ideas if you can’t speak up? How will others know what you’re thinking if nobody hears you? What’s more important? Hiding behind your insecurities or getting your ideas out there so your team does great work that you can all be proud of.
Once you’re ready to let go of your shell and learn to communicate, feel free to move on to the next step.
The key to communication is respect and trust.
If everyone in your team respects and trusts each other, you won’t have a problem with communication. Everything can be shared and discussed openly without an issue.
If you don’t however, that’s when things begin to go haywire. You get a designer hating a developer, a developer harboring murderous thoughts against that same designer, or a project manager treating designers and developers like design and code monkeys.
Don’t be dejected if your work culture isn’t one of trust and respect. You have the power to change it, even if you’re the smallest person in the team.
What you have to do is to get the trust of one person at a time.
That trust begins with respect.
You need to put aside your biases. You need to treat everyone like an adult. You need to see everyone for who they are: unique individuals with their quirks, likes and dislikes and strengths and weaknesses. Like you, they have opinions, fears and emotions and they’re waiting desperately for others to hear them out.
So, hear them out! Ask questions. Find out more about them. Understand their perspective. What made them learn design/development? What made them bring out this “new shiny idea”? More importantly, how do they want you to work with them? (This one solves 99.99% of the conflicts).
Most hateful situations between designers and developer arise because one party doesn’t respect the other enough. They don’t talk enough. That’s why you get situations like designers showing the final mockup to stakeholders before asking developers if the design is feasible. (*facepalm*)
Sometimes, they arise due to bad listening and lack of understanding. Why is your designer chasing pixel-perfectness? Maybe it’s because that’s the hallmark of quality and all they want is to produce good work? ¯\_(ツ)_/¯
Oh yeah. One more thing.
People keep saying designers need to learn to code. Developers need to learn to design. While learning about the other technology is good, you don’t need domain knowledge to communicate.
You don’t need to know how to code, nor design. Likewise, you don’t need pair program, nor be in the same physical space (although they all help) in order to understand and communicate with your team members. All you need is a genuine interest in finding out what the other party think and feel.
Maybe listening to what others think and feel might change your mind about your ideas. Maybe it may not. But either way, it definitely allows you to talk about your ideas in a way they can relate.
Besides, if you genuinely listened to your team mate, they’ll reciprocate and listen to you too (though, sometimes you need to tell them to listen!). Over time, you’ll notice the camaraderie between the two (or more) of you gets stronger.
Managing conflicts
(Eew. Conflicts. *turns and run*)
Well, nothing goes smoothly all the time. Though we hope it never happens, sometimes things just get ugly. You need to learn to manage them too. (This is probably what everybody flees from…)
The best way to manage conflict is to get the two parties involved to talk it out. If you get into a conflict with another person, the best way is to approach the person and ask if they want to talk it out and resolve it between the two of you. (They may not agree to, so be prepared).
If they don’t, you can tell them why resolving the issue between the two of your is important to you. (A genuine reason get things started most of the time).
Next, you want to identify the cause of the conflict. Was it because the two of your disagreed on an idea and one party didn’t listen? Was it because one person got attacked personally? Then, you’ll want to talk it out. Apologize sincerely if you need to.
The procedure to resolving conflicts is exactly the same as understanding a person in the first place. You need to listen, listen and keep listening. Make sure what you’ve gotten from the other person is right on the money by checking in with them at opportune times.
Sometimes, words and communications techniques can help you out, keep you cool and allow you to continue to listen. If you’re looking for books on communication, I highly suggest difficult conversations and never split the difference. These two books will arm you with the framework and processes you need to know about managing conflicts.
Dealing with jackasses
So far, we’ve assumed that everyone is an adult. That’s great. But once in a while, you’ll run into jackasses. They’re people who shit on your face no matter how you try to respect them.
Sometimes, there’s no other way than to bring a manager into the mix. Try to settle the differences between the two of you as much as possible before you bring a manager into the conversation.
Sometimes, there’s no other way than to voice out your problems to a manager (and hope for the best). Before you do so though, try to settle the differences between the two of you.
The manager can’t side with either party, because that’ll make things worse. If you are a manager, you can try to get both parties to talk while you facilitate the communication.
Whatever you do, (as an employee or a manager or whoever you are), don’t say “I don’t care”. This will tell the other party you really don’t give a shit. Then, why should they?
Mindset vs Tactics
Before I wrap up, there’s one final thing I’ll like to say.
If you google around the internet, what you mostly find are tactics to help people communicate with each other. You see things like “put them in the same space”, “be open” and “pair programming”.
These tactics treat the symptoms. It’s not a cure for the problem. They work mostly because people are adults that you can respect.
What happens if they don’t work then? What if you work for a company that doesn’t provide you with these tactics to play with?
In my opinion, what’s important is to learn how to communicate properly with anyone. Learn the mindset, learn the skills, and you can talk to anyone, anytime.
Wrapping Up
Communicating with designers and developers is the same as communicating with anyone. If you feel that talking to your designer or developer is hard, it probably means that you have some biases against him or her that you’re not aware of.
Drop the biases, start to respect and understand them, and you’ll be able to talk about your ideas in a way they can relate to.
If you need help, I highly suggest reading difficult conversations and never split the difference. These two books gave me the steps and processes and words to use to communicate with anyone when I want to.
Good luck! :)
Welcome! Unfortunately, you don’t have access to this lesson. To get access, please purchase the course or enroll in Magical Dev School.
Unlock this lesson