Participatory Evaluation for Workforce Development Team Guide | Issue 2 of 8

You design skill assessments for workforce programs. You watch journeyers grow from uncertain beginners into capable practitioners -- and then you try to document that growth with a checklist. You have felt the gap between what your rubric captures and what you actually observed. Maybe you have watched a journeyer demonstrate real problem-solving ability during a lab session and then scored them "meets expectations" because your assessment instrument has no category for "thinks on their feet." This issue is for faculty building skill-based curricula, program coordinators tracking cohort development, lab directors observing daily growth, and anyone who suspects that their current tracking system measures compliance when it should be measuring capability.

Marcus, a CNC machining journeyer, is in his second semester at a regional community college. Last week, the CNC lathe started producing parts outside tolerance.

Names and scenarios in this guide are composites, drawn from presentations, case studies, professional experience, and evaluation research across multiple programs and regions. Any identified programs or individuals that are featured have opted in to share their experience and program information in support of the community. His classmates called the instructor. Marcus did something different. He paused, checked the spindle temperature, recognized thermal drift from a concept covered in week four of the previous semester, recalibrated the machine, ran three test cuts, measured each one, and documented the process on a maintenance log that nobody had asked him to fill out.

His instructor watched the entire sequence from across the shop floor. She saw systematic troubleshooting. She saw a connection between classroom theory and shop floor reality. She saw initiative -- Marcus did not wait to be told what to do. She saw documentation habits that would serve him in any manufacturing environment. She saw the kind of capability that employers describe when they say "this person is ready."

The next day, she enters Marcus's scores into the program tracking system. Skill: Machine Operation. Rating: Proficient. That is the entire record of what happened.

Somewhere in that gap between what the instructor observed and what the system recorded, the most valuable evidence of Marcus's development disappeared. Not because anyone made an error. Because the tracking system was never designed to capture it.

This happens across workforce programs every day. Faculty and lab directors observe growth in real time -- they see the shift from following instructions to anticipating problems, from isolated skill execution to connected thinking. But tracking systems ask for proficiency ratings, not development stories. They capture the snapshot, not the trajectory.