Orna, E.: Information strategy in practice (2004)
0.04
0.03612675 = product of:
0.0722535 = sum of:
0.0722535 = product of:
0.144507 = sum of:
0.144507 = weight(_text_:policy in 4819) [ClassicSimilarity], result of:
0.144507 = score(doc=4819,freq=10.0), product of:
0.2727254 = queryWeight, product of:
5.361833 = idf(docFreq=563, maxDocs=44218)
0.05086421 = queryNorm
0.52986264 = fieldWeight in 4819, product of:
3.1622777 = tf(freq=10.0), with freq of:
10.0 = termFreq=10.0
5.361833 = idf(docFreq=563, maxDocs=44218)
0.03125 = fieldNorm(doc=4819)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Footnote
- Rez. in: JASIST 56(2005) no.14, S.1556-1557 (J. Graef): "On one level, Information Strategy in Practice by Elizabeth Orna is a handbook an how to create an "information strategy." On another, it is a commentary an changing information roles and responsibilities in organizations. The main theme is aimed at information professionals (usually librarians) who want to learn the nuts and bolts of how to conduct an "information audit," how to develop an "information policy," and how to create an "information strategy." The subtext-that information management is everyone's responsibility-is a more radical (and interesting) message. An information strategy as defined by the author is an action plan for managing and applying an organization's information resources and supporting its essential knowledge base (the people who contribute and use information to achieve the organization's objectives). The emphasis is an a specific problem, function, or departmentnot the entire enterprise. For example, a strategy might be aimed at capturing knowledge that is transferred informally among employees or making an information system more efficient, less error prone, and more accessible. According to Orna, an information strategy is the last stage of a three-step process that begins with an audit (needs assessment), which is the basis tot a policy (objectives, priorities, and metrics). As she defines it, the audit describes "what is" in terms of information use. The policy describes "what should be," and the strategy shows how to get from "what is" to "what should be." Table l compares the three processes. The audit example is Orna's; the policy and strategy examples are mine. . . .
Information Strategy succeeds as a guide for librarians who want to conduct an information audit and then follow it up with a set of recommendations and an action plan. IT staff who need to develop a specific kind of policy (e.g., for security or privacy) and businesspeople who want to develop an information strategy for competitive advantage should look elsewhere. Orna also makes a valuable contribution in raising such issues as "mutual information obligations," the relationship between information and knowledge management, the overemphasis an technology solutions and measuring of intellectual capital, and the need to support "incidental information managers." These would make good discussion topics for a graduate library/information science class or a roundtable of practitioners.
