When I was growin' up, I was the laziest kid I knew and I knew a lot of people. I'm still one of the laziest devs I know, but I make my deadlines and I know how to code myself out of a job. Your problem might not be OO, but design patterns that contain more layers than lasagna like MVVM or have dependency injection. Another issue might be .NET (assuming its what you work in) I've started playing with python. If you wanted to get stuff done by doing as little as possible as often as possible with maximum results, Python is it.

You shouldn't look at object oriented programming as if you're working with objects. You should look at it objectively.