What You Need To Be A CTO • Simon Raik-Allen • YOW! 2018
Interesting. report The topic of responsibility of the CIO from the speaker who worked in both large and small teams. Nice story.
- accompanied by excellent humor
- contains an analysis of the roles of CIO, CTO, VP Engineering Consider the situation in both large and small companies, as well as in consulting It is full of visualizations with Euler-Venn diagrams to illustrate different areas of responsibility, for example, business - executive - engineering - product - clients - board - business. Shows exactly what the CTO does in all of these cases and what it does It breaks down the financial model of a conditional startup and shows why CTO and other engineers need to understand where money comes from and where it goes. Shows what local optimizations look like and why CTO’s helicopter vision is more likely to lead to global optimization As a result, the author summarizes the role of CTO. Steer technology and people towards the medium-term through knowledge sharing and influence And the bonus track at the very end of the speech, the author tells how to communicate with the executive. Don’t speak a technical language, speak a business language. (I recommend reading Technology Strategy Patterns, which we discussed in Code of Architecture.)
- don't say stupid things Have a logical plan to achieve business goals in the area for which a particular executive is responsible
P.S. I also shared a report with a similar topic on Highload. + +
#Management #Leadership #Engineering #Career #Software #SoftwareDevelopment #SelfDevelopment