Begin before assigning points
Before an event receives a weight or a behavior earns a bonus, someone has to decide what the score is for. In this From the Foundry episode, David reads Chapter 2 of The Innovation Forge, Collaboration and Staff Engagement. The chapter pauses before rubric construction to bring the people who understand students into the design.
That timing matters. Staff will interpret the score, use it to plan outreach and notice when it misses something important. Involving them early gives those observations a place in the tool itself. Adoption also takes time: a new calculation does not automatically change an institution's daily work.
In the recording · 01:37 ↗Ask what the data can actually show
Recorded behavior gives a team something concrete to examine. It also depends on what the institution collects, how reliably it collects it and how its practices have changed. David points out that a changing Slate implementation makes staff knowledge of the data particularly valuable.
Start with a behavior the team understands. What action created the record? Has tracking been consistent? What might be missing? A useful follow-up is to ask whether a student had a reasonable opportunity to take that action. Attendance can reflect access as well as interest.
Staff judgment needs scrutiny too. Experience can supply context, but it does not make a proposed weight unbiased. Write down the reasoning, compare it with available evidence and leave room for disagreement. An engagement rubric and a prediction of enrollment have different purposes.
In the recording · 04:54 ↗Make the weighting discussion visible
The chapter pairs collaborative development with continuing feedback. Analysts and admissions staff bring different questions to the same behavior: whether it can be measured consistently, what it means in a student conversation and how it supports the institution's priorities.
Later, David describes collecting both points per event and a maximum contribution. His example of fifteen points per event with a seventy-five-point cap makes two decisions visible: the value of one interaction and how much repeated activity can dominate the total.
Use that distinction to structure the discussion. Ask participants for a proposed weight, a cap and their reasoning. Keep meaningful disagreements visible rather than treating the average recommendation as the correct answer. A cap limits repetition; it does not by itself resolve unequal access to the activity.
In the recording · 07:54 ↗Give feedback a usable home
Forms provide a place for successive rounds of ideas, proposed behaviors, negative points, bonuses and revisions. David also leaves space for questions and a request to meet. That gives someone with a complicated concern a way to continue the conversation.
Decide whether responses should be identifiable or anonymous before collecting them. The chapter distinguishes a quick staff-record approach from a more robust standalone dataset and notes the downstream consequences of that choice. Staff participation need not require every contributor to have a Slate user account.
Plan how responses will be retrieved. Export keys or connected fields make later summaries easier to assemble. The collection method should support the feedback process beyond the first form submission.
In the recording · 11:38 ↗Show people what happened to their input
David describes using Deliver to keep a curated project history in staff updates. A message can return a participant's own recommendations beside averages from everyone or a relevant group, such as counselors or leadership. That comparison gives the next conversation a shared starting point.
The portal discussion extends the same approach: show an action when it is needed, reflect completion and bring new work back into view. The useful design question is what each participant needs to understand or do next.
Close the loop in the content as well. Explain which suggestions changed the rubric, which remain open and why a proposal was declined. Collecting feedback without a visible response leaves staff guessing whether participation mattered.
In the recording · 14:03 ↗Keep reviewing the score and its use
The chapter returns to open communication, support across departments and recognition of staff contributions. Those habits give the scoring system a way to change as the institution learns.
Pair a review of the numbers with a review of the work they prompt. Are staff using the score as intended? Which student situations are poorly represented? Did a tracking change alter the measure? Document the next adjustment and the question it should answer. Recruitment benefits remain something to evaluate, while people retain responsibility for interpreting the score and deciding how to support students.
In the recording · 18:03 ↗