The Human Side of DevOps: How to Build Relationships That Drive Results
What would Dale Carnegie Do If Worked in DevOps
“Dealing with people is probably the biggest problem you face, especially if you are in business. Yes, and that is also true if you are a housewife, architect or engineer. Whether you are dealing with customers, colleagues, employees or your boss, you need to know how to get along with people.”
Dale Carnegie
The people side of DevOps can be challenging, but it doesn’t have to hold you back.
The truth is, the ability to build strong relationships and communicate effectively is just as crucial to success in DevOps as it is in any other field.
Carnegie’s principles have stood the test of time and can be applied to any industry, including DevOps.
In this article, we’ll take a journey with Carnegie through his principles and see how they can be applied to the world of DevOps.
Grab these practical tips, so you can use them next time you feel stuck.
1. Don’t criticize, condemn, or complain
First of all Carnegie would strive to create a blameless culture.
This is where, engineers are encouraged to identify problems and mistakes without fear of retribution or blame.
Instead of criticizing a colleague’s work, try to offer constructive feedback that focuses on specific areas for improvement.
If you are frustrated with a colleague, try to approach the situation with empathy and understand that everyone has different perspectives and approaches to their work.
Instead of complaining about a problem, try to offer a solution or suggestion for how to improve the situation.
Avoid using negative language or tone when communicating with colleagues, as this can create a defensive or confrontational atmosphere.
Practice active listening and seek to understand others’ perspectives before jumping to conclusions or making assumptions.
If you are feeling overwhelmed or stressed, try to take a step back and address the root cause of the problem rather than lashing out at colleagues or complaining about the situation.
2. Give honest and sincere appreciation
Carnegie’s principle of showing appreciation is a powerful way to build trust and respect with your team and stakeholders.
In DevOps, appreciation can be expressed through PRs in GitHub or GitLab, where developers can give each other “kudos” or “thumbs up” on their code contributions.
Provide constructive feedback on colleagues’ code contributions, making them feel valued and appreciated.
Similarly, a DevOps engineer might express appreciation for a colleague’s work during a daily standup or sprint retrospective meeting.
3. Arouse in the other person an eager want
Carnegie’s principle of creating a sense of urgency or desire can be applied in DevOps to motivate teams and stakeholders to take action.
When working on a project with a colleague, take the time to understand their goals and motivations. Ask questions to uncover what they are passionate about and what they hope to achieve through their work.
When presenting a new idea or proposal, focus on the potential benefits and outcomes rather than just the technical details. Help your colleagues see how your idea can help them achieve their goals and improve their work.
Show enthusiasm and excitement for the work that you and your colleagues are doing. If you are passionate about your work, it can be contagious and inspire others to feel the same way.
When collaborating with others, seek to create win-win situations where everyone’s needs and goals are being met. Help your colleagues see how working together can benefit everyone involved.
Use positive language and framing when communicating with others. Instead of saying “we can’t do that” or “that won’t work”, try to say “let’s explore other options” or “how can we make this work?” This can help inspire creativity and a sense of possibility in your colleagues.
4. Smile
Carnegie’s principle of smiling might seem simple, but it can be a powerful tool for building rapport and creating a positive work environment in DevOps.
A DevOps engineer might use a video conferencing tool like Zoom or Microsoft Teams to have face-to-face meetings with remote team members, smiling and nodding in agreement to show engagement and support.
And keep your camera on!
5. Remember a person’s name
It is to that person the sweetest and most important sound in any language.
In DevOps, remembering someone’s name can help build trust and rapport. Here are a few techniques:
Try using name association techniques. For example, if you meet someone named “Chris” and they have a beard, associate their name with the famous actor Chris Hemsworth, who also has a beard.
Repeat the person’s name back to them when you first meet them. This not only helps you remember their name, but also shows that you are actively listening and engaged in the conversation.
Write down the person’s name and a brief description of them in a notebook or in your phone after you meet them. This can be especially helpful if you are meeting a lot of new people at once.
Use the person’s name when you speak to them throughout the conversation. This will help reinforce their name in your memory.
Make a conscious effort to remember the person’s name. Sometimes, simply paying more attention and being mindful can make a big difference.
6. Give the other person a reputation to uphold:
Dale Carnegie believed that people will often live up to the reputation that others have of them.
In a DevOps context, this means recognizing and acknowledging the skills and abilities of your colleagues and team members, and giving them opportunities to showcase those talents.
For example, if you know that a team member is particularly adept at a specific tool or process, ask them to lead a training session or share their expertise with the rest of the team.
7. Make the other person happy about doing what you suggest:
Carnegie believed that people are more likely to take action if they feel good about the suggestion or request being made of them.
In a DevOps context, this means framing requests and suggestions in a way that emphasizes the benefits and positive outcomes that will result from taking action.
For example, if you need a team member to implement a new process or tool, you might highlight how it will improve efficiency, reduce errors, and ultimately make their job easier and more satisfying.
8. Ask questions instead of giving direct orders:
Carnegie believed that people are more likely to take ownership of a task or project if they feel that they have had a say in its direction and scope.
In a DevOps context, this means engaging team members in conversation and asking for their input and ideas.
For example, instead of simply telling a team member to implement a specific tool or process, you might ask them what they think of the idea, and whether they have any suggestions or concerns.
9. Let the other person save face:
Carnegie believed that people are often more sensitive to criticism than praise, and that it is important to avoid embarrassing or humiliating others.
In a DevOps context, this means providing constructive feedback in a way that is respectful and non-judgmental.
For example, if a team member makes a mistake, you might avoid publicly calling attention to the error, and instead offer feedback privately and in a way that highlights opportunities for improvement.
10. Praise the slightest improvement and praise every improvement:
Carnegie believed that people respond well to positive feedback, and that even small accomplishments and improvements should be recognized and celebrated.
In a DevOps context, this means acknowledging and appreciating the efforts of team members, even when progress is incremental or slow.
For example, you might use a tool like Jira to track and publicly celebrate every milestone and accomplishment, no matter how small.
Hope Dale’s suggestions help you rock!