STOP SOPA ☣ STOP RWA
Two bills are making their way through the U.S. Congress that would have highly negative consequences for AcaWiki and the public good. Please take action against both.
Many large sites are blacked out January 18 to spur action against SOPA. Visit americancensorship.org to take action against this bill, which is a censorship and security risk for the entire internet. Wikimedia's General Counsel explains how SOPA would hurt wikis.
RWA would prohibit federal agencies from conditioning their grants to require that articles reporting on publicly funded research be made accessible to the public online. This is unjust and would specifically harm AcaWiki by greatly reducing the number of people with access to important literature — access is required to summarize. Please tell congresspeople to oppose RWA.
See AcaWiki:SOPA-RWA for planning and discussion of this message.
A coordination theory approach to organizational process design
From AcaWiki
Citation: Kevin Crowston (1997) A coordination theory approach to organizational process design. Organization Science (RSS)
Tagged: Business (RSS) knowledge management (RSS), coordination (RSS), coordination theory (RSS)
Summary:
Kevin Crowston's article provides a description of how to apply coordination theory to the design of organizational processes. Crowston shows how a focus on coordination can help provide a way to understand organizational processes or routines, break them down into pieces, and understand where support can be used or where new forms of organizations or processes might be useful.
The paper reviews coordination theory before presenting a detailed example from a software development division of a large computer manufacturer. Crowston presents data from that manufacturer and then uses coordination theory to identify dependencies and coordination mechanisms and then to suggest possible alternative mechanisms and processes or routines that the organization might follow.
Using 16 interviews of 12 individuals, Crowston presents a detailed model of the process around a change process (presumably the process that the team uses to the change the software on their products or devices). It is a complicated process with a large number of dependencies and is shown on a two page flow-chart. Crowston then uses a set of three techniques to identify dependencies and coordination mechanisms in the process. These involve (1) look for known coordination mechanisms like duplicated tasks or task assignment, (2) identify possible dependencies between resources, and (3) look for problems that suggest unmanaged or unspecified dependencies.
After identify these coordination points, Crowston suggests a series of alternative coordination mechanisms that might be used to better manage these dependencies and then evaluates these in interviews and based on the firms actual later actions. Crowston concludes arguing that, "coordination theory is a success if those attempting to understand or redesign a process find it useful to consider how various dependencies are managed and the implications of alternative mechanisms."
Theoretical and practical relevance:
For a background on coordination theory, although one aimed at the CSCW community, refer to Malone and Crowston's (1990) What is coordination theory and how can it help design cooperative work systems?.
Crowston's article is based on his dissertation work. It has been cited more than 270 times since it was published 13 years ago, primary by those in the knowledge-management literature.
