tgroenwals shared this post ยท 20h ago
Dr Milan Milanoviฤ‡

๐—›๐—ผ๐˜„ ๐˜๐—ผ ๐—ฏ๐˜‚๐—ถ๐—น๐—ฑ ๐—ต๐—ถ๐—ด๐—ต-๐—ฝ๐—ฒ๐—ฟ๐—ณ๐—ผ๐—ฟ๐—บ๐—ถ๐—ป๐—ด ๐˜๐—ฒ๐—ฎ๐—บ๐˜€?

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":

https://t.co/Z7HVooOiIh


3

Every week, 50,000+ engineers and tech leaders get actionable insights on building great careers, teams, and software products. Join us here:

https://t.co/q02IQfHewG

Aakash My developer experience survey would be one question: can you roll back at 2am without waking the one person who knows the Jenkins job? If not, I'd fix that first lol. Yesterday