Guiding Principles of Slate Implementation

 

Transitioning from a legacy system to Slate provides an opportunity to reconsider the full range of student success and advising business operations. Slate is process built, allowing individual institutions to customize at every step. Approaching an implementation with a creative and open mind will allow existing processes to move beyond limitations of previous technology tools, resulting in increased efficiencies.

Before your begin your implementation, we encourage you to review these principles:

1. Start simple and build over time.

In the first year of implementation, focus on building processes and understanding the architecture of Slate. Avoid focusing on special cases and design your new processes for the 99%.  As your knowledge of Slate grows, you will be able to customize as needed for the nuanced situations that may exist.

2. Use all available resources.

Slate provides extensive documentation, webinars, and integrated help resources. Make a concerted effort to understand the functionality and underlying logic. Avail yourself of the Slate community through the user forums, our Service Desk, and the Technolutions experts who stand ready to assist you.

2. Commit to creating a sustainable process.

Slate’s out-of-the-box functionality immediately offers new and improved ways of doing business. Building processes using best practices will make future updates much easier, with minimal time investment. 

3. Be creative.

Instead of simply recreating an old system within Slate, think carefully about how to structure current processes in an ideal world. Slate can support and foster many different, efficient business processes, so be creative—the possibilities are endless!

Was this article helpful?
2 out of 2 found this helpful