I just checked out that article. That task focused vs. object focused example clearly illustrates the difference. When implementing designs, programmers do not start with "wash", they start with "dog" and then add "walk" or "color" in relation to the dog. Then that dog's relationships are not to "walking" but to "owner", etc. The point is, there are several walls between disciplines in a UCD UX process, and part of it might be due to specialization, but part of it is due to the fact that the researchers and designers are thinking in terms of tasks and the programmers, who come at the end of the process, are thinking in terms of nouns/objects. There is somewhat of a conflict in perspectives.
Anyway, I'm really trying to explore this topic and build upon it so I appreciate any input anyone might have. I'll be presenting at UXPA in Seattle at the beginning June and I'll be working some aspects of OOUX into my presentation. And, after that, I hope to continue to explore the topic of OOUX in other ways. I'm really hoping to expand on methodologies that can be employed throughout the UCD process. So you may be hearing more from me in this forum.
I recently finished the Dave Collins book referenced in the article you referenced. Also, these are really great:
Object-Oriented UX · An A List Apart Article
OOUX: A Foundation for Interaction Design · An A List Apart Article
But beyond the Dave Collins book, those two articles in A List Apart, and the article you posted, there just isn't a lot out there on this topic. I'm hoping to do what I can to change that.