Recently an Enterprise Architect for a large bank in Canada asked me what I thought about using BizTalk for to centralize human workflow. His goal is to centralize this functionality as much as possible. This is a great idea but there are many challenges to this.
If you refer to my previous post I describe many of these issues indirectly though unstructured vs. structured data. The theme applies here as well.
I would encourage you to take a look at an MSDN article I wrote on this topic, you can find it at:
Architecting Enterprise Loan Workflows and Orchestrations
The following article echoes a lot of my thoughts from a rules and separation perspective:
http://www.edmblog.com/weblog/2005/11/biztalk_windows.html
For a developers aspect there is a good deck:
