In my experience (of having my office 2-doors down from the CEO of a minor public company), most of his “work” was just meetings with other CEOs and execs over breakfast, lunch, dinner, golf, etc to discuss business deals, acquisitions, and such. Not sure how an AI could do that, as it was mostly a social/class/nepotism thing.
Market the company and, for smaller companies that want funding, beg and network.
Leadership is often removed from how work actually gets done. This is part of why they often make bonkers decisions.
They don’t understand that most of the time isn’t going into typing code into the computer. It’s figuring out what the product guy and CEO actually want. It’s pulling answers out of them (eg: what do you want to do if the user’s name is null?) or dealing with it when they don’t like your decision (eg: you didn’t say what to do when I don’t have their name, so the email just says “hey”. I really don’t think this is a crisis)
So much the last bit! I can’t count the number of times our CEO has either sent a mail or created an issue (very small company) with something along the lines of “X is broken”, when what they mean is “I don’t like the design choice behind X.” Like, whatever they’re complaining about is completely functional, it just doesn’t work exactly the way they envisioned it. When explaining why it can’t (or shouldn’t) work exactly the way they envisioned, there’s maybe a 50 % chance that “X is broken” turns into “oh, I hadn’t thought about that”.
What exactly do CEOs do, anyways?
In my experience (of having my office 2-doors down from the CEO of a minor public company), most of his “work” was just meetings with other CEOs and execs over breakfast, lunch, dinner, golf, etc to discuss business deals, acquisitions, and such. Not sure how an AI could do that, as it was mostly a social/class/nepotism thing.
Usually some new chick in marketing.
Make shitty decisions, like letting AI make decisions.
Market the company and, for smaller companies that want funding, beg and network.
Leadership is often removed from how work actually gets done. This is part of why they often make bonkers decisions.
They don’t understand that most of the time isn’t going into typing code into the computer. It’s figuring out what the product guy and CEO actually want. It’s pulling answers out of them (eg: what do you want to do if the user’s name is null?) or dealing with it when they don’t like your decision (eg: you didn’t say what to do when I don’t have their name, so the email just says “hey”. I really don’t think this is a crisis)
So much the last bit! I can’t count the number of times our CEO has either sent a mail or created an issue (very small company) with something along the lines of “X is broken”, when what they mean is “I don’t like the design choice behind X.” Like, whatever they’re complaining about is completely functional, it just doesn’t work exactly the way they envisioned it. When explaining why it can’t (or shouldn’t) work exactly the way they envisioned, there’s maybe a 50 % chance that “X is broken” turns into “oh, I hadn’t thought about that”.