But what I found out after a few years was people don't care that much if you're always right. What they care about is that you make mistakes, that you admit mistakes. It is hard to admit mistakes when you are a manager, but you need to do this, because every manager builds culture by example.
You cannot create a culture, if you, yourself, can't become vulnerable. And first of all, you should "over-communicate" expectations, you should always communicate what you are doing.
Now weekly calls for me are an opportunity to show the whole team what is going on in the company, in different teams, and what is going on with myself, what I'm doing here, what went wrong, and what I learned from that and how it can help them.
You should be ready to be vulnerable yourself. And in my case, as an engineer, when I started out with this startup, I didn't know many things like how to do the architecture right, what kind of frameworks to use. And over time, we collected the big legacy, big technical depth, mostly because of my code. Of course, now my engineers see that something is wrong. They can ask why this stupid technology was used. And I can be silly with this and say "That was the best option. I think this is still the best framework in the world." But I want to be honest with my team and myself, I want to be able to say "Hey, guys, we have a situation where we need to act fast and fix something that has worked up until this moment. Yes, it wasn't the right solution for long term, but now I have you and you have more experience, so now we can make this right."
And when you do this, you set an example and then people are also ready to find solutions that work right now, and they know if something goes wrong, it won't be a situation of blame.
I find it really great to speak about group goals when we want to make some decisions. For example, one of the decisions that we are working on right now is our technical roadmap for this year. Obviously I have a lot of ideas about what I want to see in our product, in our technologies stack, but the truth is I don't use this technology on a daily basis. There are other people who will use the process that they should come up with, not that I should dictate everything like "This is the process you should use, because I like it." So instead of a list of tasks, they should do, sometimes it's better to ask, "What do you want to see?". And it completely changes the way you plan things, how you do communications.
A couple of months ago, I heard the joke that some company decided to reduce the number of managers they have. So they sent all the managers to a remote island and said to them: "You should continue to do your daily job. You'll be on this island for months, then you'll come back and we'll see what's happened with your teams."
So one month passed and there were teams that started to perform worse. There are teams that become better without a manager. And there are teams that changed not so much. Definitely, the team's performance was highly dependent on their presence.
And after I heard this joke, I learned that actually, that is one of the practices in Japanese companies when they take over all of their management, send them on a sea cruise and then see what happens with the teams. So they understand if the manager doing a great job or not. And honestly, my job here as a CTO, as a co-founder, is to make sure that the company can exist without myself.