Practitioner Readiness
Readiness is not about having every capability in place. It is about having enough clarity, ownership, expertise, and capacity to build the next capability responsibly. Use this assessment to surface dependencies, identify constraints, and determine what needs attention before expanding the work.
Assess Your Readiness:
Consider eight areas that shape whether an integrated Student Affairs Data Lake can be built and sustained. Rate each from 1 (not established) to 5 (sustained and routinely reviewed) based on current practice, not future plans.
| Domain | Statement | Rating |
|---|---|---|
| Strategic Alignment | Are the decisions and institutional priorities this work should support clear? | |
| Data Foundation | Are sources, definitions, identifiers, quality expectations, and refresh needs understood? | |
| Governance & Access | Are ownership, approval, secure use, review, and access lifecycle clear? | |
| Partnership | Are roles, dependencies, escalation, and shared commitments explicit? | |
| Methods & Validation | Can data be made analysis-ready and appropriate methods selected? | |
| Talent & Capacity | Do you have the expertise, time, backup, and operational support needed? | |
| Adoption & Action | Are users prepared to interpret evidence and translate it into decisions and action? | |
| Sustainability | Can integrations, documentation, refreshes, and recurring work be maintained? |
RATING SCALE:
1 = Not established | 2 = Emerging | 3 = Partially established | 4 = Established | 5 = Sustained
Mostly 1s and 2s- Build the foundation:
Your assessment suggests that some of the conditions needed to support an integrated data environment are not yet firmly established. This is a good time to narrow the scope, clarify ownership, strengthen standards, and build the partnerships needed to support the work. Focus on creating a stable foundation before expanding demand or analytical complexity.
Mostly 3s- Build through practice:
You have many of the core elements in place, but practices may still be inconsistent or dependent on individuals. A focused, high-value use case can help you strengthen repeatable processes while demonstrating what is possible. Use the experience to clarify what needs to become more consistent, documented, and sustainable.
Mostly 4s and 5s- Build for scale and sustainability:
Your assessment suggests that the core conditions are largely established and the work is positioned to expand selectively. Focus now on monitoring value, strengthening adoption, documenting practices, building backup capacity, and creating opportunities for continued learning.
The assessment tells you where to focus. The 90-day play helps you turn that insight into action.
Once you have identified the priority, move it through a focused cycle of confirm, design, build, review, and decide. The goal is not to solve everything at once, but to build and test one capability well enough to determine what should happen next.
1 | Weeks 1-2 • Confirm | Validate ratings with partners; identify the single most important dependency and decision authority. |
|---|---|---|
2 | Weeks 3-4 • Design | Define the minimum viable capability, scope, owners, milestones, risks, and evidence of completion. |
3 | Weeks 5-8 • Build | Complete the foundational work; document decisions; test the process with a bounded use case. |
4 | Weeks 9-10 • Review | Conduct partner, governance, validation, and user review; address gaps before expansion. |
5 | Weeks 11-12 • Decide | Adopt, revise, pause, or scale based on evidence—not momentum alone. |
READINESS PRINCIPLE: Readiness is not having every capability. It is having enough clarity, ownership, skill, and capacity to deliver the next capability responsibly.