Make learning part of the workload
Staff empowerment gets difficult when the calendar tells a different story from the strategy. A team may be encouraged to learn, collaborate and improve its Slate work while every available hour is already committed. Jon Rowand brings the conversation back to a practical starting point: give people permission to learn, then set aside time they can actually use.
That time needs a focus. Someone working through a reporting problem may benefit from a community discussion; someone learning a new process may need a short demonstration and room to practice. Choose a useful channel rather than expecting everyone to follow every forum. Ask what the person wants to accomplish and what would help them do it.
Treat the learning block as real work when planning capacity. If urgent requests repeatedly replace it, discuss that tradeoff openly. Professional development cannot depend on a quiet week that never arrives.
In the recording · 06:48 ↗Choose the useful improvement you can support
A striking portal can make a project look deceptively simple. Jon separates must-have work from a wish list and points toward quick wins with meaningful impact. The team's available time, experience and competing responsibilities all affect what it can reasonably deliver.
Start with a task that repeatedly consumes staff attention. Identify the manual steps, the people involved and the part that could become easier. A functional portal or a modest integration may serve the need sooner than a heavily customized design. Agree on the essential behavior before adding the attractive extras.
An automation also creates work to maintain. Name the person who will notice a failed import or an unexpected result, and decide how the team will handle it. Judge the improvement by the burden it removes from the whole process, including the person who supports it.
In the recording · 08:12 ↗Keep the conversation open and the request visible
Jon describes a helpful approach to request intake: the support team can create the ticket. A conversation, chat or call can remain a comfortable way to raise an idea while the resulting work still enters a shared system. Staff do not have to choose between approachable colleagues and a dependable queue.
Capture the actual need while the context is fresh. Record the requested outcome, owner, relevant deadline and next step. Confirm your understanding with the requester. A hallway suggestion can become a tracked question without becoming an immediate promise to build.
The capacity conversation matters just as much as the ticket. When an urgent request arrives, show the existing commitments and ask what should move. A shared list makes that decision possible; it does not create more hours. The team still needs someone authorized to resolve competing priorities.
In the recording · 19:16 ↗Listen before demonstrating the tool
Cross-campus collaboration starts with the other office's work. Jon recommends asking what is most painful, time-consuming or manual in a colleague's day before introducing a technical solution. The answer may reveal a useful project that a tour of Slate features would have missed.
Bring the relevant stakeholders into the first discussion and make the proposed steps visible. Explain what you need from each office, what they can expect from you and where decisions remain open. Smaller working meetings can follow once responsibilities are understood.
A short case study can help another office recognize a similar problem. Describe the need, the approach and what happened without promising that the same design will fit every setting. Follow that conversation with a small, agreed next step rather than an expanding list of possible features.
In the recording · 28:13 ↗Agree on what the numbers mean
The analytics discussion adds another layer to collaboration. Two offices can produce different counts because they use different definitions of an application, an admitted student or an enrolled student. Before rebuilding a dashboard, compare the populations, filters and definitions behind the numbers.
Jon distinguishes quick operational questions in Slate from more complex analysis or storytelling that may benefit from a dedicated analytics tool. Choose based on the question and the people who need to use the result. Moving data into a different tool does not resolve disagreements about its meaning.
Write down the agreed definition, its owner and the point in time the count represents. Keep people responsible for reviewing discrepancies and maintaining usable data. A growing history of clean, consistently understood records gives future analysis a stronger foundation.
In the recording · 39:59 ↗Write down the answer you will need again
Jon's knowledge-base example begins with an ordinary need: remembering how a task was done. A short article can help its author next month and give a colleague a starting point today. Documentation becomes easier to sustain when it solves recurring questions.
Begin with a few useful sentences, the steps that matter and any known limitation. Let colleagues improve the explanation as they use it. Imperfect wording can be corrected, but a risky instruction still needs checking before someone follows it.
Choose one recurring question from the request queue and document its answer this week. Give the note an owner and a way to flag changes. That small habit connects staff development, support work and institutional knowledge without requiring a separate documentation project.
In the recording · 47:21 ↗