Faculty development: if you build it, they will come
Bibliographic record
Abstract
OBJECTIVES: The goals of this study were three-fold: to explore the reasons why some clinical teachers regularly attend centralised faculty development activities; to compare their responses with those of colleagues who do not attend, and to learn how we can make faculty development programmes more pertinent to teachers' needs. METHODS: In 2008-2009, we conducted focus groups with 23 clinical teachers who had participated in faculty development activities on a regular basis in order to ascertain their perceptions of faculty development, reasons for participation, and perceived barriers against involvement. Thematic analysis and research team consensus guided the data interpretation. RESULTS: Reasons for regular participation included the perceptions that: faculty development enables personal and professional growth; learning and self-improvement are valued; workshop topics are viewed as relevant to teachers' needs; the opportunity to network with colleagues is appreciated, and initial positive experiences promote ongoing involvement. Barriers against participation mirrored those cited by non-attendees in an earlier study (e.g. volume of work, lack of time, logistical factors), but did not prevent participation. Suggestions for increasing participation included introducing a 'buddy system' for junior faculty members, an orientation workshop for new staff, and increased role-modelling and mentorship. CONCLUSIONS: The conceptualisation of faculty development as a means to achieve specific objectives and the desire for relevant programming that addresses current needs (i.e., expectancies), together with an appreciation of learning, self-improvement and networking with colleagues (i.e., values), were highlighted as reasons for participation by regular attendees. Medical educators should consider these 'lessons learned' in the design and delivery of faculty development offerings. They should also continue to explore the notion of faculty development as a social practice and the application of motivational theories that include expectancy-value constructs to personal and professional development.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.013 | 0.047 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.010 | 0.005 |
| Scholarly communication | 0.013 | 0.013 |
| Open science | 0.002 | 0.014 |
| Research integrity | 0.005 | 0.010 |
| Insufficient payload (model declined to judge) | 0.058 | 0.055 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".