From AI Pilot Evaluation to Educator Adoption Support
Evaluated three AI platforms through authentic educator and student workflows, synthesized structured user feedback, usability findings, bugs, and instructional value that contributed to the district’s MagicSchool selection, then supported educator adoption through practical demonstrations, workflow guidance, troubleshooting, Q&A, and follow-up.

Verified Professional Experience
Salt Lake City School District | Franklin Elementary & Indian Hills Elementary
2024–2026 | Evaluation → Adoption Support
Skills Demonstrated
Product Evaluation, Pilot Execution, User Research, Usability Testing, Structured Feedback Synthesis, Decision Support, Stakeholder Communication, Implementation Support, User Enablement, Technology Adoption, Troubleshooting, Change Support
Challenge
Salt Lake City School District was evaluating three AI platforms, but a useful platform decision required more than comparing feature lists. The tools needed to work in authentic educator and student workflows, provide meaningful instructional value, and avoid usability problems that would create barriers to adoption. After MagicSchool was selected, the challenge changed: educators with different levels of technical confidence needed practical support turning an unfamiliar platform into usable day-to-day workflows.
Role & Scope
At Franklin Elementary, I was selected by my principal to participate in the district AI pilot and focus-group work. I independently learned and tested three AI platforms, developed authentic educator and student use cases, gathered structured feedback through Microsoft Forms and notes/logs, documented bugs, usability limitations, instructional value, and recurring friction, and presented findings to district stakeholders. That evidence contributed to the district’s selection of MagicSchool. The following school year at Indian Hills Elementary, my role shifted from evaluation to adoption support: I helped educators use the selected platform through demonstrations, practical workflows, written guidance, troubleshooting, Q&A, and follow-up tailored to different levels of technical confidence.
Approach & Execution
I evaluated the three platforms through real educator and student workflows rather than treating the pilot as an abstract feature comparison. I developed practical use cases, tested how the tools performed in authentic situations, gathered structured user feedback, and documented both instructional value and points of friction. I then synthesized those observations and shared the findings with district stakeholders. The following school year, I applied that practical understanding to adoption support by demonstrating usable workflows, providing written guidance, answering questions, troubleshooting recurring barriers, and adjusting support based on each educator’s level of technical confidence.I evaluated the platforms through real workflows rather than treating the pilot as an abstract feature comparison. I developed realistic use cases, tested how each tool performed in authentic educator and student situations, gathered structured user feedback, and documented both value and friction—including usability limitations, bugs, instructional usefulness, and potential implementation barriers. I synthesized those observations into findings for district stakeholders. After the district selected MagicSchool, I applied that product knowledge to adoption support by demonstrating usable workflows, creating practical guidance, answering questions, troubleshooting recurring barriers, and adjusting support based on each educator’s level of confidence with the technology.
Key Decisions & Rationale
I deliberately centered the evaluation on what users actually needed to accomplish rather than on which platform had the longest feature list. A tool could offer impressive capabilities and still create adoption problems if educators found it confusing, unreliable, or difficult to integrate into real workflows. I therefore captured both value and friction so stakeholders could evaluate the platforms in context. Once the district selected a platform, I shifted from judging the technology to helping people use it successfully, adapting support to recurring barriers and individual confidence levels rather than assuming every educator needed the same kind of training.
Outcome & Impact
The evidence I gathered and presented during the Franklin pilot contributed to Salt Lake City School District’s selection of MagicSchool. The following year at Indian Hills, I supported educators as they translated that selected platform into practical day-to-day workflows through demonstrations, written guidance, troubleshooting, Q&A, and follow-up. Together, the two phases show a continuous progression from evaluating technology and informing a decision to supporting users after that decision was made.
What This Demonstrates
This work demonstrates my ability to learn unfamiliar technology quickly, evaluate products through authentic user workflows, gather and synthesize structured feedback, identify usability and implementation barriers, communicate decision-relevant findings to stakeholders, and support users through technology change. It reflects strengths in product evaluation, pilot execution, user research, usability testing, decision support, implementation support, user enablement, troubleshooting, and technology adoption—and shows that I can connect what a product promises with how people actually experience and use it.