That might be the case in the short term, but a lot of the time that apparently more-complex, testable solution winds up being more flexible and easier to change than the not-testable one that almost certainly is harder to test because it introduces tight coupling. But if this isn't self-evident to your team, likely they weren't deriving the full benefits of tests on their code anyway.