Bureaucrats, darkmatter, Administrators
1,459
edits
WikiCED manual: Difference between revisions
Jump to navigation
Jump to search
→Benefits and risks of introducing change
| Line 26: | Line 26: | ||
= Benefits and risks of introducing change = | = Benefits and risks of introducing change = | ||
Many people dream about being a change hero, making one suggestion – [[todo::example]] and suddenly we have a successful transformation that everyone recognizes. The reality is usually far more complicated. | |||
Computer systems can yield tremendous efficiencies, but they can force people to work in ways they have difficulty adapting to. There's always a question of individuals adapting to tech versus the tech adapting to the person. Good technology will consider the user experience and impact as important as the potential gain. This can be recognized by learning about successful uses of the technology, and the kind of background and processes that went into its development. Many companies and projects are very technically driven. Whatever clever “invention” a technical person managed to come up with becomes the focus. This | People have very good reasons to be hesitant about change. It's always a good idea to wait and see what other organizations, similar to yours, are doing. If you're going to try to leap ahead, make sure you have steady partners and are not compromising your organization; changing the organization's focus or making participation more difficult for some. | ||
Computer systems can yield tremendous efficiencies, but they can force people to work in ways they have difficulty adapting to. There's always a question of individuals adapting to tech versus the tech adapting to the person. Good technology will consider the user experience and impact as important as the potential gain. This can be recognized by learning about successful uses of the technology, and the kind of background and processes that went into its development. Many companies and projects (potential components of your innovation) are very technically driven. Whatever clever “invention” a technical person managed to come up with becomes the focus. This may be a good model for ultra competitive commercial enterprise, but it's not so good for social organizations. Signs of a good service providers are multidisciplinary teams that include, where practical, designers, content experts, and end user representation, as well as those focusing only on the technology (hopefully with some interest in the context). | |||
Ultimately, however, individuals and the organization will have to adapt to the way the technology works. No technology is completely flexible, so past procurement and training, some processes will need to be changed, information constrained to a system, and systems interfaced. As an individual, you'll have to consider how your innovation can be integrated (or not - "loosely coupled" system are often considered the most robust). | Ultimately, however, individuals and the organization will have to adapt to the way the technology works. No technology is completely flexible, so past procurement and training, some processes will need to be changed, information constrained to a system, and systems interfaced. As an individual, you'll have to consider how your innovation can be integrated (or not - "loosely coupled" system are often considered the most robust). | ||