Start with a piece of work that crosses boundaries
A request for a portal change can also be a question about data ownership, staff responsibilities and the next message a student receives. Solving only the visible screen may leave the underlying problem intact. The useful learning opportunity is often where two areas of work meet.
The Next Slate Practitioner Stack connects eight conference sessions through that idea. David describes advanced practice as translation: understanding a local need, selecting an appropriate structure, checking the evidence and leaving work that other people can use. Technical depth remains valuable, alongside the judgment to connect it to a purpose.
Choose a recurring piece of work you already understand well enough to examine. List the skills it depends on and where the handoff becomes uncertain. That gives professional development a concrete target instead of another open-ended intention to learn more features.
In the recording · 00:29 ↗Practice evaluating AI output
The AI discussion focuses on supervision. Drafting, summarizing and troubleshooting can save effort, but the practitioner still needs a reliable source, a clear task and a way to inspect the result. A convincing answer is not evidence that a policy statement or proposed change is correct.
A useful first project is a review checklist for one bounded workflow, such as drafting support documentation from approved material. Identify which facts must be traced to a source, which parts need technical testing and who decides whether the result is ready for use. Use examples that fit the institution’s data-handling requirements.
For code or portal work, include accessibility, fallback behavior and maintainability in the review. Record what was changed after checking the first output. Those corrections make the learning visible and give the next practitioner something more useful than a prompt that happened to work once.
In the recording · 04:45 ↗Make a data-design choice explainable
Data architecture supplies another practical development path. Before adding a field or dataset, describe what the information represents. Is it a single value, a repeating relationship or reusable configuration? Who maintains it, how often does it change and which processes depend on it?
Turn one real design discussion into a short decision guide. Compare the plausible options, record why one fits and describe what would make the team revisit it. Include missing values and ownership, rather than stopping at the layout of fields.
Pair that guide with a reporting question. A structure becomes easier to assess when someone explains the decision it must support. A leadership trend, counselor action list and workflow queue may use related data while requiring different levels of detail, freshness and interpretation.
In the recording · 07:57 ↗Translate between local needs and shared standards
Shared Slate environments create another kind of technical work. Departments may have different schedules, terminology and responsibilities while depending on common definitions and controls. A local request can call for configuration, training, documentation or a process conversation.
An ownership map is a useful learning artifact here. Identify what is shared, what may vary locally, who approves changes and where support requests go. Trace one proposed variation into the populations, messages, reports and staff routines it could affect.
Keep the exercise connected to the people who own those decisions. Ask the designated owner to review permission dependencies before proposing a change. The skill is recognizing when a seemingly small adjustment needs another perspective before it becomes part of the shared system.
In the recording · 13:56 ↗Choose one primary skill and one useful partner
The self-assessment pairs confidence with evidence. For each area, ask where it appears in current work and what you could produce to demonstrate progress. Use the rating to choose a manageable next project, then let the result show what you learned.
The episode recommends one primary skill and one adjacent skill for a quarter. Communications governance can pair with query literacy so the audience logic supports the message. Workflow governance can pair with training so staff understand the statuses they use. AI evaluation can pair with documentation so the review process travels with the draft.
Name a reviewer and an intended user before building. A report note, query pattern, teaching brief or campaign map is strongest when someone else can try it. Define the question their feedback should answer, rather than asking only whether they like the result.
In the recording · 18:22 ↗Build, test, then teach or revise
Use the three-month rhythm as a planning frame. In month one, create a small artifact. In month two, test or use it through the appropriate review process. In month three, teach it, document it or revise it based on what happened.
Keep a record of what was created, how it was used, what changed and what you can now explain. A first version may reveal that the original question was too broad or a dependency was missing. That is useful feedback for the next iteration.
The team does not need every person to specialize in every area. It needs a visible map of strengths, gaps and reliable handoffs. One well-chosen project can improve both a practitioner’s skill and the next person’s ability to work with the result.
In the recording · 20:58 ↗