Faculty Development Programmes: From Training Sessions to Improved Teaching

Define the development need

A faculty development programme should respond to a teaching challenge that participants recognise. Examples include unclear assessment criteria, limited student participation or difficulty providing timely feedback. Begin with evidence from course reviews, student work, staff discussions and institutional priorities. Avoid assuming that all teachers need the same workshop because a topic is fashionable.

Carnegie Mellon's teaching assessment guidance links reflection on teaching with professional development.^[1] For local planning, write a specific development objective: participants will redesign one assessment brief, trial a discussion routine or create an accessible learning activity. Such objectives make it possible to examine what changed after the programme.

Understand participants' starting points

Ask faculty about experience, discipline, teaching responsibilities and available time. A new instructor learning basic course design has different needs from a programme leader coordinating assessment across modules. Separate essential common learning from optional specialist sessions. Identify barriers such as timetable conflicts, limited technology access or the absence of a colleague with whom to practise.

Collect needs information respectfully. Development should not become a public ranking of supposedly weak teachers. Explain how responses will be used and who can see them. Where participation is linked to performance management, clarify that relationship in advance so that expectations and confidentiality are not ambiguous.

Design a learning sequence

A useful sequence combines preparation, a focused session, application, feedback and reflection. Before the workshop, participants bring an existing teaching artefact. During it, they examine an example and improve their own material. Afterwards, they trial the change and discuss evidence with a peer. The facilitator helps participants adapt ideas to disciplinary and class-size differences.

For AI-related development, UNESCO's teacher competency framework offers a relevant reference on teacher knowledge, skills and values.^[2] It should inform a locally appropriate programme, not become a certificate claim that participants have acquired every competency after one session. Define the limited capabilities that the programme will actually develop and assess.

Create conditions for application

Reserve time for redesign and follow-up. Training that adds work without adjusting existing demands may result in unused materials. Ask department leaders to support a small pilot and provide access to necessary platforms or instructional advice. Build a community of practice around a concrete task rather than a large, inactive messaging group.

Pair participants for structured feedback. Give peers questions such as: is the outcome clear, can learners understand the task, and does the evidence show the intended capability? Where classroom observation is used, agree its purpose and protocol. Developmental observation should provide specific feedback and a chance to respond.

Illustrative example: improving feedback

Consider a fictional college where faculty report spending considerable time writing comments that students rarely apply. A development cycle begins with anonymised assignment feedback and student interviews. Participants learn to identify one consequential improvement, redesign a feedback prompt and add a short resubmission task.

Each teacher trials the approach in one course. The follow-up examines whether students can explain and use the feedback, how long marking takes and whether the revised task remains fair. The college does not infer success merely from positive workshop ratings. It uses the pilot to decide which practices merit wider adoption and which require modification.

Evaluate proportionately

Collect evidence at several levels. Participation records show reach; feedback shows perceived relevance; revised teaching materials show application; student work may show changes in learning. These measures answer different questions and should not be treated as interchangeable. Establish a baseline where practical and avoid attributing every improvement to the development programme.

Use a modest evaluation design that staff can sustain. For a small pilot, a sample of revised briefs, peer observations and learner reflections may be sufficient. For a major institutional investment, more systematic evaluation may be justified. Report limitations, including other changes occurring during the same period.

Sustain development over time

Create a repository of reviewed examples with permission from contributors. Recognise mentoring and course improvement as legitimate academic work. Refresh programmes when curriculum, student needs or technology changes, and retire sessions that no longer serve a clear purpose. Invite participants to identify the next challenge rather than repeating a fixed calendar indefinitely.

Faculty development succeeds through cumulative practice, feedback and institutional support. A participation certificate records an activity; it should not be presented as evidence of comprehensive teaching competence. Keep the programme's claims aligned with the learning and assessment that actually occurred.