Alex Chen — Technology Procurement Manager

Why do you consider technology procurement a leadership role rather than a purchasing function?

Because the purchase order is one of the last steps, not the first. A technology contract shapes instruction, privacy, accessibility, staff workload, interoperability, security, and the district’s future choices. If we only ask whether money is available and the vendor form is complete, we have missed most of the leadership decision.

My job is to help the district make a promise it can keep. We are promising that the product serves a real need, that staff can support it, that student information will be handled responsibly, and that we understand the full cost. That requires educators, technology staff, privacy and security reviewers, business services, and end users to see themselves as part of one decision rather than a sequence of approvals.

How does technology strengthen your own ability to lead the process?

We use a contract repository, application inventory, approval workflow, risk register, and renewal dashboard. The important thing is not having five tools; it is connecting the information. I can see who owns a service, what data it receives, which schools use it, when the agreement renews, and whether security or accessibility commitments remain open.

That visibility gives us time. Before we built it, a renewal might surface two weeks before expiration, when the district had little negotiating leverage and schools feared losing access. Now owners receive notice months earlier and must confirm continued need, usage, unresolved issues, and funding. Technology increased my agency by moving the conversation to a point when the district still has choices.

What was your most important procurement win?

We created a fast, understandable review path for lower-risk instructional applications. Teachers were frustrated because every request seemed to enter the same long process, whether the tool collected student records or simply displayed public content. Some staff began using free applications without review because they believed the official process could not respond in time.

We worked with privacy, security, curriculum, accessibility, and technology teams to create risk tiers. A low-data, low-integration tool can now follow a shorter review with clear boundaries, while systems handling sensitive information receive deeper review. We published the questions, expected timelines, and status of each request. Approval time dropped for low-risk tools, and unapproved use also declined. The win was not weakening review. It was making governance usable enough that people chose to participate.

Was there a contract negotiation that changed district practice?

Yes. We were replacing a learning platform, and an early proposal made it easy to import information but expensive and technically difficult to leave. The vendor’s demonstration focused on features, while our data and curriculum teams focused on implementation. We added an exit scenario to the evaluation: if the agreement ended in three years, how would we retrieve courses, records, configurations, and documentation in usable formats?

That question changed the negotiation. We secured defined exports, transition assistance, deletion verification, and limits on end-of-contract charges. We also required documentation for the integration rather than accepting a proprietary connector as a black box. We have not needed to leave the platform, but the district now uses exit requirements in major technology solicitations. Preserving the ability to change direction was the win.

What makes this work difficult inside a school district?

Urgency and fragmented budgets. A program may receive grant funding and need to act quickly, while the staff who will manage accounts, integrations, records, and support are not included in the budget conversation. The subscription looks affordable because the hidden labor belongs to someone else.

There is also understandable fear that review means “no.” If the process is mysterious or takes months, people route around it. I spend a lot of time explaining that our goal is not to eliminate risk; it is to understand the promise we are making and decide deliberately. Review teams have to meet departments halfway by publishing expectations, responding on time, and distinguishing a correctable concern from a reason to stop.

Which vendor claims require the most follow-up?

“Seamless integration,” “OneRoster compliant,” “AI powered,” “FERPA compliant,” and “single sign-on” all sound reassuring and tell me almost nothing by themselves. I ask which version and services are supported, whether the exact product is certified, what data moves, which party operates each connection, what costs extra, and what happens when a record changes or is deleted.

Legal compliance claims need the same discipline. A vendor cannot decide the district’s authority or educational purpose for us. We still need to examine minimization, access, retention, subcontractors, security, and contract terms. The best vendors welcome specific questions because precise expectations protect both parties.

How do you calculate the real cost of educational technology?

The license is only the visible part. We consider implementation, identity and rostering, data cleanup, training, substitute coverage, support, accessibility remediation, integrations, storage, transaction limits, renewals, upgrades, and exit. We also ask what current product or manual process will be retired. If nothing stops, the new purchase may simply add another layer of work.

One question I always ask is, “Who inherits this when the grant ends or the project champion leaves?” If the answer is unclear, the product is not operationally ready. Total cost is not just financial; it includes staff attention and organizational complexity.

What advice would you offer aspiring educational leaders?

Learn to turn a need into a testable requirement before falling in love with a product. Invite the people who understand instruction, privacy, security, accessibility, data, support, and fiscal impact early enough to shape the decision. Ask vendors to demonstrate the district’s workflow with realistic exceptions, not only the polished path.

Most importantly, preserve agency. Understand how data returns, how services end, and how the district can change direction without harming students or losing its own work. Procurement is leadership because it determines which future choices remain available.

Reflective questions

1. How does a technology contract influence teaching and leadership after the purchase decision?
2. Which information should a district require before permitting a demonstration to shape requirements?
3. How can a review process remain rigorous without driving staff toward unapproved tools?
4. What evidence should support a vendor’s claim of standards compatibility or legal compliance?
5. Which lifecycle costs are commonly omitted from technology proposals?
6. How do contract-exit terms preserve future district agency?