Use what you're best at.
I've always found it difficult to think the OOP way, even though I use it from time to time. My mind just sees everything as linear steps, and that maps nicely to functional/procedural programming. As long as you understand what you're reading when you see some OOP code, so that you can change it then don't force yourself to use it in other scenarios just because you may feel pressured to.
I've been writing some assembly language over the past month and I had forgotten how satisfying it is to be completely unencumbered by object structures. All languages eventually end up as opcodes, and you won't find any notion of objects at that level. It's all procedural.
I think the biggest problems are that people really suck at explaining OOP and people are often really, really, really bad at it, and then...