Your second-year graduate student, Maria, starts in January. She is sharp, organized, and eager. She took a research methods course last semester where she learned about validity, reliability, survey design, and statistical analysis. She is ready to help.

At her first team meeting, the PI mentions that the fall convening generated ninety-seven response cards from poster sessions, forty-two stories from the "moment that mattered" prompt, and a network map built from yarn and index cards. Maria nods politely, but inside she is confused. Where are the surveys? Where is the control group? How do you analyze yarn?

She tries to be helpful. She drafts a satisfaction survey for the next event: twenty-five items, Likert scales, clean and professional. She shares it with the team. The PI says, gently, "This is good survey design, but it is not how we do evaluation here." Maria feels embarrassed. She thought she was contributing. Instead, she learned she does not understand the system she is supposed to support.

This is not Maria's failure. It is an onboarding failure. Nobody explained to her that this team treats evaluation differently: that the poster session IS the evaluation, that stories are the primary data, that the improvement cycle is how findings become actions. She was dropped into a sophisticated participatory system with no orientation beyond "read the proposal."

Now multiply this scenario across every role transition your project experiences. New graduate students join every year. Community partners rotate liaisons. Institutional staff get reassigned. External evaluators start mid-project. Each person brings assumptions about what evaluation looks like, and those assumptions may not match the approach you have spent years developing.

Onboarding failures in evaluation are rarely about competence. They are about philosophy. Most new team members arrive with a mental model of evaluation shaped by traditional approaches: surveys administered after programs, external experts judging quality, quantitative data as the gold standard, evaluation as a separate activity bolted onto the real work.

Participatory evaluation operates from a fundamentally different set of assumptions. The activity IS the evaluation. Partners define success. Stories are data. Findings drive improvement. These are not just techniques; they are a worldview about what evaluation is for and how it works.

When you skip onboarding, new team members fill the gap with their own assumptions. Graduate students default to survey design because that is what they were taught. Community partners disengage because they assume evaluation is something done to them, not with them. Institutional staff try to map your approach onto institutional assessment frameworks that do not fit. External evaluators apply their standard protocols without understanding why your team does things differently.

The result is not just confusion; it is subtle erosion of the participatory approach. Each new person who defaults to traditional methods pulls the system back toward bolt-on evaluation. Over time, the integrated design you built degrades into a collection of disconnected activities. Intentional onboarding is not just orientation. It is protection for the evaluation system itself.