• Design a domain model that enables both institutions (districts, schools, ministries) and individuals (teachers, coaches) to use Playlab successfully • Clarify how users, organizations, apps, and permissions relate to each other as Playlab scales • Ensure the model supports Playlab's current partnerships while creating flexibility for future growth • Specify the controls that give institutions visibility and confidence: user management, app distribution, usage reporting, and appropriate content governance • Balance institutional needs with Playlab's commitment to educator agency—administrators need oversight without locking down what makes Playlab powerful • Work with the partnerships team to prioritize based on what's actually blocking deployments • Define requirements for getting roster data into and out of Playlab at scale—supporting districts and organizations with varied SIS configurations • Specify integration patterns that work across the fragmented K-12 data landscape (Clever, ClassLink, OneRoster, custom exports) • Design flows that reduce manual work for IT administrators and partnership teams