Clean architecture vs pragmatic architecture: where's the line?

our team's been really leaning into clean architecture principles lately, which is great for theoretical purity and testability. the challenge we're running into is the overhead, especially for what should be simple CRUD operations. we're ending up with maybe 5-6 files just to handle a basic request: controller, use case, interface, repository interface, concrete repository, and entity mapping. it feels like a lot of boilerplate for a simple 'create user' endpoint. my previous team was much more pragmatic, often just having a controller and a service layer directly talking to the ORM, and we were shipping features a lot faster. i'm struggling to find the right balance here. how do others decide where to draw the line between architectural purity and just getting things done efficiently, especially in a fast-paced environment where requirements change frequently?