Funny memory, at a startup weekend in a team as the only technical resource. Had my headset on but wasn't listening to music... was somewhat amusing as everyone passed out C letter titles for an idea that wasn't even implemented. Took my headset off when someone claimed CTO "CTO huh? What am I doing right now?... Oh you don't actually know? You want to be the CTO but you don't know what your only engineer is doing?" Walked off after that.
Minimize use of CxO titles at early company stages
21–30 of 35 posts
Re: Minimize use of CxO titles at early company stages
#22Earlier quoted context omitted.
Most successful VCs are not so willing to risk their investment by putting incompetent people into executive positions. The fact is that often the lead developer who builds the first version of a product does not have the skills and experience to be the CTO as the company grows. The first salesperson may well not be ready to build a sales team. The accountant might not have the breadth to be a CFO. In addition to mon…
The fact is that often the lead developer who builds the first version of a product does not have the skills and experience to be the CTO as the company grows. Ok, I admit I've never even worked at a startup, so perhaps I'm missing something, but this idea just smells fishy. Why on earth would the lead developer who built a software product from the ground up, possibly single-handedly, not have the "skills and experi…
I agree with what Michael said and would add that the CTO role encompasses far more than just development. A good CTO needs to understand product management, business development, and sales. He or she has to be able to present to customers, partners, investors, and the board. Managing a growing team is also part of the role, as is balancing business and technical demands. It's possible that your PHP hacker co-founder can do all that, but your VCs just might know someone more qualified.
Re: Minimize use of CxO titles at early company stages
#23Earlier quoted context omitted.
I think that his argument is that, as the job of CTO becomes more of a management/connections role, it's better to have someone else in it. I actually agree. The right people to build a business are often not the right people to maintain it at maturity. I'd want the title of "CTO" if building someone's product, but I would agree to abdicate it if I agreed with the choice of successor, and was genuinely convinced he'd…
Right, the key distinction being that in your scenario, the title change is entirely voluntary, and even beneficial from the perspective of the technical co-founder, because he wants to continue working on the codebase rather than having his time taken up by all the politician duties that C*O roles entail. I think in the OP, it seemed like more of a "you shouldn't let your first developer be the CTO because you want…
"Repulsive" needs some logical support. If your first developer lacks the necessary skills, it doesn't make sense to put the company at risk by setting him or her up for failure.
Re: Minimize use of CxO titles at early company stages
#24If they're not a rockstar, I'd make the case that they're your "development head / lead". How do you even know if your lead developer is a "rockstar" or not--especially if you're the non-technical co-founder? Are you supposed to give him/her coding tests? The term "rockstar" needs to die, now. It's a meaningless mumbo-jumbo term invented by someone who didn't understand what developers do.
I absolutely hate these meaningless titles. I just started work in the corporate world. After a month I literally want to kill myself.
We use the following terms:
To do items -> ACTION TASKS!
Manager -> Champion.... groan
Meetings -> "Social". As in, "in ten minutes, we're having a social in room 10D.
Cooworker -> Friend.
We have to use these terms, there are so many more, that combined with the fake forced "i love to work here" attitude day in day out is absolutely crushing me.
Re: Minimize use of CxO titles at early company stages
#25If they're not a rockstar, I'd make the case that they're your "development head / lead". How do you even know if your lead developer is a "rockstar" or not--especially if you're the non-technical co-founder? Are you supposed to give him/her coding tests? The term "rockstar" needs to die, now. It's a meaningless mumbo-jumbo term invented by someone who didn't understand what developers do.
I absolutely hate these meaningless titles. I just started work in the corporate world. After a month I literally want to kill myself. We use the following terms: To do items -> ACTION TASKS! Manager -> Champion .... groan Meetings -> "Social". As in, "in ten minutes, we're having a social in room 10D. Cooworker -> Friend. We have to use these terms, there are so many more, that combined with the fake forced "i love…
Don't forget Leaders!
In Manager -> Leader in the HR context and then the Leader -> Champion in the project management context.
Re: Minimize use of CxO titles at early company stages
#26Ha! This is great, it looks as if this article was written for Soylent Corporation. I personally hope their company succeeds, to the point where they're going to have some awkward title changes. :)
Re: Minimize use of CxO titles at early company stages
#27Funny memory, at a startup weekend in a team as the only technical resource. Had my headset on but wasn't listening to music... was somewhat amusing as everyone passed out C letter titles for an idea that wasn't even implemented. Took my headset off when someone claimed CTO "CTO huh? What am I doing right now?... Oh you don't actually know? You want to be the CTO but you don't know what your only engineer is doing?"…
Startup weekend is probably one of the last places on earth to find legit entrepreneurs/founders. I've been to 2 and never will be going again- such a mental drain to accomplish so little.
Re: Minimize use of CxO titles at early company stages
#28If they're not a rockstar, I'd make the case that they're your "development head / lead". How do you even know if your lead developer is a "rockstar" or not--especially if you're the non-technical co-founder? Are you supposed to give him/her coding tests? The term "rockstar" needs to die, now. It's a meaningless mumbo-jumbo term invented by someone who didn't understand what developers do.
I absolutely hate these meaningless titles. I just started work in the corporate world. After a month I literally want to kill myself. We use the following terms: To do items -> ACTION TASKS! Manager -> Champion .... groan Meetings -> "Social". As in, "in ten minutes, we're having a social in room 10D. Cooworker -> Friend. We have to use these terms, there are so many more, that combined with the fake forced "i love…
Let's not foget this gem:
Figuratively -> Literally
Do people in your company use "Social" to mean a conversation about business topics? A "social" is people eating/drinking and chatting informally to get to know each other.
"Champion" is not a "manager". A champion is someone who cares about a project and fights for it. Someone assigned to maange a project might not be a champion -> will neglect it and let it die.
Re: Minimize use of CxO titles at early company stages
#29Ha! This is great, it looks as if this article was written for Soylent Corporation. I personally hope their company succeeds, to the point where they're going to have some awkward title changes. :) https://campaign.soylent.me/soylent-free-your-body
Proposed new titles:
Founding team: Soylent Red
New hires: Soylent Green
Re: Minimize use of CxO titles at early company stages
#30Earlier quoted context omitted.
I absolutely hate these meaningless titles. I just started work in the corporate world. After a month I literally want to kill myself. We use the following terms: To do items -> ACTION TASKS! Manager -> Champion .... groan Meetings -> "Social". As in, "in ten minutes, we're having a social in room 10D. Cooworker -> Friend. We have to use these terms, there are so many more, that combined with the fake forced "i love…
Don't forget Leaders! In Manager -> Leader in the HR context and then the Leader -> Champion in the project management context.
I have 3 months left at this internship at which point I'm going to hermit and develop my own shit for the next year. I just need to stick this out since it pays a fat paycheck, funding my food and rent.