Treat teaching as part of the systems work
A strong Slate builder can still need help teaching someone else. Sarah Kotlinski describes that gap as one reason the training user group found an audience. Technical ability often brings responsibility for staff training, even when the person has had little opportunity to develop that separate skill. Her response began with a conversation among people facing the same problem.
Choose one task a colleague needs to perform and ask them to show you their current approach. Notice where they hesitate and which terms need explaining. Build a short practice task around that point, then let them try it without your narration. Invite another trainer to review the instructions. That gives you a useful exchange even before there is a formal program.
In the recording · 07:54 ↗Let a small friction point become the next lesson
Slate Feature Friday began when Sarah overheard a cumbersome email workflow and recognized a simpler feature that could help. She made a small graphic for staff, then began sharing the tips more widely. The subject came from work already happening around her.
Keep a short list of repeated questions and awkward steps. Pick one, show the starting situation and demonstrate the improvement with fictional records. End with a task the reader can repeat. Sarah also describes changing the audience of her posts toward Slate captains, so check who each tip is for. A clever technique for an administrator may need a different explanation for an occasional user.
In the recording · 10:30 ↗Make values visible in the workweek
Sarah connects joy at work with noticing small moments, appreciating colleagues and doing work that matches her values. When that sense of alignment slips, she looks at whether busy work has displaced strategic work. This offers a concrete place to begin a review of an overloaded week.
Name one value and the behavior that would express it. If the value is generosity, that might mean an hour helping a colleague understand a process. Compare that intention with the calendar. Decide what can move, shrink or stop so there is room for it. Keep the check practical and voluntary; a difficult week should not become a test of whether someone is cheerful enough.
In the recording · 17:03 ↗Give people context they can act on
Sarah's AI dashboard example gathers school-visit notes and interaction history into a narrative that staff can read before a visit. She compares its purpose with the old folders that kept previous visit notes close at hand. The useful outcome is arriving informed enough to have a better conversation.
Design that summary around the next task: what happened previously, what has changed and what remains unanswered? Keep dates and links to the underlying records available. Check a draft against those records, especially when notes disagree or a number lacks a clear denominator. A readable summary still needs a route back to its evidence. Missing history should stay visible rather than being filled with a plausible story.
In the recording · 19:07 ↗Revise the plan without abandoning its purpose
Sarah's leadership advice is to hold plans lightly and values tightly. A change in circumstances may require a different schedule or approach while leaving the reason for the work intact. She also emphasizes listening to how a change affects the team.
When a priority shifts, write down the new constraint and ask people what it changes in their day-to-day work. Separate what must be delivered now from what can be reduced or postponed. Explain the trade-off and keep the next review date visible. This makes flexibility something the team can understand, rather than a succession of urgent requests with no explanation.
In the recording · 24:07 ↗Give the next person an easier way to ask
Sarah encourages newcomers to ask questions and describes a community space specifically intended for new Slate users. That invitation works best when experienced members help make the first question manageable.
Offer a simple structure: what were you trying to do, what happened and where did you get stuck? Use a fictional example or a carefully cleared screenshot when discussing a system publicly. Answer the immediate question, explain one useful principle and leave space for a follow-up. Shared problem-solving becomes more useful when newcomers can contribute without first proving how much they know.
In the recording · 30:56 ↗Keep signals separate from conclusions
In Molten Metrics, Sarah points to information already being collected, including visits, clicks and engagement in other systems. She describes combining those signals as ongoing work. Their practical value depends on the context available and the question a team wants to answer.
Before combining sources, check what each measure counts, whose activity it represents and when it was recorded. A family member's engagement is not the same as a student's stated preference, and silence does not establish disinterest. Use an uncertain signal to frame a respectful question or inspect a process. Keep decisions grounded in verified information and the person's own expressed needs.
In the recording · 35:12 ↗