Or you could use a language that uses object orientation in a more natural way, such as Ruby and Scala, which both are fundamentally OO languages.
You can do procedural-y things with both languages, much to their credit, but packaging up functionality is both natural and intuitive.
Over building APIs is not a hallmark that Objects are bad. They're a hallmark of bad design.
So, yeah, i agree, prototype a minimal solution and iterate, and teach others to do this. This is an issue that is orthogonal to object orientation. At least, it is in languages that don't make you jump through weird hoops (C++ & Java, i'm looking in your general direction).
You can do procedural-y things with both languages, much to their credit, but packaging up functionality is both natural and intuitive.
Over building APIs is not a hallmark that Objects are bad. They're a hallmark of bad design.
So, yeah, i agree, prototype a minimal solution and iterate, and teach others to do this. This is an issue that is orthogonal to object orientation. At least, it is in languages that don't make you jump through weird hoops (C++ & Java, i'm looking in your general direction).