“(i.e. Wikis have terrible workflow”

I have to disagree with you there - the point of a wiki is not to have workflow in the traditional sense. If you need workflow, there are other tools that do a great job providing it. A wiki is there to help a group of people who work on something together from the start, and therefore don’t need workflow, approvals, etc. because they’re seeing changes as a result of being subscribed to the wiki page to watch those changes, and making subsequent revisions as they see fit.

Tools that provide workflow (i.e. some CMSs, Intranets, etc.) and wikis are providing two different types of functionality that meet different needs. I think it’s a mistake to confuse the two and conclude that wikis provide poor workflow. :)

Regards,
Stewart
Regards,
Stewart

While there are some conceptual similarities between MindTouch and Jotspot these are only skin deep. The architecture of MindTouch Deki is dramatically different from JotSpot: http://mindtouch.com/Technology and, of course, JotSpot was closed source and targeting consumers and small businesses.

PS- Thanks for the write up…

So, as portals (wikis, etc.) become more like workflow engines and BPM/BPA tools develop better web portals what’s the best balance? Seems like doing both is a mistake. (i.e. Wikis have terrible workflow and BPMS have terrible interfaces.)
??

but maybe veneerware’s time has come.