DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / Visiting Artisan

Transfer Process with Ben Parsons: make the next handoff easier

Connect transfer notes, credit-review work and staff portal views into a process people can follow, with clear ownership, practical exception handling and useful feedback.

Two open tool rolls beside a brass workpiece on a shared demonstration bench.
Build a process the next person can follow.

THE IDEA, IN A MINUTE

Make the next action clear before making the system bigger.

Ben Parsons describes bringing transfer coordination into a staff portal, reusing entity-based notes and building a compact credit-review workflow. Start with one office-to-office handoff, then use the team's experience to improve the next version.

01 / THE RECORDING

Watch the episode.
Or find your moment.

Start with the handoff that keeps breaking

A transfer process can involve several offices working with different parts of the same record. When the next step depends on finding an email, reconciling a spreadsheet or copying a worksheet, the student waits while staff reconstruct the context. Ben Parsons starts his discussion with those everyday coordination problems.

His project brings a transfer dashboard and a credit-review workflow into the same working environment. The useful starting question is specific: where does one office lose the information it needs from another? Map that handoff before choosing the interface or designing another form.

Write down the event that starts the work, the information already available, the person responsible for the next action and the evidence that the step is complete. A short map can reveal that a request for a digital worksheet is really a request for a shared workflow.

In the recording · 07:59 ↗

Keep the conversation attached to its work

Ben describes an entity-scoped commenting form that presents exchanges between offices alongside the student’s record. Instead of following a separate email chain, staff can read the relevant notes where they are doing the work. The repeated note structure also lets him reuse the pattern for other populations.

Decide what one note represents and how it connects to the process being discussed. Preserve enough context for the next reader to understand who wrote it, what needs attention and whether a response is expected. Agree on which kinds of information belong in the shared exchange.

Keeping notes together can reduce searching, but their audience still needs deliberate review. Design the view around the duties of the people using it, then test access with the appropriate role. A convenient place to display information is only useful when the intended staff can use it and unrelated audiences cannot.

In the recording · 11:25 ↗

Build a small workflow around the real review

The credit-review example begins when a counselor asks whether a handwritten worksheet could become a Slate form. A conversation with the registrar reveals the larger opportunity. Ben describes a compact workflow with two bins, three movement rules and one review form, bringing courses, schools and transcripts into the review.

The important move is the discovery conversation. Ask the reviewer what they need to see, what they decide, where work waits and what should happen when information changes. Choose the smallest set of states that makes those responsibilities clear.

Test a normal case alongside an incomplete transcript and a revised submission. Confirm where each case belongs, who should act and how a correction returns to review. Keep the academic judgment with the responsible reviewer while making its supporting information and handoffs easier to follow.

In the recording · 12:14 ↗

Make the portal a dependable place to work

A staff portal helps occasional users find the right form, report or task without remembering the underlying navigation. Ben’s initial portal grows as more offices find uses for that shared entry point. The design challenge becomes maintaining a clear path through the work as the number of functions increases.

Organize around what a person needs to accomplish. Give each view a recognizable purpose and a named owner. Review whether a new tab clarifies the task or merely adds another place to look.

Data timing belongs in that design too. Ben describes information refreshed from another system overnight. Staff need to know when a view may lag behind its source and what to do when the displayed information conflicts with a recent update. For an embedded report, check the report system’s permissions as well as the surrounding portal.

In the recording · 16:23 ↗

Use feedback to improve the first useful version

Ben describes moving away from withholding a build until he has anticipated every possible situation. An early useful version lets colleagues try the process and contribute to its development. The partnership matters because the people doing the work can identify friction that the builder has not encountered.

Choose a bounded first release and document the exceptions that need a human handoff. Make it easy for staff to report an unexpected case without inventing a parallel spreadsheet. Bring those cases into the next review and decide which deserve a change to the shared pattern.

Adoption is part of the result. Ask someone who did not build the tool to find the next task, explain its status and identify the person who can help. A technically sound process still needs a usable explanation.

In the recording · 27:39 ↗

Measure the process without overstating the outcome

At the time of the interview, the revised transfer process had been used for the latter part of one cycle. Ben reports positive feedback and less energy spent on manual work, but says he does not yet have a quantitative measure. That distinction gives the next review a useful job.

Choose a small set of process measures: time waiting for a handoff, repeated requests for the same information, incomplete reviews or staff effort spent finding context. Define the start and end points and note changes in the workload. Compare those observations with the team’s feedback before attributing an enrollment result to the new workflow.

Leave the review with one adjustment and an owner. The project can improve coordination now while building better evidence for the next decision.

In the recording · 30:13 ↗

03 / A SMALL EXPERIMENT

Trace three transfer handoffs

For each fictional case, identify the missing context, the person responsible for the next step and the evidence needed to finish the handoff.

A transcript changes after review

A fictional transfer review is marked complete when an updated transcript arrives from a second institution. The document is visible, but nobody is assigned to revisit the evaluation. What should the workflow make clear?

Compare your reasoning

Identify the reviewer, the rule for returning changed information to review and how the prior evaluation remains understandable. Define expected behavior for a revised submission and an incomplete record, then test both cases with the process owner.

Revisit this moment · 12:14 ↗
The portal is one refresh behind

A staff member sees an old review status in a portal immediately after another office updates the source system. The import runs overnight. What should the team check before treating the portal value as current?

Compare your reasoning

Check the source update time and latest successful import. Make the refresh schedule and exception contact clear to staff, and define how urgent discrepancies are resolved. A convenient shared view still needs an understood data timeline.

Revisit this moment · 19:30 ↗
A shared note reaches the wrong audience

A reusable commenting pattern works for the transfer team. A proposed new portal tab would show the same note stream to a broader staff group whose tasks need only a status summary. How should the reuse be reviewed?

Compare your reasoning

Describe the information each role needs, preserve the detailed exchange for its intended audience and test access through the relevant roles and underlying controls. Reuse the pattern while reviewing its data scope; hiding a tab alone is not evidence that access is restricted.

Revisit this moment · 20:13 ↗
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 woodworking opening gives the later discussion of a useful first version a concrete counterpart: Ben enjoys turning a rough block into a finished bowl. Later, David asks for outcome measures rather than stopping at the build description, giving Ben room to distinguish staff feedback from empirical evidence.

Revisit the studio moment · 30:13 ↗

The Grain of the Process - Ben Parsons

An original companion song inspired by Ben’s interview, connecting the woodworking motif with gradual process improvement.

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