The web touches everything an organization does—marketing to customer service, product development to branding, internal communications to recruitment. This is the era of cross-platform digital services, fast networks, and mobile devices. Sounds like the ideal time to be a person who makes websites.
So why do we feel frustrated so often? Why do we experience burnout or depression? What makes it difficult to do work that has meaning, that satisfies us?
The problem is that we need to collaborate, but we haven’t focused on developing our people skills.
Back in the day, we could get by with technical skills alone. If you could get HTML and CSS to work across browsers, you’d find work, and you might even break new ground. Technical skills still matter, but today making digital services that meet users’ needs also depends on our ability to collaborate across many types of boundaries:
- Disciplines like interaction design, content, front-end and backend development, user research, and product management
- Departments in the organization like marketing, sales, IT, communications, and customer service
- Channels like websites, native apps, social media, print, and the call center
People skills are as difficult to learn as technical skills#section2
Learning people skills is challenging, but when you take the time to develop them, it’ll seem like you’ve gained a superpower—one that allows you to:
- find common ground with people who have different perspectives, like when marketing demands its latest campaign go on the homepage, regardless of the user experience;
- handle stressful situations—like difficult conversations between backend developers and content editors who need to use the CMS—with grace and compassion;
- feel confident about your contributions without criticizing others, e.g., when your product team implements an agile process and you’re concerned that your area of expertise might be sidelined.
Behind each of these scenarios are collaboration problems. Let’s talk about four of the most common ones, and the people skills that can help with each.
- You don’t get appreciation for your contributions.
- You struggle to keep up and know everything.
- You experience conflict with people who are scared of change.
- Your organization can’t adapt.
1. You don’t get appreciation for your contributions#section3
Although it’s counterintuitive, the first person you need to look out for when you want to collaborate is yourself. Everyone needs appreciation for their contributions. When that need isn’t met, we feel frustrated or angry, and we start judging others.
For example, imagine you’re presenting a prototype of a mobile application to your team. They seem to object, saying that the app would take too long to develop and isn’t “intuitive.” Your defensive instinct might be to tell them that they’re wrong—this is the way we “should” do it—while feeling frustrated because they’re rejecting your work. Notice the judgment? These judgmental behaviors lead to conflict, which prevents collaboration.
Learn to communicate without judgment#section4
You can begin to spot this behavior by looking for language that implies people are “bad” or doing things “wrong,” or that tells people what they “should” do. You may also notice self-judgment, where you tell yourself you’re wrong, or that your work sucks. The jargon term is “negative self-talk” and we all do it.
Rosenberg’s Nonviolent Communication (NVC) model helps us identify these moments before they lead to conflict by focusing on four steps: observations, feelings, needs, and requests. You can observe that your colleagues offered “feedback” (rather than “criticism,” which contains a judgment). Then you can identify your feeling, in this case frustration. (If you’re stuck on “angry” or “upset,” try the NVC list of feelings to get more specific.) Next, figure out what you need: is it respect, appreciation, contribution, autonomy, growth? You may have several unmet needs: try this list for ideas.
Finally, put it all together into a request. You could say, “You shared your feedback about the prototype. I’m feeling frustrated because I need appreciation for my contribution. Would you be willing to share areas where the prototype meets user needs, as well as those where it may not?” Notice that you’re taking responsibility for your own feelings and needs.
NVC is difficult to pull off in the heat of the moment, so you need to practice. Get started by reading Rosenberg’s book.
2. You struggle to keep up and know everything#section5
When we collaborate, everyone shares control and no one knows exactly where they’re going. It’s uncomfortable because we’re leaving what we know and stepping into discovery. We need trust to tolerate this discomfort together. When we aren’t confident about our expertise—when we feel insecure—we can’t build trust, so we find collaboration difficult.
People want the “right” answer, the solution with proven return on investment, the fail-safe plan. Whether it’s a fixed budget, the “right” CMS for the corporate website, or the “best” mix of mobile platforms, people are asking you for certainty. You don’t have all the answers, so you can’t offer certainty without faking it. And you’re afraid that your colleagues won’t accept you unless you pretend to know everything. You feel insecure because you have an unmet need for acceptance, and it prevents you from building the trust you need with your team or client.
Learn to coach yourself and others#section6
Instead of feeling insecure, you can choose to tell yourself that it’s okay not to have all the answers, and use coaching techniques to identify both your strengths and the areas you would like to develop. You can also learn to coach your colleagues. This will help you meet your need for acceptance because you’ll be providing real value to them, instead of pretending to have all the answers.
Coaching others means acknowledging that we we can’t “fix” other people’s problems and instead supporting them to make decisions about their own development. This allows us to get real about skills and growth while also being kind.
Get started with the GROW model, which is a structured conversation based on a set of questions. Notice that the coach doesn’t offer their own ideas or fixes:
- Goal: Where do you want to be, and how will you know when you get there?
- Reality: Where are you now? How far away is the goal, and what are the challenges?
- Options: How could you overcome these challenges to get nearer to the goal?
- Way forward: What action steps will you take to carry out your preferred option?
You can both learn to coach other people and ask for coaching yourself. For yourself, this means being honest about the areas you want to develop and being brave enough to ask for help. You can even buddy up with a colleague and coach each other using this tool.
3. You experience conflict with people who are scared of change#section7
The internet is a symbol of disruption for many people: marketers are nervous of the shift from mass media to direct customer relationships, salespeople worry that websites make their skills obsolete, and publishers’ entire business models are threatened by the decline of print. We want to do digital work we can be proud of, but we’re on the front line of this disruption—a front line that’s thick with unmet needs and the feelings they create: anger, frustration, and fear.
Our culture makes things worse. We try to avoid conflict, as if ignoring it will make it go away. We tiptoe around sensitive issues or send long emails that we hope nobody will read instead of engaging face-to-face. We agree to a spec we know will never work, because it seems easier than risking an honest conversation. We choose to avoid “difficult conversations” instead of doing what the project needs.
Learn to turn conflict into collaboration#section8
Imagine a conflict situation: the IT director won’t approve the budget for your new cloud-based web server. Ask yourself what the other person is afraid of. What don’t they know? Why do they perceive the situation differently? To turn conflict into collaboration, you need to listen with empathy.
Listening is a superpower. When you listen to someone with empathy, you meet their need for understanding, which makes them more likely to listen to you. When you see shared humanity—that is, when you realize the person you’re talking to is a human being—you can always find common ground.
Web designers talk about having empathy for users. To overcome conflict, we need to have empathy for our clients and colleagues, too. When our needs for trust and respect are not met, we feel tense, as if we’re about to fight. That makes it difficult to listen with empathy. We can get better with practice. To get started, check out the active listening technique, where you listen, reflect what you heard the other person say, and clarify your understanding.
4. Your organization can’t adapt#section9
Our organizations are structured like industrial factories, with each department separated and optimized, working in isolation. Often digital work seems like diplomacy, as you try to get departments to collaborate instead of fighting over turf. If the team designing the mobile application won’t talk to the desktop website team, what hope do you have? You can’t change your organization’s structure on your own, so why even try?
I’ve fallen into the trap of complaining about culture as a way to avoid leading. If I say, “The culture here is the problem,” that’s a version of, “You’re doing it wrong”—i.e., somebody else needs to change. Change only happens when individuals choose to lead. Even if your organization’s culture is blocking collaboration, you can help it to adapt by leading change on a small scale.
Learn to lead by being honest#section10
You might think that to lead your colleagues through change, you need to present strength, crush opposition, and have a bullet-proof plan. You’ve probably seen managers behaving like this.
But being aggressive is actually a defensive response to feeling insecure. You’re trying to build yourself up by putting other people down. This makes people feel resentful and afraid, which stops them from listening to you.
In her book Daring Greatly, Brené Brown teaches that showing vulnerability is the true indicator of courage. It takes courage to be yourself, to admit that you’re imperfect. If you admit that you don’t have all the answers, people will trust you, and you’ll inspire them to be brave, too.
Being a leader often means being the first person to listen. Share your vision—e.g., designing a digital service that puts users’ needs ahead of organizational structure, and makes a profit too—and listen to your colleagues’ ideas, feelings, and needs. Overcome your insecurity, take a risk, and be brave. It could be as simple as proposing an agile process for your next project, admitting that you don’t know whether it will work, and convincing people to try it by building trust. Or you might bring together a multidisciplinary team from across the organization and work up a minimum viable product, while convincing various stakeholders to trust you. The outcome may surprise you.
People skills are web skills#section11
As the web continues to transform our society—in ways that both excite us and scare us—we need more than new technologies to keep up. We need collaboration.
Now that you understand how people skills can enable collaboration, you have an opportunity to change your work, and perhaps your organization. Invest your time in people skills and you might just change the world.
12 Reader Comments
Wonderful article! Having both technical and people skills is seen as a rare combination, but it doesn’t have to be that way.
In regards to those who are scared of change, and adaptation — if you’re dealing with developers/coders I find that it is also helpful to couch everything as a problem rather than a challenge. Developers are problem solvers, so finding a way to make every difference a study in problem solving engages their creative sense.
Instead of ‘we should use a different tool’, say ‘let’s take an hour and try building something simple with both tools, and figure out which will be better in this case’.
Instead of ‘you didn’t give attention to the interface, it’s terrible’, say ‘nice job on the code. let’s watch someone use the interface and figure out if there are any small adjustments that can be made to improve user performance.’
Make everything a problem to solve, and you’ll find that most developers suddenly become more open-minded.
Very interesting. A lot of this seems to be common sense, but even so, is very hard to implement on-the-spot.
Great concepts here. The internet in general is just a tool to facilitate communication. What is often forgotten is that how we as humans react to that communication is not affected by the means by which it reaches us. I’ve read that over 90% of our communication is perceived by the method in which messages are communicated; it could very well be that effective, productive communication online is that much more difficult because so much more focus is placed on the content of our message – something we have grown very unaccustomed to as society has evolved.
Really brilliant. I’ve read it once and it will again. Sometimes you think that your frustrations, fears and hopes are only yours, while you see other developers (or colleagues, in general) working with confidence. I guess most of us weren’t the Soccer Team Captain back in school. 😀
Insightful! I often feel like I question my own people skills and I love the recommended reading you linked here, but even more your connection to specifically being in the web industry. I’d be interested to hear if you or anyone else has further recommended reading!
I’d also be interested to hear people’s recommended further reading.
I organise a conference about people skills called #dareconf. So perhaps some further viewing (rather than reading) might be the videos of past talks.
Thoughtfull article, people skills are very important if you want to succeed, and to be honest it’s a hard task these days. Thank you!
Technical skills are required to satisfy a demanding market but including it people skills are also essential. People skills are nothing but just some of the rules in which we justify our queries and we try to understand ourselves. People skills include both the social skills and the psychological abilities. Web developers can build applications or software but what if there is always a negative feel regarding what might happen if they won’t accept so here the role of people skills come when you have to think in a positive scenario. One’s skills can lead way to a bright tomorrow.
Technical skills are required for us, i am with deep feelings,because of i am confused in the SEO for the Google ranking for my online business website http://www.replicabagsshoes.com/.
Social skills are everything! I started teaching myself to code April 1, 2014 after switching careers from being a truck driver. If you can’t be an effective communicator then you will have a really hard time in any industry. This coming from a guy that was in one of the most anti social industries out there.
Great article!It is really nice to know that there are others dealing with similar situations, I am not alone. Having people skills as well as technical skills is an awesome combination.We should all work at it! Read more about my website here: http://hubabo.com I teach individuals how to build an online business working from home
Best article I’ve ever read on conflict & collaboration. Thank you, Jonathan. What stood out to me was “Change only happens when individuals choose to lead”. I realize the need to stop complaining about “culture” (which is blaming others as you pointed out), and to simply lead in one small area.
Got something to say?
We have turned off comments, but you can see what folks had to say before we did so.
More from ALA
Personalization Pyramid: A Framework for Designing with User Data
Mobile-First CSS: Is It Time for a Rethink?
Designers, (Re)define Success First
Breaking Out of the Box
How to Sell UX Research with Two Simple Questions