Explain the outcome before the configuration
A new system brings a long checklist. The institution still needs a clear answer to a shorter question: what should become easier for the people using it? In this Visiting Artisan conversation, Kristina Kelpe keeps returning to that distinction as she connects implementation work with student success.
Her starting point is understanding. Ask questions until you can explain the problem back and the people doing the work recognize it. Then describe the desired outcome to someone in another campus office. If the explanation depends on knowing the old system's screens and workarounds, step back another level.
That test changes the conversation. Getting a student identifier earlier might support a sense of belonging or enable a downstream service. The schedule for sending a file is a later design decision. Capture the reason first so a new implementation does not inherit a sequence nobody needs anymore.
In the recording · 26:55 ↗Keep institutional responsibilities visible
An implementation partner can configure technology while important institutional work remains unfinished. Kristina identifies testing, validation, user experience and effective internal processes as responsibilities that need explicit attention. A working configuration does not automatically establish how an office will operate.
Separate technical troubleshooting from functional acceptance. Someone may need to resolve security access or a configuration mismatch before a busy staff member can meaningfully judge whether the process meets the requirement. Give that preparation time and ownership instead of treating every failed test as a user problem.
Build the new operational calendar alongside the system. Admission decisions may still happen on familiar dates, but the preparation, checks and handoffs can change substantially. Training and job aids should describe the new work. Data validation must also account for differences in the source and destination data models rather than assuming every field moves one for one.
In the recording · 15:25 ↗Choose the tool with the people who maintain it
Kristina describes complementary strengths in Workday Student and Slate: delivered student-information processes on one side, flexible communications, forms and workflows on the other. Her examples include registration, graduation review and requests to change a major. These are design choices to evaluate against a particular institution's needs.
A flexible form can reduce repeated data entry and guide someone toward the next valid choice. That benefit depends on the whole process, including where the authoritative data lives and what happens after submission. Sketch the student experience and the staff review before choosing where each step belongs.
Staffing belongs in that choice too. A solution requiring specialist development has different maintenance needs from one a techno-functional team can support. Ask who will adjust the process when requirements change and how that knowledge will survive a staff transition.
In the recording · 17:15 ↗Make the destination's data requirements explicit
For Slate-to-Workday integrations, Kristina recommends understanding the destination structure and reference identifiers before sending data. Enterprise Integration Builder templates can help make those requirements concrete. She notes that some templates can be generated with data, while qualifying that availability depends on the particular template.
Slate's export codes and translation tables can prepare values in the form the receiving system expects. This can keep routine mapping changes accessible to the team that understands the underlying programs rather than placing every adjustment inside a specialist integration.
Use a newly added program as a practical review case. Identify its destination reference code, document where the mapping is maintained and check the exported value. The goal is a maintainable handoff, with a clear answer to who notices and repairs an unmapped value.
In the recording · 23:27 ↗Document the process at more than one level
A detailed integration diagram and a counselor's explanation serve different readers. Kristina recommends workflow maps supported by a narrative account of why the steps exist, with a simpler view for people who need to understand the process without managing its technical details.
Start with the desired outcome, then show decisions, handoffs and dependencies. Use the narrative to preserve context that would otherwise be lost in a box or arrow. Give frontline staff enough information to recognize when their action changes someone else's next step.
Keep the documents connected as the implementation changes. A readable overview that describes an old process can be as misleading as an accurate technical document that nobody outside the project team understands.
In the recording · 41:26 ↗Make validation part of ordinary work
Kristina's recommendation for proactive reports is deliberately practical: look for records that fail an expected condition and make those exceptions visible in an internal dashboard. Mistakes will happen. A recurring check creates an opportunity to correct them before they become a student-facing problem.
Choose one meaningful condition, explain who should satisfy it and identify the person who will review exceptions. Agree on the next action for a record that appears. A report earns its place when somebody can use it to resolve a problem, rather than merely observe a growing count.
Bring the same approach to the implementation itself. Keep asking what the work is for, whether people understand it and whether the operations can sustain it. Those questions give the checklist a purpose.
In the recording · 43:50 ↗