๐๐ผ๐ ๐๐ผ ๐ฏ๐๐ถ๐น๐ฑ ๐ต๐ถ๐ด๐ต-๐ฝ๐ฒ๐ฟ๐ณ๐ผ๐ฟ๐บ๐ถ๐ป๐ด ๐๐ฒ๐ฎ๐บ๐?
1
๐๐ผ๐ ๐๐ผ ๐ฏ๐๐ถ๐น๐ฑ ๐ต๐ถ๐ด๐ต-๐ฝ๐ฒ๐ฟ๐ณ๐ผ๐ฟ๐บ๐ถ๐ป๐ด ๐๐ฒ๐ฎ๐บ๐?
We are all working in teams and our daily work and the results depend very much on the internal happiness of the teams. As the team is happier, they will be more productive and stay more in your company. But, how to build such teams?
The first step in building a great team is building ๐๐ฟ๐๐๐ inside. And this is important because we want to build psychological safety where people will not fear failure and be encouraged to experiment. Such teams need autonomy for their software engineers. To do this, we need to build a such culture in our company.
One way how we can build a culture where success is not the only rewarding factor, but ๐ฒ๐ ๐ฝ๐ฒ๐ฟ๐ถ๐บ๐ฒ๐ป๐๐ฎ๐๐ถ๐ผ๐ป too, is to build a product and entrepreneurial mindset with our people, where experimentation is rewarded. We can do this by creating an environment to motivate people on that path.
But some could argue, how we could know if our team is happy and productive? I'm not a big fan of surveys, they may be only a starting point, but you need to go and know your people very well. How we can do this? The best way is to ๐น๐ฒ๐ฎ๐ฑ ๐ฏ๐ ๐ฒ๐ ๐ฎ๐บ๐ฝ๐น๐ฒ, invite people for lunch, ask them something personal, and remember what is important to them, and how they feel about different stuff. Share your things also with them. And don't forget to reward initiatives from your people, such as starting a community of practice or being proactive.
We should also encourage ๐ผ๐ฝ๐ฒ๐ป ๐ฐ๐ผ๐บ๐บ๐๐ป๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป, ๐ณ๐ฒ๐ฒ๐ฑ๐ฏ๐ฎ๐ฐ๐ธ ๐๐ต๐ฎ๐ฟ๐ถ๐ป๐ด, ๐ฎ๐ป๐ฑ ๐๐ฟ๐ฎ๐ป๐๐ฝ๐ฎ๐ฟ๐ฒ๐ป๐ฐ๐. In this way, teams could work more and be more productive. With this, you need to have regular people sync and share information during all-hands meetings. Teams also need to have clear ownership, mission, and vision. The mission could be "Build the best online experience for your customers".
One of the ways how you can make your developers happier is to make it a less frustrating developer experience. This can be done by ๐๐ฒ๐๐๐ถ๐ป๐ด ๐๐ฝ ๐๐ฎ๐ฟ๐ถ๐ผ๐๐ ๐ฝ๐น๐ฎ๐๐ณ๐ผ๐ฟ๐บ ๐๐ฒ๐ฎ๐บ๐, that could reduce developer churn (take a look at the book "Team topologies").
What worked for you and what not? What do you find that motivates your people?
{{IMAGE_0}}
2
Source: my newsletter issue "Building High-Performing Teams":
3
Every week, 50,000+ engineers and tech leaders get actionable insights on building great careers, teams, and software products. Join us here: