Start a literacy platform evaluation with the teaching problem

A district leader who asks for literacy software may be carrying several problems at once: uneven results, crowded teacher workflows, and uncertainty about what to measure. Begin with the instructional decision, then map the people and evidence needed to evaluate a tool responsibly.

Curriculum director Dana says, "Reading results vary by school. Can you guarantee your platform will raise scores, and will teachers need another login?" Account executive Theo replies, "I can help you build an evaluation around the results you want to understand. How are teachers currently using the three tools already in place, and which measures does the district trust?" Dana explains that baseline measures are still being selected. Theo says, "Student results depend on local instruction and implementation, so I cannot guarantee a score change. District IT should validate identity access before we describe the login experience. Could we invite curriculum, IT, principals, and a few teachers to a workshop? We can review current workflows, the proposed measures, and what evidence each group needs."

Theo gives Dana a decision process instead of a product claim. The workshop is useful because it prevents a demonstration from becoming the only source of information. It also gives teachers a place to describe duplicate work before a pilot design is set.

Prepare for a similar call by writing four discovery questions: one about instruction, one about current tools, one about measures, and one about review owners. In roleplay, listen for a request for an outcome promise. Practice moving back to the local conditions and the evidence the district will use to judge the evaluation.