ITEC Fall Conference 2026

Qweebi is an online makerspace platform that allows students to complete hands-on STEM projects directly on their computers. Designed for grades 3–8, it offers ready-to-use, standards-aligned projects that can be searched by grade level or topic. Each project includes complete Google Slide lessons with built-in teaching videos and instructional materials, making implementation simple for teachers.
Students can progress through projects at their own pace while teachers maintain classroom control by locking levels to keep students on track. The platform encourages testing, problem-solving, and improvement through virtual engineering challenges. I have used multiple Qweebi projects with different grade levels and have seen students actively engage in critical thinking and problem-solving throughout the process. Because everything is completed digitally, no additional supplies, setup, or cleanup are required.


I would be happy to run a session to introduce this STEM platform to teachers. I would have them be the "student" to work through a bit of a lesson and then show them how to manage it all from the teacher's view. 
I really enjoyed utilizing these lessons along with the other things I do in my STEAM class and wanted to tell others about it.  This virtual platform would be simple to implement in a regular classroom as well since it is all online. 

• 
  
  

Bring one assignment you actually give. We'll hand it to AI and get back a complete response in about eight seconds — organized, on topic, free of errors. It would earn a B.


Then you'll take it apart in ninety seconds, because you can see what's missing and a chatbot cannot teach anyone to do that.


Most AI guidance prepared us for the wrong failure. We were told to watch for fabricated sources and bad math as things you catch by checking. This is different: there's nothing to catch. It's correct all the way down with no thinking in it anywhere.
The essay was never the learning. It was the best evidence of learning we had, and for a century it was excellent evidence. That link broke. Your teaching didn't.


You'll leave having added one line of sight to one assignment, in wording you'd really use, plus a card of ready-to-paste language for four more.

AI conversations often begin with tools, policies, and concerns about misuse. While those conversations are important, they don't always help educators answer a more fundamental question: What do we want AI to support?

This session explores a practical, human-centered framework built around four questions that can help educators make thoughtful decisions about AI while keeping learning at the center of the conversation. Drawing from the ongoing work of Dallas Center-Grimes Schools, participants will explore how preserving what matters, building confidence, balancing consistency with professional judgment, and continuously learning from feedback can help schools navigate AI in ways that fit their own context.

Rather than offering one model to replicate, this session focuses on questions and ideas that teachers, instructional coaches, building leaders, and district teams can adapt to support meaningful learning, student thinking, and responsible AI use.

This session explores providing effective digital feedback, with and without AI. It focuses on applying principles of actionable, specific, timely, and targeted feedback in digital environments. Participants will gain strategies to improve feedback practices and empower student learning in the AI era. Feedback is too important not to do well.

You've been shown dozens of AI tools in the last two years. The number you still use is probably one or two.
That isn't a discipline problem. "What's the best AI tool?" has a shelf life of about six weeks with the model updates, the pricing changes, your district blocks it. The question that doesn't expire is: what's the workflow I want to own?
This session is a four-step pattern for answering that with Name, Map, Mark, Lock and three of the four steps never touch a product, which is exactly why workflows built this way survive when the tools change.
You'll watch one real workflow built live from scratch: sixty exit tickets, clustered by misconception instead of by score, running automatically every Friday afternoon. Then you'll design your own, and mark the steps where your professional judgment has to stay.
Tools are rented. Workflows are owned.