Speaking

Happily employed.
Open to speak.

I speak to education agencies, conferences, and leadership teams about AI literacy, responsible AI in public work, and the data foundations that decide whether either one holds up.

About Mike
Mike Hadaway at a workstation surrounded by monitors displaying code
25+years in enterprise data
7statewide education data systems delivered
250+district implementations
20+state and regional education agencies advised
Talk topics

Three subjects, drawn from the work.

Each session is built around one question: what decision gets better because we did this? That keeps the discussion away from impressive demonstrations and on public responsibility.

Topic 01

AI literacy is more than prompt training.

Prompt training teaches people how to ask. It does not teach them how to judge. This one is about the part that stays human: knowing which sources count, noticing when a confident answer is quietly filling a gap, and deciding how much checking the work has earned.

  • Why fluency is not evidence, and how plausible errors get past busy people
  • Grounding: giving authoritative sources control over inference
  • Verification matched to consequence rather than applied uniformly
  • The four Operator disciplines: Frame, Ground, Verify, Govern

For district and agency staff, instructional leaders, and professional learning teams

Topic 02

AI in the public square.

A weak internal draft can be corrected. An unsupported answer sent to a family, or quietly wired into a workflow, becomes an institutional action. This one is about what has to be true before an agency lets that happen.

  • Hesitation is not resistance: why the hardest questions are worth listening to
  • Expert in the loop, not a generic human in the loop
  • Governing the consequence rather than the novelty of the tool
  • What must be true before an agency relies on an answer

For agency leadership, boards, policy staff, and conference general sessions

Topic 03

The data headache.

Most agencies already have data. That is not the same as having knowledge. The headache starts when definitions disagree, ownership is unclear, and nobody can say which report to trust. It does not go away by buying another tool.

  • Why the hardest failures live between systems and people, not inside either
  • People, process, policy, platform, and the purpose test that governs all four
  • Provenance before intelligence: why AI cannot rescue ungoverned data
  • Enterprise capability sized for real agency budgets and staffing

For data teams, CIOs and CDOs, state and regional agencies, and technical tracks

What to expect

No vendor deck.

I have built products and sold them, led delivery and answered for it, negotiated the partnerships that made the products possible, and sat on the agency side of the table watching it all arrive. Sessions come out of that. They do not come out of a slide library.

Grounded in the work

Examples come from statewide systems, district implementations, and standards work, not from hypotheticals.

Plain language

Written for the people who have to act on the information, including those who did not choose the technology.

Honest about limits

Where the evidence is thin or the guidance is changing, the session says so rather than smoothing it over.

Booking

Tell me about the audience.

The most useful first message describes who is in the room, what they are being asked to decide, and how much time there is. If it turns into a conversation rather than a booking, that is fine too.

Views expressed here are my own.