MétaCan
Menu
Back to cohort
Record W1484114727 · doi:10.17705/1cais.01423

Developments in Practice XIV: Marketing KM to the Organization

2004· article· en· W1484114727 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueCommunications of the Association for Information Systems · 2004
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicInformation Systems and Technology Applications
Canadian institutionsQueen's University
Fundersnot available
KeywordsCredibilityOrder (exchange)MarketingHierarchyBusinessProduct (mathematics)Public relationsKnowledge managementPolitical scienceComputer science

Abstract

fetched live from OpenAlex

KM is experiencing the steep downward slope of the "hype cycle" and some organizations are rushing to abandon KM as quickly as they rushed to adopt it. Unfortunately, much of our understanding of what KM can do for organizations is still limited to academic treatises and small pilot studies. Managers therefore realize they must market KM more effectively in order to communicate its potential and build a coalition of support while KM matures and evolves. To explore this issue, the authors convened a focus group of practicing knowledge managers. After examining how KM groups currently market themselves, this paper constructs a framework for marketing KM in an organization that integrates the experiences of KM managers with basic marketing principles. It concludes that KM faces many marketing challenges, including lack of understanding of the need, lack of brand awareness, and a negative brand attitude. It recommends that knowledge managers must see themselves as internal entrepreneurs, first building a market for their product and then developing an effective marketing strategy. It also suggests there is a hierarchy of knowledge needs in organizations that must be addressed sequentially in order to develop trust and credibility among general business managers.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.006
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.973
Threshold uncertainty score0.718

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.006
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0010.000
Scholarly communication0.0000.003
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.012
GPT teacher head0.238
Teacher spread0.226 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it