> it looks like Hephaestus wanted to leave a "way back" to the org
100% sure no on that one.
> Who is the CTO now, you or Koalemos?
Technically - neither. He's "Head of tech" but people have started skirting him and going to me directly instead because he always says he doesn't know and has to talk to me on essentially every topic.
> I'm not surprised Koalemos did it their way. Unless there was a really strong reason about not doing it, why that person cannot do the job their way?
From my understanding because it did exactly what Hephaestus foresaw - things breaking.
> What's bad about it?
Another option could have been to reset the password for the old CTO and then occasionally check their inbox.
Seems like there happened a misscommunication, there are 3 ppl in the org that could be perceived CTO.
1. You
2. The old CTO that wants to keep their inbox
3. The guy hired for the job.
You need to talk to founder to let them decide.
Another thing is - if you hire new people and they didnt finish the onboarding yet, things will be breaking, thats the circle of life.
If the new guy is expected to know these things or he repeats the same mistakes - then he is not meeting expectations and should be let go.
I think you three need to have a candid conversation about the expectations, maybe include a founder who can be a tie breaker.
Definitiely, such a mess in so small org increases the potential of failure drastically.
> Who is the CTO now, you or Koalemos? Technically - neither. He's "Head of tech" but people have started skirting him and going to me directly instead because he always says he doesn't know and has to talk to me on essentially every topic.
> I'm not surprised Koalemos did it their way. Unless there was a really strong reason about not doing it, why that person cannot do the job their way? From my understanding because it did exactly what Hephaestus foresaw - things breaking.
> What's bad about it? Another option could have been to reset the password for the old CTO and then occasionally check their inbox.