# Faculty Onboarding Playbook: Outcomes Assessment That Does Not Feel Like Busywork ## The Problem You Are Solving Faculty see outcomes assessment as compliance theater. Your job is to show them it is a tool for improving their teaching. This playbook walks you through a 4-week process that reframes assessment as a teaching improvement tool, not a checkbox exercise. --- ## Week 1: Frame It Right (NOT "You Must Assess") The first week is about positioning. You are not telling faculty they have a new administrative requirement. You are inviting them to answer a professional question: Are my students actually learning what I am teaching? ### Email Template (From Department Chair, Not Compliance) Send this email to your faculty in Week 1: --- **Subject: Trying a new approach to understanding what works in our classes** Hi [Faculty Name], I wanted to reach out about something that has been on my mind. We spend a lot of time and energy on curriculum and instruction, but we do not always know with precision whether specific topics are landing with students. We are piloting a new tool that might help us answer that question. It is lightweight, and I think you will find it useful. Here is the idea: Pick one skill or concept from your course that matters most to student success. We will create a short rubric to measure it. When students demonstrate that skill on an assignment or assessment, we score the rubric. Then we look at the results. If 85 percent of students master it, great. We know that approach works. If only 60 percent master it, we ask: Why? And we fix it. That is the whole thing. No extra grading. No busywork. Just: What works? What does not? And what do we change? I am running a pilot with a small group this semester. Would you like to try it with one of your courses? If you are interested, let me know and we will set up a 15-minute conversation to pick the outcome. [Your name] --- ### What to Expect from This Email Most faculty will not respond immediately. That is normal. Send a follow-up in 2-3 days offering to meet for coffee or Zoom. When you do meet, emphasize: - "This is one skill, one assessment. Not ten outcomes." - "I will help with the rubric. You do not build it from scratch." - "We look at the results together." --- ## Week 2: Do One Outcome Together (Shared First Assessment Cycle) Week 2 is about showing, not telling. You run one complete cycle with the faculty member so they see how it works. ### Step 1: Pick One Outcome Meet with the faculty member and ask: "What one skill do your students absolutely have to master to succeed in your course or the next course?" Write down their answer in one sentence. Example: "Students can troubleshoot network connectivity issues." Do not overthink this. One outcome. One sentence. ### Step 2: Create a Simple Rubric You and the faculty member create a 4-level rubric: **Level 4 (Proficient):** Student demonstrates clear understanding and can apply the concept correctly. **Level 3 (Developing):** Student shows understanding with minor gaps. Mostly correct. **Level 2 (Beginning):** Student has limited understanding. Significant gaps or errors. **Level 1 (Insufficient):** Student demonstrates minimal understanding. That is it. Four levels. Takes 15 minutes. ### Step 3: Administer the First Assessment The faculty member uses an upcoming assignment, quiz, lab, or project as the assessment tool. They do not create new work. They use something already happening. When students submit, the faculty member scores each submission using the 4-level rubric you just created. Takes maybe 30 minutes to score 20 students (90 seconds per student). ### Step 4: Look at the Results Together Here is where the magic happens. You and the faculty member sit down and look at the scores. You say: "What do you notice?" Maybe they say: "Seventy-five percent scored a 3 or 4. That is great." Or maybe: "Only 55 percent scored a 3 or 4. That is lower than I expected." Let them react first. This is their teaching. You are not judging. Then ask: "Why do you think that is the case?" They might say: "I think the concept is hard to explain. I rushed through it." Or: "I did not give them enough practice." Or: "The assignment was not clear about what I was asking for." All valid. All fixable. This conversation is the key. This is where busywork becomes professional reflection. --- ## Week 3: Closing the Loop (The Turning Point) Week 3 is where the tool stops feeling like busywork and starts feeling like teaching improvement. ### Document What You Found Write down (in simple language): "On [assignment name], [X]% of students scored proficient on [outcome]. This tells us [what that means]." Example: "On the Module 8 HOT, 62% of students scored proficient on 'mitigation strategies.' This tells us students can identify threats, but struggle with defensive techniques." ### Ask the Critical Question "What are we going to change?" Not "Could we maybe consider possibly adjusting..." No. "What are we going to change?" The faculty member might say: "I am going to add two case studies on defense mechanisms to the study guide." Or: "I am going to do more live coding examples on remediation." Or: "I am going to create a practice scenario set where they have to respond to a threat." Write it down. This is not a suggestion. This is a specific change. ### Set a Target "When we re-assess this in [next semester], what score are we aiming for?" Maybe 75%. Maybe 85%. Whatever is realistic. This is the commitment. This is the difference between "we documented activity" and "we are intentionally improving." ### This Is the Turning Point At this moment, the faculty member shifts their mindset. They are no longer checking a compliance box. They are answering a real professional question: "Did my change work?" --- ## Week 4: Celebrate the Win (Show Improvement) Week 4 happens after you re-assess. You run the same rubric on the next cohort or semester. Then you compare. ### The Numbers Tell a Story Example: Semester 1: 62% proficient on mitigation strategies Semester 2 (after changes): 78% proficient on mitigation strategies That is 16 points of improvement. That is real. ### Share the News Tell the faculty member: "Your changes worked. Proficiency went from 62 to 78 percent." Then tell others. Share it in a faculty meeting. Mention it in a newsletter. Post it on the department board. Not to brag. But to show that outcomes assessment is not busywork. It is how we improve teaching and student success. ### Celebrate Together Buy the faculty member coffee. Write them a note. Tell them directly: "Your willingness to look at the data and make changes improved student outcomes." This matters. This is the moment they become a believer. --- ## Common Objections and Responses ### Objection 1: "This is just more work." Response: "You already grade assignments. We are just using one rubric to structure how you grade. It actually saves time because you know exactly what you are looking for. The entire cycle is maybe 2-3 hours per semester." ### Objection 2: "I do not have time." Response: "We will do this during a department meeting. You do not need to find extra time. We will carve it out together." ### Objection 3: "My outcomes are too vague." Response: "That is exactly why we do this. We work together to make them clear. You are not alone in this." ### Objection 4: "I already know what students struggle with." Response: "You might. But data shows you where you are wrong. And it gives you evidence when you talk to a dean or accreditor about why you made a curriculum change." ### Objection 5: "This feels like my teaching is being evaluated." Response: "This is not about you. This is about the tool. Is the assignment clear? Is the concept difficult to explain? What support do students need? We figure it out together." --- ## Timeline | Week | Action | Time | |------|--------|------| | Week 1 | Send email, schedule meetings | Ongoing | | Week 2 | Create rubric, administer assessment, score results | 2 hours total | | Week 3 | Review data, document change, set target | 1 hour | | Week 4+ | Re-assess and compare | 1-2 hours (next semester) | Total time investment: 4-5 hours per outcome per year. --- ## Key Principles 1. **Start with one outcome.** Not five. Not ten. One. Once they see how it works, they may want to do more. 2. **Use existing assignments.** Do not create new work. Score something already happening. 3. **Make the data discussion safe.** You are not judging the faculty member. You are solving a puzzle together. 4. **Document the change.** Write down what you are going to do differently. Make it specific. Not "improve the lesson" but "add three more worked examples to the practice set." 5. **Verify the change worked.** Reassess. Show improvement. This is the payoff. 6. **Celebrate and share.** When proficiency goes up, tell people. Make it visible that assessment drives improvement. --- ## Success Looks Like - Faculty member asks to do a second outcome in the next semester - Faculty member talks about the results in a faculty meeting - Proficiency on the outcome increases between cycles - Faculty member says "this actually helps me understand what works in my teaching" If you get there, you have won. The tool becomes part of how they teach, not a burden on top of teaching.