DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / Visiting Artisan

Technical Innovation with Jon Thornton: build systems the next person can maintain

Make Slate systems easier to maintain through clear requirements, mobile-first workflows, documented dependencies and a deliberate division of technical and everyday work.

Two open tool rolls beside a brass workpiece on a shared demonstration bench.
Build for the next pair of hands.

THE IDEA, IN A MINUTE

A useful system should outlast the person who built it.

Jon Thornton connects technical innovation with sustainable operations. Review what a system is for, who will maintain each part and which dependencies the next person needs to understand before making a change.

01 / THE RECORDING

Watch the episode.
Or find your moment.

Begin with the requirements people need to review

A complicated application can reflect years of separate decisions rather than a deliberate student experience. Jon Thornton describes organizing graduate application materials and requirements in a dataset, then turning that information into a working document for annual review with program advisers.

The review gives colleagues something concrete to correct: what is required, where it belongs and what needs to change for the next cycle. Before configuring the dataset, examine the underlying data and how the structure will scale. A convenient first example is not enough if later programs require a different model.

Start with one application path. List its requirements, their owners and the questions that remain unresolved. Use the next cycle review to confirm the process, not just repeat last year’s configuration.

In the recording · 04:30 ↗

Design for the moment someone actually uses the page

An event agenda may be built on a desktop but opened from a text message while a visitor walks across campus. Jon’s redesign starts with that mobile situation. He discusses accessibility in the wireframe stage and a content structure that event staff can update without rebuilding the page.

Review the complete task: find the right session, read its details and understand the next step on a small screen. Check keyboard navigation, readable labels and content order alongside the visual design. Then test the editing task with the staff member who will make a last-minute correction.

Keep the recurring changes simple. Session text, instructions and annual updates should have a clear home and an understandable workflow. A design that works for visitors but requires a developer for every correction still has an operational bottleneck.

In the recording · 26:22 ↗

Audit purpose before reducing complexity

Jon describes a cleanup effort that examines which populations remain necessary and which uses could be served more simply. The distinction matters: a population governing permissions is doing different work from a filter used to describe a communication audience.

Inventory the purpose, owner and dependencies of each candidate before consolidating anything. Check where it controls access, feeds another process or appears in a staff workflow. Similar names do not establish that two populations are interchangeable.

Choose one understandable improvement, test its effect and record the decision. A lower object count is useful only if people retain the access and behavior they need. Keep a recovery path for changes that affect downstream work.

In the recording · 29:08 ↗

Decide who maintains each part

The dividing line between technical staff and end users runs through the interview. Jon argues for making routine work accessible without requiring the technical team to explain every query individually. That begins with a realistic account of what each group will own.

Name the routine edit, the person making it and the knowledge they need. Distinguish a content change from a logic change or a permission change. Provide a short example and a route for exceptions, then ask someone other than the builder to complete the task.

Jon’s query-library documentation project points in this direction: descriptions and examples beside reusable query components. He describes it as an unfinished project competing for time, so the useful starting point is smaller. Explain one frequently used component well enough that a colleague can recognize when to use it.

In the recording · 44:56 ↗

Leave a map of the connections

A source format rarely stands alone. Jon describes a documentation proposal connecting the source format, feeding query and responsible owner in a record view. The aim is to spare a successor from rediscovering every relationship by searching through separate objects.

For one export-and-import process, trace where the data originates, what transforms it and what consumes the result. Record the purpose, owner, schedule and expected output. Add the place a colleague should check when the result is missing or unexpected.

Use the map during an actual review. If an important dependency is discovered only through memory, add it while the context is fresh. Documentation is more useful when it helps someone make the next decision.

In the recording · 35:06 ↗

Agree on timing and the outcome together

A nightly feed changes the design of any workflow that depends on it. Jon asks cross-functional teams to consider the available data, feasibility, dependencies and delivery window together. A rule that runs before fresh data arrives can produce the wrong experience even when each component works independently.

Bring the people responsible for both sides of the exchange into the discussion. Describe the student-facing outcome, then work backward through the milestones and timing needed to support it. Agree on what happens when a feed is late and who investigates.

Apply the same discipline to complex territory definitions. Jon describes ongoing work to simplify a mixture of geographic and school-based rules. Test the common cases and meaningful exceptions, and make the maintenance cost visible before adding another special case.

In the recording · 39:17 ↗

03 / A SMALL EXPERIMENT

Review three maintenance handoffs

Use these fictional cases to identify the dependency, owner and test needed before a system becomes someone else’s responsibility.

The audience filter also controls access

A fictional team finds two similarly named populations and plans to remove one. It appears in a communication query, but another office also uses it for record access. What must the review establish?

Compare your reasoning

Identify both purposes and every dependent use. Confirm the access owner and intended scope before changing anything. Test representative authorized and unauthorized views, preserve a recovery path and document which function each remaining object serves.

Revisit this moment · 29:08 ↗
Every agenda correction needs a developer

An event agenda looks good on a desktop, but staff cannot change room information themselves. Visitors open it from a text message on the day of the event. What should the next small redesign include?

Compare your reasoning

Define editable content separately from layout and logic. Give the responsible staff member an appropriate editing workflow and a short example. Test reading, navigation and correction on a phone, including keyboard use and a last-minute change.

Revisit this moment · 26:22 ↗
The rule runs before the new data arrives

A fictional feed usually arrives at 3:00 a.m. A dependent rule runs at 2:30 a.m., and delayed files sometimes arrive after 5:00 a.m. Staff assume the morning status is current. What needs to change?

Compare your reasoning

Map the feed, import and rule sequence with both owners. Define how freshness is checked, when dependent work can safely run and what happens after a delay or failed import. Make stale results visible and test the normal, late and missing-file cases.

Revisit this moment · 39:17 ↗
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

Jon’s source-format documentation idea turns the handoff problem into a concrete design: show the format, feeding query and owner together so the next engineer can follow the connections. The same concern appears in his unfinished query-library project, where descriptions and examples would help staff understand reusable components.

Revisit the studio moment · 35:06 ↗

Build the Ship While It Flies - Jon Thornton

A companion song inspired by Jon Thornton’s Technical Innovation interview.

Watch the standalone lyric video

Art from the workshop

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

Open the artwork ↗

CONTINUE EXPLORING