We all have been through this, right? In my case I have been through this kind of conversations several times in my career working in product companies either as consultant or as an employee.
A company grows, the product evolves and suddenly the crises happens. At least, that is what they say. The reality though is something different, as the company becomes successful, the company misses its priority, often giving step-motherly treatment to the very software product that is feeding them the millions of dollars.
I have witnessed a lot of companies being run without a CTO hoping to magically solve their problems and it has only been a matter of time for them to hit a road-block that they are unable to surmount.
And then there are those companies that I have witnessed to have hired wrong person as a CTO. This person ends up being a bad (not bad-ass) CTO. So what makes a bad CTO? The following are some of the things that I have had witnessed first-hand on things that a CTO does only to fail a company miserably: