MétaCan
Menu
Back to cohort
Record W2006822915 · doi:10.3917/riges.373.0058

Comment gérer les employés à haut potentiel ?

2012· article· fr· W2006822915 on OpenAlex
Kathleen Bentein, Sylvie Guerrero, Malvina Klag

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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueGestion · 2012
Typearticle
Languagefr
FieldBusiness, Management and Accounting
TopicHuman Resource and Talent Management
Canadian institutionsnot available
Fundersnot available
KeywordsHumanitiesPolitical sciencePhilosophy

Abstract

fetched live from OpenAlex

Résumé Une revue de la documentation montre que la gestion des employés à haut potentiel pose des défis aux organisations, notamment l’absence de définition universelle des hauts potentiels, l’identification des employés à haut potentiel privilégiant la performance et les résultats passés, des programmes officiels risquant de susciter trop d’attentes et des perceptions d’injustice, une gestion ciblant une relève possible plutôt que des hauts potentiels. Pour aider les dirigeants et les cadres à améliorer l’identification et le développement des employés à haut potentiel, nous proposons dans cet article les actions suivantes : partager la responsabilité jusqu’au plus haut niveau de l’organisation et créer une culture du développement, définir et communiquer les critères de repérage des hauts potentiels et rendre le processus transparent, gérer régulièrement les attentes des hauts potentiels et leur offrir des trajectoires de carrière individualisées, privilégier la logique du développement plutôt que celle du remplacement et, enfin, réviser et ajuster la gestion des hauts potentiels selon des indicateurs préétablis. Fonctions : GRH, management

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.544
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

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

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.031
GPT teacher head0.233
Teacher spread0.201 · 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