Ask HN: Autonomy vs. QC

I'm a first time team lead and I'm struggling to come up with a good process for my team. The nature of the work is very independent: each developer is responsible for a project from requirements gathering to deployment. There's only 2 of us right now, but we'll be growing soon so I want to iron this out.

On a project basis, I've found a good balance of being involved with specs. I'm struggling to find a way to be involved with the code itself though. There needs to be some form of code quality control. At the same time, I need a way to teach technical skills to my new hires.

I've thought about code reviews, but with 1 dev per project, that could get personal and wouldn't identify bigger problems until it's too late. If I scheduled code reviews weekly, that seems a little micromanagement to me, but it might be necessary.

There is a subtext of under performance and trying to correct it, but I feel like once I put a process in place, the path to improvement will be easier to see.

Any thoughts or experience?