Development and Implementation of a Shared Vision
What this domain tests
This domain asks whether you can build a vision collaboratively, communicate it clearly, align resources and actions to it, and monitor whether it is actually changing student experience. Distinguish vision (desired future state), mission (purpose), and goals (measurable targets). CPACE-style questions reward an inclusive, data-informed, equity-centered, cyclical process.
Concepts to know
- Collaborative development with staff, families, students, and community partners-not an administrator-only product.
- Grounded in student outcome data and stakeholder input, including groups historically underserved.
- Plain-language communication through multiple channels, repeated and modeled by leaders.
- Enactment through school plans, budgets, hiring, professional learning, and the master schedule.
- Monitoring with indicators, then revisiting the vision as conditions change.
- Equity lens: which students are not served by current outcomes?
Traps
A common trap is the principal who writes a slogan and announces it. Another is labeling a mission statement or a single goal as a vision. Watch for answers that emphasize public relations over stakeholder ownership, or that skip resource alignment. Also beware of choosing “revisit the vision” as a first step when the real problem is implementation.
Worked example
A stem says a district board adopts a new vision. The strongest first step is usually to engage site stakeholders to interpret that vision against local data and identify gaps-not to print posters, rewrite it alone, or wait for a plan. Rule of thumb: if an action does not change adult behavior, resource allocation, or student experience, it is communication, not implementation.