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 ↗