# data[].attributes.body
Teacher as the designer!

# data[].attributes.body
what fears? from Lana: any fears they might have if we only addressed one or the other (design vs. tech knowledge of the tool)

# data[].attributes.body
Students can access and create content on their mobile devices.

# data[].attributes.body
Teachers collaboration on Professional Development days or In-service-days.

# data[].attributes.body
How do we provide them enough information so they can take this back to their campus and have it be meaningful?

# data[].attributes.body
Can we convince the teacher that they are developers.

# data[].attributes.body
Teachers' collaboration by grade level  and by campus.

# data[].attributes.body
By designating a campus "admin", campuses can customize according to their needs.

# data[].attributes.body
Teachers/Curriculum Dept. can share modules and leave feedback for others to benefit from.

# data[].attributes.body
Are they learning this platform while still under development

# data[].attributes.body
So teachers can collaborate in creating resources. Especially Dual Language
teachers.

# data[].attributes.body
Collaborative module building by placing work in the AISD Commons. Others can add Bilingual language, Adaptive, Dyslexic etc resources

# data[].attributes.body
The Commons could eliminate some planning time, by teachers being able to use/share lessons from other educators. They can also share their own lessons.

# data[].attributes.body
Explain and provide support access.

# data[].attributes.body
Teachers can design their own lessons and courses. As well as differentiate for their individual student needs.

# data[].attributes.body
Allows teachers autonomy over their learning environment.

# data[].attributes.body
Have a common place to pull resources from

# data[].attributes.body
Do we support the teacher's technical skills when the platform is still is still being developed.

# data[].attributes.body
The students can work collaboratively via the LPS. It intuitively integrates tech and places it into the hands of the students.

# data[].attributes.body
Framing our approach as you are a designer(autonomy) and here are your tools(belonging and mastery)

# data[].attributes.body
Share examples of modules at different grade levels.

# data[].attributes.body
By combining just enough "how-to" with "teacher as designer", we will help ease concerns about both.

# data[].attributes.body
It organizes all the resources for a lesson into one place.

# data[].attributes.body
It will ease any fears they might have if we only addressed one or the other (design vs. tech knowledge of the tool)

# data[].attributes.body
Small steps.. deliverables...norms...how to get started

# data[].attributes.body
It integrates TEAMS, granted there are limitations.

# data[].attributes.body
Learning takes place in an interactive learning environment

# data[].attributes.body
It (potentially) makes efficient use of teacher time.

# data[].attributes.body
It is empowering!

# data[].attributes.body
How might we design a professional learning experience that promotes the philosophy of "teacher as designer" while supporting teachers with technical skills needed for implementation of the Pilot