4 ms·
As with others, not a CTO, but an architect for many years, and I know the perspective I'd start out with, which is that the biggest problem at the CTO level is
by jerf 8y ago
As with others, not a CTO, but an architect for many years, and I know the perspective I'd start out with, which is that the biggest problem at the CTO level is the mismatch between the people making decisions about what we work on next, which once you are no longer a 3-5 person start up is not the developers, and the people who understand where the technical debt is and what could be done about it.
Transferring the knowledge across that gap is very difficult, perhaps virtually impossible, because both sides of that transaction have a lot of incentives to mangle the message in the process.
The manager who is deciding what to do, and likely incentivized one way or another based on features, uptake, performance, etc. is going to always be very biased in favor of providing more to the customer, and will want the developers always visibly working on something that provides visibly more to the customers. They don't want to hear about why we need to rewrite this thing for no customer-visible change except maybe "fewer bugs", and probably don't want to hear about why the project is slower than expected ("just fix it! but without any additional resources") or what could speed it up.
The engineers have even more complicated problems. First, the engineer may not be able to correctly determine what technical debt even matters if they are not properly kept in the loop about where the product is going. That is, bad code on a feature we're about to dump or obsolete is way less important than on a core feature. Keeping engineers in the loop about future product directions seems to be a big challenge. (I mean, I've seen it done successfully, but it takes a lot of effort. It's just so easy for the manager to go to some four hour meeting with the CEO and the board about the product and all that ever gets back to the team is "We need feature #64." I mean, OK, great for distilling those 4 hours down to the next action item, but at least your senior engineers really could use a bit more guidance about where the product is going.) Second, the engineer is likely to have a personal connection to the code, which can have any number of effects ranging from being defensive about any suggestion that the code is less than perfect, to believing that everything, everywhere is "technical debt" and really needs to be rewritten.
To properly gauge the technical debt on a project takes an almost perfect merger of both the business side of the project and full engineering knowledge of the project. It's harder than even spec'ing out a new feature by far. I don't know that I've ever seen a great solution for this; the requisite bits of knowledge are structurally very hard to bring together.
(This is written from the assumption that technical debt is in fact a big problem. There's a distinct possibility that it really isn't, but I'm answering the question as written. In general if I was starting a new CTO job at anything but a very established software company, I would be surprised and pleased if "technical debt" really was my biggest problem, and not flawed processes, broken cross-team communication, or goodness forbid but all too likely, internal team communication.)