Identify at least three groups of people who work inside your groups organization. Identify at least three groups of people outside the organization who depend on or have a stake in the success of your groups organization.
When things go wrong: Changing the System
I/CT's - Information and Communication Technologies
Reengineering
Some less than successful implementations
A customer service system (telephone support)
Goals:
Increase time spent talking with customers
Decrease time interacting with peers
Implementation:
Electronic Trouble Ticket System
If you can't handle the question, pass it on
Effect
Disconnected workers from the "human database"
Created a dissociated aggregate
A workaround
Informal practice
An informal networking system that allowed workers to interact covertly
Widespread deception of the record-keeping system
System changes eventually resolved these problems
A police patrol radio system
Goals:
A higher quality and more secure radio dispatch system that would make it easier to do database searches.
A lower cost dispatching systems in which clerks with no police experience, supplemented by computer data, could replace higher-cost officer dispatchers.
Centralized communications that gave district managers more control of cars on patrol (e.g. micromanagement).
Implementation:
Comprehensive computer database, including detailed mapping software
Digital and voice communication in the police cars
Centralized interaction, with all radio communication flowing through dispatchers
Effects:
Mostly positive, but
The maps were not sufficient and the clerk dispatchers didn't have the knowledge to transcend their limitations or to properly understand what officers were requesting.
With entirely centralized communication, officers couldn't interact with each other directly, this losing the "human database"
Informal Practice:
Officers supplemented the official police radio system with an informal C.B. radio system, re-enabling contact with each other.
System changes eventually resolved these problems
A hospital patient tracking system
Goals:
Improve patient monitoring with a portable system
Implementation:
Walkman-sized unit strapped to ambulatory patients
Antennas in hallways picked up signals and put into monitoring system
No training or support structure
Effect:
No significant use
Informal Practice:
The system was dropped without a reasonable tryout
In the end, road kill in the process of organizational innovation
An electronic forms management system
Goals:
Route all forms through a single forms management system
Improve forms processing workflow
Reduce clerical staff
Implementation:
A requirements and design process engaged relevant groups
A jurisdictional rivalry emerged involving the part of the company that would take the staff reduction
Regional and divisional divisions weren't accounted for
Effect:
An extended requirements process as additional concerns were addressed
A range of system compromises that reduced the value of the system
Informal Practice:
The scope of the system was reduced, with several system goals left unsatisfied.
System changes eventually resolved these problems
Lessons: Why productivity enhancements fail
Work is situated in work communities in which members collect knowledge of how a job is done.
Ignoring that knowledge and the value of that knowledge is a recipe for failure.
Facing such failures, work communities react by modifying the system
Work patterns and structures emerge in response to many contingencies, including the media with which they are implemented in
Systems re-implementing systems are likely to have very different requirements
Failing to restructure organizational structures in tandem with the new implementation is a recipe for failure.
Work is generally situated within the context of complex organizational politics.
Ignoring the competing interests that surround an implementation is a recipe for failure.
Stakeholders who are threatened by a new implementation will work to undermine it.
Implementations that force work to be done in a different way prevent people from adapting to changes in the environment.
Creating implementations that don't allow users to change/customize the system to local needs is a recipe for failure.
The Systems Perspective
From a systems perspective, an organization is not just a collection of people
Its an artifact, constructed by its members, that has the potential achieve more than its members might achieve individually
A place where 1+1 can equal 3
The systems perspective is a response to "reductionism"
Breaking a system down into its fundamental components
And studying those components in isolation in the hope of better understanding the system
Systems thinking says that this doesn't work
because it misses the context all the other pieces provide
because it misses the interaction of all the pieces
But systems theory still has to structure things
So the pieces don't go away
The system theorist just doesn't study them in isolation
Simon's (1968) model of artifacts captures some of this
Note here that for our purposes:
The organization is the artifact
Information theory and the Shannon Model come from systems theory:
The interactive (or cybernetic) model also comes from systems theory:
The whole is greater than the sum of its parts
Relationships are what makes a group a system
Perhaps the big lesson of Hawthorne Studies
Productivity is a function of expectations and relationships
People are not just parts in a machine
Examples
Physics
Bodies trapped in space and time affect space and time
Suggestive of issues in time and motion studies
Meeting one goal may impede another (efficiency and taste)
What are the intended and unintended effects of increased or decreased efficiency?
How does productivity affect morale, turnover, absenteeism, and training costs?
Biology
Using living systems a a metaphor for machines and social systems
Communication is the process of organizing (Farace, Monge, and Russell)
Cybernetics and feedback
What is a system?
A complex set of relationships between interdependent parts.
Closed systems are entirely self-reliant:
Open systems are exposed to an outside environment:
This is true of all organizations.
Competition
Influences from without
Scanning to anticipate
Coopetition
Development consortiums
Business Partner Relationships
Internal and External Stakeholders:
Internal
Management
Employees
Boundary
Stockholders
Employee Representatives
External
Customers
The Community
Government
The Media
Elements of systems
Components (Mediators in communication systems) or Static structures
Assemblies of Components or Clockworks
Organization of Components or Control Mechanisms
A larger systems in which a system is embedded (e.g. systems are open
Characteristics of systems
Environment
Interdependence
Unawareness of interdependence can be an issue that prevents incremental improvement
Cross-Training
Productivity Circles
Reengineering
Goals
Different participants/stakeholders have different goals
Those goals interact and must sometimes be negotiated
Equifinality: Goals can be reached multiple ways
Processes and Feedback
Consider keeping a canoe straight
Order
Greater openness increases the complexities
The problem with system theory has been
this complexity
requires advanced multivariate time series methodologies
it isn't easy to do experiments in real organizations
the theory, for the most part, is not tested
conceptually useful, but hard to prove in practice
We'll pick up from here next time.
Group Assignment due Monday
Compile as a complete a list as possible of the internal and external stakeholders associated with your groups organization.
Unless otherwise noted, the contents of this page
were written by participants on the Media Space Wiki, operated by Davis Foulger,
and should be cited accordingly. For example (APA): Foulger, D. and other
participants. (August 27, 2008). Organizational Spr2006 Sess09. MediaSpaceWiki. Retrieved on from
http://evolutionarymedia.com/wiki.htm?OrganizationalSpr2006Sess09.