DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / Visiting Artisan

Creative Uses for Slate: build something your team can keep using

Cody Gray, Chris Kwan and Katie Jordan explore creative Slate workflows through staff pain points, trained permissions, maintainable handoffs and community ideas.

Two open tool rolls beside a brass workpiece on a shared demonstration bench.
Visiting Artisan series artwork.

THE IDEA, IN A MINUTE

Give the next person a workable system.

Travel tools, ticketing, inventory and auctions begin with a practical problem. Turn the guests' examples into a small, testable workflow that colleagues can understand, maintain and improve.

01 / THE RECORDING

Watch the episode.
Or find your moment.

Start with the part of the day that hurts

A counselor needs tomorrow's travel details without rebuilding a report. An office needs to know where its materials went. A visitor needs a place in line without spending the afternoon standing in it. Those are useful starting points for a creative Slate project because each one names a person, a task and a frustration.

In this Visiting Artisan conversation, Cody Gray, Chris Kwan and Katie Jordan connect their ideas to work they have actually had to do. Katie asks what fails in the current process. Chris looks back at the support he needed as an admissions counselor. Cody describes feedback as a way to understand where users are struggling.

Try that approach before choosing a feature. Describe the present task, the interruption and the result someone needs. Ask the person doing the work to walk through a recent example. A request for a dashboard may really be a request to find the next action without opening five different places.

In the recording · 21:29 ↗

Choose a structure you can explain

The examples range from counselor travel tools to ticketing, inventory and live auctions. Their variety is an invitation to look at familiar building blocks differently. Forms collect information, related records preserve relationships, and portals or communications put the result in front of the right person.

Cody and Chris also describe moving Summit proposals into a Slate-hosted application. The useful lesson is to revisit inherited choices. A process that began with person-scoped forms may eventually need the structure of an application. Repeating the original design forever can create more work than reconsidering it.

Before building, write down what one record represents and what it must relate to. For inventory, distinguish an item from a movement of that item. For ticketing, distinguish a person from a particular visit.

In the recording · 29:08 ↗

Make the handoff part of the build

Chris brings the discussion back to maintenance: the institution has to understand what it receives. A clever Liquid solution becomes fragile when nobody can explain its conditions or change it after the original builder leaves.

Document the purpose alongside the clicks. Record which fields, queries, forms and messages the workflow depends on, what each condition means and where to look when the result is wrong. Give another colleague a routine change to make using those instructions. Their questions reveal the gaps that the builder's familiarity hides.

Include failure cases in that handoff. A missing contact method should not look like a successfully delivered notification. An inventory count with incomplete movement records should not be presented as a verified stock balance. Name those states explicitly, identify who resolves them and keep an understandable path back to the underlying records.

In the recording · 32:59 ↗

Pair permission with practice

An overloaded administrator can become the queue through which every small improvement must pass. Chris recommends giving interested staff room to learn through training and appropriate permissions. Cody reinforces the need for trust while retaining limits and protecting data.

Katie describes the shift that made knowledge-sharing more appealing: teaching somebody else a familiar task creates room to tackle the next challenge. That is a practical capacity decision. The team gains another capable operator, and the administrator gains time for work that cannot yet be delegated.

Choose a bounded starting task, such as maintaining an event or reviewing a query in a safe training environment. Define what the learner may change, what needs review and how to recognize a problem. Ask them to explain a result using a few known test records before extending their responsibility.

In the recording · 35:03 ↗

Borrow an idea, then test your version

Chris traces an inventory idea through several community adaptations. Each builder brings a different need and another possibility. The useful habit is to understand the earlier work well enough to change it deliberately, then leave enough explanation for the next person.

An implementation is also a chance to improve the process instead of reproducing every familiar step. Cody encourages new users to see what other institutions are building, including possibilities they may not be ready to use immediately. Keep those ideas visible while choosing a first version the team can support.

Decide how you will judge that first version before expanding it. For a queue, observe missed notifications and staff follow-up as well as waiting time. For inventory, compare recorded balances with a physical count. Use a small pilot to uncover missing data and awkward handoffs. Creativity becomes useful when the new workflow makes the daily task easier and remains understandable after its creator moves on.

In the recording · 47:55 ↗

03 / A SMALL EXPERIMENT

Make a creative idea maintainable

Use these fictional cases to plan a small Slate workflow. Write the intended result, the dependencies and the test that would persuade a colleague it works.

A visitor misses the message

A fictional advising office wants visitors to leave the waiting room until their turn approaches. One visitor has no usable mobile number. How should the queue handle that visit?

Compare your reasoning

Separate the visit from the person, define queue states and agree on a fallback with staff. Test the missing-number case and a failed notification without marking either as delivered. Observe missed calls and staff follow-up alongside waiting time.

Revisit this moment · 47:19 ↗
The inventory builder leaves

A fictional office inherits an inventory workflow with a displayed balance of 40 brochures, but two recent withdrawals have no recorded quantity. What must the next owner know before relying on the balance?

Compare your reasoning

Trace the item and movement records, identify the missing quantities and reconcile against a physical count. Document the calculation, dependencies and correction process. Have a colleague explain the result and make a routine change using the handoff notes.

Revisit this moment · 32:59 ↗
Rebuild the old request form?

A fictional implementation team asks to copy its current request process exactly. Staff currently re-enter each request into a second tracker. How would you choose a first version and a staff learning task?

Compare your reasoning

Follow a real request through the existing steps and identify why the second entry exists. Prototype one complete path with fictional records and explicit ownership. Give a trained colleague a bounded maintenance task, define review limits and measure duplicate entry before and after the pilot.

Revisit this moment · 41:58 ↗
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

The inventory story follows an idea through several builders rather than presenting it as a single finished invention. Chris describes adapting an earlier community example, then seeing another team adapt his version. That chain explains why the maintenance discussion matters: a useful shared build needs enough context for somebody else to understand its choices and make the next version their own.

Revisit the studio moment · 47:55 ↗

The Spark Between the Lines - Cody Gray, Christopher Kwan, Katie Jordan

The episode's standalone companion song draws on the conversation about creativity and community.

Watch the standalone lyric video

Art from the workshop

Visiting Artisan series artwork.

Open the artwork ↗

CONTINUE EXPLORING