K2.Net

I would respectively have to disagree with the previous poster. I've used K2.net at several clients with very complex workflow requirements and the solution has been able to meet those requirements without much, if any, additional coding. I've certainly never contemplated writing my own workflow engine.

I've seen these types of comments before and it can typically be tracked back to a lack of experience or training with the tools. I also see it from people that like writing code or using more complex tools like BizTalk or other EAI tools that were never meant to provide human workflow capability (...has anyone ever seen a successful implementation of BTS HWS?). Somebody who wants to write code will come up with reasons to write code. IT resources that want to provide real value to their organization will focus on building solutions that solve business problems not building their own workflow engines.

The remarks regarding Microsoft's human workflow solution (...not sure if you're referring to WF or MOSS Workflow) show a lack of understanding not only about the space, but about the capabilities of that offering. Low-level best describes WF and entry-level best describes MOSS workflow. From what I've seen in the WF and MOSS betas, K2.net's current offering goes well beyond what Microsoft will deliver next year and I've seen some demos of their next offering, code-named BlackPearl, at some recent MS events and all I can say is WOW!

In regards to the original posting on this thread, I see a huge opportunity for K2.net skilled resources and regularly get calls from head-hunters and search firms looking for resources with this skillset. I think it could be especially lucrative if you were willing to be a road warrior.