One thing I have not tried, yet seems viable, is instead of frequent 1:1's (which only really matter when there is a personal problem) is something similar to the Oxbridge Tutorial (small group of students sit with Professor and discuss problems at hand.)
I think this approach could hear fruit as it moves the discussion from "how are you feeling" and onto "let's have an open but focused discussion on the problems facing us - not writing code but thinking first and foremost"
When me or my teams think first, things always flow better.
It's rather an indictment of me that I miss it and want to try it again ...
Not the way I am thinking of it. A retro is more what went wrong / right with our interactions in the team or outside team. It's rarely in my experience a technical what if discussion
I am thinking more a way of allowing a single CTO to engage regularly with individuals, less time consuming than 1:1, more free flowing and technically focused - a discussion on what are good or bad or crazy approaches.
Again the main things not to do are give the answers nor set deadlines. That's for the team / coders to do.
I think I see a blog post sized comment coming so will stop now :-)
I think this approach could hear fruit as it moves the discussion from "how are you feeling" and onto "let's have an open but focused discussion on the problems facing us - not writing code but thinking first and foremost"
When me or my teams think first, things always flow better.
It's rather an indictment of me that I miss it and want to try it again ...