Starting new role as senior manager – I want to change the way how team builds software – I need your feedback.

Intro:

I am a developer with 15y of experience, with some management experience. I'm starting new senior management role soon.

Observation:

Through my career I've seen many ways which tried to make software good in a systematic way (scrum, TDD, code reviews, and more) yet there's always a way to make a spaghetti/big ball of mud.

My conclusion is pretty simple: no amount of processes, policies, methodologies and 360 feedbacks will ever work, if no major emphasise is put on code quality. Do you agree or not?

Plan:

As a senior manager, I want to make sure my engineers can (and will) write clean and readable code. Meaning I want to promote those who do this, and let go those who can't write clean, readable, well structured solution.

Example 1: If someone shows me 100% code coverage, but tests are one big messy code – I'll consider it as a disadvantage of that developer (despite coversge metric is met).

Example 2: if team delivered a feature but code is unreadable by others – it's not considered "done".

Example 3: if CodeReviews are accepted without any comments, I'll consider it as clumsy and lazy work.

Question:

Do you think that emphasising code quality will be a good startegic move? Or rather as a senior manager I should focus on higher metrics and business value and peoples matters?