The 10 Most Common Mistakes of First-Time CTOs, #7 and #8
- Sergio Visinoni from Sudo Make Me a CTO <makemeacto@substack.com>
- Hidden Recipient <hidden@emailshot.io>
Hi, 👋 Sergio here! Welcome to another free post from the Sudo Make Me a CTO newsletter. If you prefer to read this post online, just click the article title. As this is a free newsletter, I do immensely appreciate likes, shares and comments. That's what helps other readers discover it! The 10 Most Common Mistakes of First-Time CTOs, #7 and #8I've made most of these mistakes myself, and see people following the same path over and over. Don't let these mistakes limit your ability to have impact in this role.
Today's article is the fourth in a 5-part series in which I share the ten most common mistakes I see first-time CTOs make and ways to avoid them. If you found this article and would like to read the series in order of publication, jump to the bottom of the page, where you'll find a link to the previous articles. Today's mistakes examine common issues with ego getting in the way, making us believe we must have all the answers to prove our worth. I hope you'll find this helpful and actionable. Let's get started! #7 Trying to be the person with all the answersAt this level in the organization, you're not supposed to have up-to-date information on everything happening at every moment or know how to fix every issue your team faces. It's OK sometimes to answer “I don't know" when a peer in the executive team or a member of the tech organization asks you a question.
To overcome the fear of looking incompetent by saying I don't know, combine it with a commitment to finding the answer and taking action to follow up. As you do this consistently, people will develop a lot of respect for your professionalism. For example, when facing a question from a peer for which you don't think you have all the details, you can say I don't know, but I'll check with the team, and I'll get back to you by tomorrow's EOD. Then, take note of the action, follow up with the team, and get back to the person within the agreed-upon time frame. There is no shame in recognizing that our knowledge is limited and accepting that things on the ground can move faster than you can keep up with. Normalize the acceptance of partial knowledge and make it a starting point of an investigation rather than the final point of an awkward conversation. #8 Not asking for help.Being in the C-suite can be a lonely journey. Your peers are not experts in the same domain as you are, and you don't feel comfortable asking for help from other team members.
There is one thing that will help you get rid of those old beliefs about asking for help. Asking for help is a powerful way to build trust with people.¹ When you ask people for help, you're signaling two things:
If finding someone to ask for help within your organization can be challenging, you can consider other options. The first one is to reach out to fellow practitioners. Find Slack communities and meetups, or contact people you know and exchange ideas with them. The second one is to engage the support of a professional mentor and coach, someone who has gone through similar pains and who can help you gain more clarity on your role and course of action. I wrote an article on the merits of mentoring. You can find it here if you want to know more about my views on the topic. Today, I described two more of the ten most common mistakes I've seen first-time CTOs make. Your situation might resonate with some of them, and you might struggle with other aspects I didn't cover here. Each case is different, and generalization can help us start thinking about our case from an outside perspective. I hope you enjoyed today's article. See you next week! Previous articles in the seriesIf you want to read the previous article in this series, you'll find them here. If you found this valuableIf you found this valuable, here are other ways I can help you and your company:
1 Brene Brown did exciting research on the topic and found that for most people, what made them trust others was when they were asked for help. I could not find the paper from the research online, but it's mentioned in multiple places. Brene Brown puts that under the nonjudgement part of her Braving Inventory, which is discussed in more detail here. You can find more about Brene talking about it in this speech transcription. Sudo Make Me a CTO is a free newsletter edited by Sergio Visinoni. If you found this post insightful, please share it with your network using the link below. If you or your company need help with one of the topics I talk about in my newsletter, feel free to visit my website where you can schedule a free 30 minutes discovery call. I'd be delighted to investigate opportunities for collaboration! |
Similar newsletters
There are other similar shared emails that you might be interested in: