FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W1567740164> ?p ?o ?g. }

• W1567740164 startingPage "135" @default.
• W1567740164 abstract "INTRODUCTION Groupware capabilities include e-mail, electronic conferencing, discussion forums, and document handling, as well as additional facilities that enable database customization and perhaps help coordinate other groupware and desktop products. Groupware is a collaborative tool that requires group members to want to share their work, collaborate, and cooperate. Employees, however, may resist sharing their knowledge because of a culture that stresses personal rewards and a perception that their position depends on their personal expertise (Wasko and Faraj, 2005). Unequal distribution of the effort required to share information is yet one more impediment to using groupware. That is to say, individuals who benefit least from sharing information face the task of making it available to other organizational members who benefit most (Rogers, 1994). Therefore, obtaining business benefit from groupware can be elusive (Aldenberg et al., 1999; Lou et al., 2006; Orlikowski, 1996; Orlikowski and Yates, 2006). As far back as the 1990s, researchers have tried to determine the reasons for success and failure of information systems in general and groupware in particular (Halloran et al., 2002; Orlikowski, 1996; Tan and Kondoz, 2008). Halloran et al., (2002) reported the non-uptake of Lotus Notes in a classroom setting. Students in this case used regular e-mail instead of the available Lotus Notes to report on the progress of group assignments. Failure in this case arose from a misunderstanding by tutors and students concerning the value of Lotus Notes. Tan and Kondoz (2008) argued that collaborative systems are often implemented without consulting potential users or without assistance being offered for living with the system. A case study by Orlikowski (1996) exemplifies additional reasons for failure. Alpha, the case company, at the behest of its CIO, implemented Lotus Notes with the purpose of leveraging the firm's expertise. The CIO actively promoted Lotus Notes by giving many presentations describing the software's features. Yet, in spite of these efforts, many employees remained ignorant about why Lotus Notes was installed on their computers at all. Furthermore, a lack of instructions on how to use Lotus Notes proved to be a major obstacle to the use of all the software's features. Users were expected to learn the software on their own personal time, which they refused to do. Even though the firm was initially ill prepared to adopt Lotus Notes, it eventually changed organizational processes that in turn resulted in the company's reaping the benefits from Lotus Notes (Orlikowski, 1996). In these and other cases, the adoption of groupware has required employees to change the ways of performing--and even understanding--their jobs. When employees refuse to make those changes, adoption of the groupware can be problematic. In another case study involving Lotus Notes, Aldenberg et al. (1999) noted that groupware requires employees to accept more responsibility because they have access to more information. That is to say, because team members have broad access to more information, they have the responsibility to initiate contacts for further needed information, resulting in empowered employees who are then expected to do more for themselves. Furthermore, using Lotus Notes to organize meetings resulted in information capture in the form of meeting minutes and decisions that could be accessed by all relevant staff. This information formed the basis for analysis and review of decisions long after the particular issues discussed were acted on. An analysis of Colruyt, a large Belgian retailer that designed, implemented and used groupware, provides a counter-example to the typical story of groupware adoption and use. Since its founding in 1965 and before designing and implementing its groupware, the company developed an organizational culture that emphasized devolution of power, decentralization of decision making, and acceptance of responsibility by staff at all levels. …" @default.
• W1567740164 created "2016-06-24" @default.
• W1567740164 creator A5037886063 @default.
• W1567740164 creator A5062208032 @default.
• W1567740164 creator A5070326208 @default.
• W1567740164 date "2014-07-01" @default.
• W1567740164 modified "2023-09-24" @default.
• W1567740164 title "Groupware Design, Implementation, and Use: A Case Study" @default.
• W1567740164 hasPublicationYear "2014" @default.
• W1567740164 type Work @default.
• W1567740164 sameAs 1567740164 @default.
• W1567740164 citedByCount "0" @default.
• W1567740164 crossrefType "journal-article" @default.
• W1567740164 hasAuthorship W1567740164A5037886063 @default.
• W1567740164 hasAuthorship W1567740164A5062208032 @default.
• W1567740164 hasAuthorship W1567740164A5070326208 @default.
• W1567740164 hasConcept C136764020 @default.
• W1567740164 hasConcept C183003079 @default.
• W1567740164 hasConcept C3020028006 @default.
• W1567740164 hasConcept C41008148 @default.
• W1567740164 hasConcept C554579003 @default.
• W1567740164 hasConcept C56739046 @default.
• W1567740164 hasConceptScore W1567740164C136764020 @default.
• W1567740164 hasConceptScore W1567740164C183003079 @default.
• W1567740164 hasConceptScore W1567740164C3020028006 @default.
• W1567740164 hasConceptScore W1567740164C41008148 @default.
• W1567740164 hasConceptScore W1567740164C554579003 @default.
• W1567740164 hasConceptScore W1567740164C56739046 @default.
• W1567740164 hasIssue "2" @default.
• W1567740164 hasLocation W15677401641 @default.
• W1567740164 hasOpenAccess W1567740164 @default.
• W1567740164 hasPrimaryLocation W15677401641 @default.
• W1567740164 hasRelatedWork W1517227101 @default.
• W1567740164 hasRelatedWork W1531500077 @default.
• W1567740164 hasRelatedWork W1575972330 @default.
• W1567740164 hasRelatedWork W2021824108 @default.
• W1567740164 hasRelatedWork W2040087248 @default.
• W1567740164 hasRelatedWork W2088321826 @default.
• W1567740164 hasRelatedWork W2144972925 @default.
• W1567740164 hasRelatedWork W2149118044 @default.
• W1567740164 hasRelatedWork W2273021975 @default.
• W1567740164 hasRelatedWork W2274226389 @default.
• W1567740164 hasRelatedWork W2309604881 @default.
• W1567740164 hasRelatedWork W2411718304 @default.
• W1567740164 hasRelatedWork W297825902 @default.
• W1567740164 hasRelatedWork W2992726523 @default.
• W1567740164 hasRelatedWork W3044265891 @default.
• W1567740164 hasRelatedWork W3187004658 @default.
• W1567740164 hasRelatedWork W3200561930 @default.
• W1567740164 hasRelatedWork W62062250 @default.
• W1567740164 hasRelatedWork W884114315 @default.
• W1567740164 hasRelatedWork W2282190092 @default.
• W1567740164 hasVolume "17" @default.
• W1567740164 isParatext "false" @default.
• W1567740164 isRetracted "false" @default.
• W1567740164 magId "1567740164" @default.
• W1567740164 workType "article" @default.