DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / Visiting Artisan

Joy in Community with Sarah Kotlinski: build systems people can use together

Build a more generous Slate practice with useful peer training, readable information, flexible plans and a regular check that busy work still serves your values.

Two open tool rolls beside a brass workpiece on a shared demonstration bench.
Build a generous community.

THE IDEA, IN A MINUTE

Make everyday systems work a little more human.

Sarah Kotlinski connects joy, mentorship and systems design. Her examples offer a practical starting point: help colleagues learn the work, make context easier to use and protect time for the values your team wants to put into practice.

01 / THE RECORDING

Watch the episode.
Or find your moment.

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 ↗

03 / A SMALL EXPERIMENT

Check three people-centered systems choices

Use these fictional cases to practice turning a useful idea into a clear lesson, a dependable summary or a realistic work plan.

The feature tip looks good but nobody can use it

A fictional Slate captain shares a polished graphic about a new feature. Colleagues like the post, but two still use the old workaround because the graphic assumes they know where to start. You have 15 minutes for a follow-up. What should you teach and check?

Compare your reasoning

Ask one colleague to show the current task using fictional records. Identify the missing step or term, then demonstrate just that part. Have each learner complete the task from the normal starting screen without the trainer directing every click. Check the finished result and save the short instructions where the team already looks for help. Likes alone do not show that the task became easier.

Revisit this moment · 10:30 ↗
The AI summary sounds certain about conflicting history

A fictional school-visit brief says most applicants enrolled last year. Its sources contain 18 applications and four enrollments, a note from two years earlier and a recent note with a different visit outcome. A recruiter needs the brief tomorrow. What must change before it is used?

Compare your reasoning

Check the counts and year against the underlying records, replace the unsupported claim and label the dates of both notes. Resolve the conflicting visit accounts where possible; otherwise preserve the disagreement as a question for the visit. Keep source links available and have the recruiter review the corrected brief. Do not turn an aggregate pattern into a prediction about an individual.

Revisit this moment · 19:07 ↗
The mentoring session disappears every week

A fictional team says sharing knowledge is a priority, but three urgent report requests have displaced its weekly mentoring hour. A new deadline now makes the original schedule impossible. What would a values-based revision look like?

Compare your reasoning

Ask what the new deadline actually requires and who is affected. Reduce or postpone a lower-priority output with the responsible person's agreement, then protect a smaller mentoring session focused on one recurring question. Record the changed scope and review it next week. If capacity is still insufficient, make that conflict visible rather than asking the mentor to absorb the work after hours.

Revisit this moment · 24:07 ↗
Build a test card to take with you

Notes stay in this tab. Reloading clears them.

04 / INSIDE THE STUDIO

The seams are part
of the story.

Behind the episode

Slate Feature Friday started as a small staff-training graphic after Sarah noticed an unnecessarily complicated workflow. A colleague suggested sharing the tips more widely. She describes later shifting their focus toward Slate captains and finding that the posts she expected to be most popular did not always draw the strongest response.

Revisit the studio moment · 10:30 ↗

Joy in the System

An original song based on Sarah Kotlinski's Joy in Community interview, created with AI help.

Watch the standalone lyric video
Hear it in the original episode · 49:53 ↗

Art from the workshop

Visiting Artisan series artwork brings two sets of tools to a shared workbench.

Open the artwork ↗

KEEP THE IDEA MOVING

Where would you take it next?

CONTINUE EXPLORING