Families rarely think to ask how educational technology gets chosen, which is unfortunate, because the answer explains most of why school tools often seem out of step with both teachers' needs and students' realities. Teachers do not, on the whole, pick the tools that arrive in their classrooms. The actual mechanism is more complicated, and the complications matter.
The procurement cycle
Large district technology purchases, the kind that result in every student getting a Chromebook or every school switching from one LMS to another, operate through formal procurement processes. A district identifies a need, issues a Request for Proposals, receives bids from vendors, evaluates them against criteria that are partly technical and partly administrative, involves a selection committee, sometimes pilots with a subset of schools, and eventually makes a recommendation to the school board, which votes. From initial need identification to deployment, the process routinely takes one to three years.
That timeline has consequences. The technology going into classrooms this fall was likely selected based on evaluations done two or more years ago, against criteria developed before current classroom realities were fully understood. By the time a platform is deployed at scale, the teachers who will use it have often had no meaningful input into the selection, and the problems that emerge in actual use were not visible in the vendor demonstration.
The vendor relationship
Educational technology is a large and lucrative market, and vendors invest substantially in the sales process. The investment is not nefarious, it is standard enterprise sales, but it shapes what districts see when they are evaluating tools. Vendors present polished demonstrations, provide reference customers who had good experiences, and show research (sometimes internally funded) that supports their platform's efficacy. What is harder to see in a procurement process is what the tool looks like for a frustrated teacher on a slow internet connection with a class that is half engaged, or what happens when the vendor's support queue is backed up for two weeks.
Teacher input in procurement varies widely. Some districts have genuine teacher representation on selection committees. Others involve teachers primarily through a brief pilot where positive feedback is solicited. The further the people making the selection sit from the classroom, the more the decision will reflect administrative and technical criteria over pedagogical ones.
The platform fatigue problem
One consequence of school technology procurement is what teachers call platform fatigue: the accumulation, over years, of systems that each solved a specific problem and none of which talk to each other. An LMS for assignments, a separate gradebook, a different communication tool for parents, a content filtering system, an attendance platform, a special education tracking system, a video conferencing tool. Each was procured at a different time, by a different committee, on a different contract cycle. Teachers navigate all of them; students navigate whichever subset their teachers use; parents receive notifications from several different apps about the same child.
The integration problem is real, widely acknowledged, and genuinely hard to solve, because the contracts are on different renewal timelines and the data does not move cleanly between systems. Districts trying to consolidate often discover that switching costs are high and that consolidation platforms introduce their own problems. The technology landscape at most schools is less a designed system than an accumulated stack of decisions made at different moments under different pressures. That history is most of the answer to "why does school tech work this way?": it was the best option available at the time someone had to make a decision, and the decisions never had a chance to cohere.