Web 2.0 workflow failures

Web 2.0 workflow failures

It seems like one of the major failures of Web 2.0 applications is the fact that they fail on the workflow analysis.

I seem to be starting to analyse the fact that many of the so-called Web 2.0 applications seem to be forgetting the fact that they are no longer simple informational tools, but actually allow users to do something practically.

This raises one very significant issue. In order to work properly Web 2.0 applications will have to bare in mind (properly) the natural work-flow of their users.

In order to understand and analyse the natural workflow of the users, Web 2.0 Information Architects will have to be more than that. They will, in perfect world, have very good understanding of business processes, and workflow patterns, in order to be able to 'map' the Web 2.0 application to the users' workflow preferences.

I have seen many people talk about usability, accessibility, user-centered design and usability testing, but very few of them talk about the actual workflows of the users. I believe these are (at least) slightly separate matters and they need to be considered if not separately then as part of the same application design process, but looked at from a different angle.  

Oh yeah, did I mention about people needing to have some business process related knowledge?  

Jason Grant 

Related items

See also