Comments on: Workflow 2.0 http://libraryclips.blogsome.com/2009/03/23/workflow-20/ sharing ideas thoughts and feedback Sat, 28 Nov 2009 15:50:33 +0000 http://wordpress.org/?v=1.5.1-alpha by: John Tropea http://libraryclips.blogsome.com/2009/03/23/workflow-20/#comment-32875 Sun, 29 Mar 2009 07:47:59 +0100 http://libraryclips.blogsome.com/2009/03/23/workflow-20/#comment-32875 Thx Samuel, I do have some tasks which I coordinate with a blog and wiki, but the blog and the wiki are not related in a explicit workflow. If someone else came along they would not see the workflow...they would not see any connectors, and if they interacted they would not get a prompt that instructs them to move from one to the other. Web 2.0 is great to design the components, and make them flexible to suit our needs, but now we need to connect them into a process. I kind of want to crystallise what I'm doing informally, so an outsider can understand. Thx Samuel,

I do have some tasks which I coordinate with a blog and wiki, but the blog and the wiki are not related in a explicit workflow. If someone else came along they would not see the workflow…they would not see any connectors, and if they interacted they would not get a prompt that instructs them to move from one to the other.

Web 2.0 is great to design the components, and make them flexible to suit our needs, but now we need to connect them into a process.

I kind of want to crystallise what I’m doing informally, so an outsider can understand.

]]> by: Samuel http://libraryclips.blogsome.com/2009/03/23/workflow-20/#comment-32868 Fri, 27 Mar 2009 16:23:39 +0000 http://libraryclips.blogsome.com/2009/03/23/workflow-20/#comment-32868 This is very interesting, John. Sharepoint has very basic workflow features. Could you use their workflow features for workflow management between wiki's and blogs? This is something I'm working on in the company I work for. We have heavy, formal tools to manage product data. These tools are very good at relating data/information, managing changes/workflow, etc. Typically stuff that web 2.0 tools are usually not so good at. I'm wondering if we could combine these two worlds in some way. This is very interesting, John. Sharepoint has very basic workflow features. Could you use their workflow features for workflow management between wiki’s and blogs? This is something I’m working on in the company I work for. We have heavy, formal tools to manage product data. These tools are very good at relating data/information, managing changes/workflow, etc. Typically stuff that web 2.0 tools are usually not so good at. I’m wondering if we could combine these two worlds in some way.

]]> by: John Tropea http://libraryclips.blogsome.com/2009/03/23/workflow-20/#comment-32860 Tue, 24 Mar 2009 12:29:29 +0000 http://libraryclips.blogsome.com/2009/03/23/workflow-20/#comment-32860 Great Matt. At the moment for some coordination tasks I do use a combo of wikis and blogs with subscription notifications to prompt people, and comments to discuss. And now I'm thinking about making this workflow more formal I guess. I like your bit about using a wiki to design/trial a flow. Wikis as final product or just a tool to design a final product (the true double nature of wikis) Great Matt. At the moment for some coordination tasks I do use a combo of wikis and blogs with subscription notifications to prompt people, and comments to discuss. And now I’m thinking about making this workflow more formal I guess.

I like your bit about using a wiki to design/trial a flow.

Wikis as final product or just a tool to design a final product (the true double nature of wikis)

]]> by: Matt Moore http://libraryclips.blogsome.com/2009/03/23/workflow-20/#comment-32859 Tue, 24 Mar 2009 09:14:47 +0000 http://libraryclips.blogsome.com/2009/03/23/workflow-20/#comment-32859 Two observations from my experiences: 1. Wikis make great prototyping tools for website & process design. You work out what information you need to display and therefore what you need to collection. A few of you do the process manually and collaboratively on the wiki for a few iterations and after that you have a much better idea of elements, process, workflow, inputs & presentation. 2. Zoho & Google forms are starting to offer some basic workflow collection & presentation options. With Sharepoint, K2 offers some impressive functionality (and they've just released a version that's Confluence-affordable) around workflow mgt. It's worth checking out BPMN as well... Two observations from my experiences:

1. Wikis make great prototyping tools for website & process design. You work out what information you need to display and therefore what you need to collection. A few of you do the process manually and collaboratively on the wiki for a few iterations and after that you have a much better idea of elements, process, workflow, inputs & presentation.

2. Zoho & Google forms are starting to offer some basic workflow collection & presentation options. With Sharepoint, K2 offers some impressive functionality (and they’ve just released a version that’s Confluence-affordable) around workflow mgt.

It’s worth checking out BPMN as well…

]]>