<p>I am evaluating WF for use in line of business applications on the web, and I would love to hear some recent first-hand accounts of this technology.</p>

<p>My main interest here is in improving the maintainability of projects and maybe in increasing developer productivity when working on complex processes that change frequently.</p>

<p>I really like the idea of WF, however it seems to be relatively unknown and many older comments I've come across mention that it's overwhelmingly complex once you get into it. </p>

<p>If it's overdesigned to the point that it's unusable (or a bad tradeoff) for a small to medium-sized project, that's something that I need to know.</p>

<p>Of course, it has been out since late 2006, so perhaps it has matured. If that's the case, that's another piece of information that would be very helpful!</p>

<p>Thanks in advance!</p>

It really depends on what you want to do with it.  I've only used it a little, but compared to more mature products like MetaStorm (I know technically it's a BPM, but there is still a workflow component), Process Choriographer and IBM MQ workflow, there's no comparison.  It's just not mature enough.  On the other hand it's free where the others are not and can probably get the job done.  I don't know if I would place a multi-million dollar operation on it, but with smaller ones, I'd give it another shot.  The real hurdle you are going to face is the change in thought process it requires.  If you don't have developers that have worked with state systems before that can be a real hurdle.