# Vetting & Choosing EdTech Tools (Workshop) > A ready-to-run PD workshop on choosing edtech tools by learning value, privacy, and evidence. Run-of-show, handout, follow-up. *A ready-to-run professional learning workshop from K12 Academics. Source page: https://pd.k12academics.com/vetting-edtech-tools-workshop.html* There are endless edtech tools, and most do not improve learning. Choosing well means asking what learning problem a tool actually solves, whether it is worth the time and privacy cost, and whether the evidence supports it, before adding one more app. Most edtech does not improve learning; choose tools by the learning problem they solve, their privacy and time cost, and the evidence, not by novelty. ## Why it works Schools adopt far more technology than improves outcomes, and many tools add workload, distraction, and privacy risk without a clear learning benefit. A simple vetting habit, start from the learning goal, ask what problem the tool solves, weigh time and privacy cost, and look for evidence, prevents tool overload and protects student data. **The research:** Research on edtech effectiveness; FERPA and COPPA privacy requirements. ## The run-of-show ### Staff meeting (15 minutes) A fast introduction to plant one routine. **Goal:** everyone leaves with one thing to try. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 3 min | Hook | How many apps do your students juggle? Do they all help? Name it. | You are surfacing tool overload. | | 0:03 | 5 min | Mini-teach | Vet by learning, privacy, and evidence. One slide. | | | 0:08 | 5 min | Plan one | Name the learning problem one tool solves. Turn and talk. | | | 0:13 | 2 min | Commit | Each person names a tool to vet. | | ### PLC / team meeting (45 minutes) The standard version. **Goal:** every teacher leaves with something designed for a real upcoming lesson. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 5 min | Hook | A flashy tool vs one that solves a real problem. Which lasts? | Let them separate novelty from value. | | 0:05 | 8 min | Mini-teach | The vetting habit and the privacy questions. | | | 0:13 | 12 min | See it in action | Vet a sample tool together. Adopt, drop, or simplify? | Model the questions. | | 0:25 | 12 min | Design | Vet a real tool you use or are considering. | Protect the full time. | | 0:37 | 5 min | Share | Swap in pairs; check the privacy answers. | Keep it in pairs. | | 0:42 | 3 min | Commit + follow-up | Lock in the decision; set the check-in. | | ### Half-day institute (~3 hours) A deep session for a PD day. **Goal:** built, practiced, and a rollout planned. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | Block 1 | 45 min | Experience + why | Tool overload, then the vetting habit. | | | | 15 min | Break | | | | Block 2 | 60 min | Vet the toolkit | Teams vet their current tools and prune. | Protect privacy. | | Block 3 | 45 min | Practice | Vet a proposed tool against the criteria. | Starting from learning is the skill. | | Close | 15 min | Plan the rollout | Adopt the vetting habit; set the check-in. | | ## The core activity: vet one tool Teachers leave having vetted one tool against learning value, privacy, and cost. - Pick a tool you use or are considering. - Name the specific learning problem it solves, and whether a simpler approach would do. - Weigh the time and privacy cost: what data, where it goes, FERPA and COPPA. - Decide: adopt, drop, or simplify. ## Facilitator notes - Start from the learning goal. - Ask the privacy questions, and weigh the time cost. - Prefer fewer, better tools. ## Adapt it - **Elementary:** simple, privacy-safe tools; fewer is better. - **Secondary:** tools matched to real tasks. - **Leaders:** vet and approve tools at scale, and protect data. ## Participant handout One page for every teacher. Print it, or save it as a PDF. ### Vetting EdTech: learning, privacy, evidence **Choose on purpose:** what problem it solves, the time and privacy cost, and whether evidence backs it. - The tool: __________ - The specific learning problem it solves: __________ - Whether a simpler approach would do: __________ - The time and privacy cost (data, FERPA/COPPA): __________ - My decision (adopt, drop, simplify): __________ ## Make it stick - Vet before adopting. - Prefer fewer, well-chosen tools. - Bring a tool you dropped, or kept, to PLC or leadership. ## Common questions **How do I know if a tool is worth it?** Start from the learning goal, not the tool. Ask what problem it solves that a simpler approach does not, what it costs in time and privacy, and whether there is evidence it helps. **What privacy questions should I ask?** What student data it collects, where that data goes, and whether it complies with FERPA and COPPA. If you cannot answer those, do not use it with students. **Isn't more technology better for engagement?** Novelty engages briefly, then fades, and tool overload adds friction. Fewer, well-chosen tools that solve real problems beat many flashy ones. ## Go deeper - [ISTE Standards for Educators](https://iste.org) ## Build it into a bigger day - [AI Literacy for Teachers](https://pd.k12academics.com/ai-literacy-for-teachers-workshop.html) - [Building an AI Policy](https://pd.k12academics.com/building-ai-policy-workshop.html) - [Blended Learning Models](https://pd.k12academics.com/blended-learning-models-workshop.html) --- Full workshop page: https://pd.k12academics.com/vetting-edtech-tools-workshop.html All workshops: https://pd.k12academics.com/