[australia] Capturing Processes

[White, David]

One of the issues with capturing processes is that there's an assumption
that the workflow model fits all processes. The workflow model is great
for production line type processes - linear, even branching processes
that have a defined set of steps through which to proceed.

However 'knowledge worker' type work often doesn't fit the production
line (and therefore workflow) model.  This type of work is a series of
conversations where the 'product' is developed through collaborating
with information repositories and other knowledge workers in a process
that may often change. 

These sorts of processes usually have stages of progress (eg interviews,
requirements documentation, review), but these stages aren't in the same
class as workflow states/transitions. 

This is why, in my opinion ;) the most useful/common workflow in most
CMS implementations is Author -> Approve -> Publish. 

As I say, this assumption that the workflow model is suitable to all
publishing processes is only one of the issues. The other biggie I
reckon is that one about how technology implementation projects are
actually business change projects, but often aren't run with that
emphasis. You can't program a change into people like you can computers
;)

Cheers,
David.

--
David White
Senior ECM Specialist, ICT Portfolio Delivery, RailCorp
e: david.white at railcorp.nsw.gov.au 
p: (02) 820 22280



This e-mail and any attachments may contain confidential information that is intended solely for the use of the intended recipient and may be subject to copyright. If you receive this e-mail in error, please notify the sender immediately and delete the e-mail and its attachments from your system. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. Any opinion expressed in this e-mail and any attachments is not an opinion of RailCorp unless stated or apparent from its content. RailCorp is not responsible for any unauthorised alterations to this e-mail or any attachments. RailCorp will not incur any liability resulting directly or indirectly as a result of the recipient accessing any of the attached files that may contain a virus.