Workflow is an intermediate consumer

Lorcan 1 min read

I have been using the following contrast in presentations for a while. This is to make a distinction between library services – or any other service for that matter – in a pre-network age, and such services now.
Then: people were prepared to build their workflows around library services.
Now: the library must be prepared to build its services around people’s workflows.
This is to try to capture succinctly a recurrent theme in these pages. This shift is because people are increasingly building their workflows – or learnflows, or researchflows. … – on the network. In some cases through a bricolage of desktop and network tools (e.g. toolbars, rss feeds, social networking sites, search engines, etc); in some cases through prefabricated workflow environments (e.g. course management systems, …). Where resources are not easily available to those workflows, they may not be used.
Of course, putting library services in those flows is not straightforward …. It does mean that the library needs to think about ‘intermediate consumers‘ – those workflows and applications that may sit between the library and its users (search engines, RSS aggregators, course management systems, search engines, social networking sites, cell phones, etc).
Related entries:

More from
The technology career ladder

The technology career ladder

Library leaders should be drawn from across the organization. Any idea that technology leaders are overly specialised or too distant from general library work is outmoded and counter-productive.
Lorcan 7 min read

Lorcan Dempsey dot Net

The social, cultural and technological contexts of libraries, services and networks

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.