Speaking
Practical talks on AI adoption, methodology, and the gap between what organizations think they need and what actually works.
I speak on AI, process, and what it takes to build and lead well in a moment when the tools are changing faster than most organizations can adapt.
My approach is direct and grounded in things I've actually built. I don't do hype, and I don't do vendor-neutral summaries of what AI can theoretically do. I talk about what works, what doesn't, and why the gap between those two things is almost always a people and process problem rather than a technology problem.
The audiences I work best with are past the "what is AI" phase. They're asking the harder questions: How do we actually use this? What do our people need to be able to do? What do we stop doing, and what do we do differently?
Topics
An exploration of Jevons Paradox applied to software development, what commoditized code actually means for teams and organizations, and where the new leverage lives. For technical leaders, product leaders, and anyone trying to figure out how to compete in an environment where execution is no longer the differentiator.
The models have to align to us. That part gets talked about. The other direction — humans developing the literacy to work effectively with these tools — gets talked about much less. This talk is about what AI literacy actually looks like in practice, what it takes to build it inside an organization, and what happens to organizations that don't.
A talk on process philosophy: why process matters, why it fails, and how to build organizations that can hold both. Grounded in real examples from across industries. Works for operations leaders, founders, and anyone who has watched a good team grind to a halt under the weight of its own procedures.
A practical look at how to actually run AI-augmented software development at a level that produces output worth keeping. What the workflow looks like, where the leverage is, and what the human still has to bring. For technical teams, product organizations, and engineering leaders.
What to Expect
Talks run from 30 minutes to full workshop format depending on the engagement. I do Q&A as part of every session because the best part of a talk is usually what happens after the slides stop.
I don't use a canned deck. The material is consistent but the delivery is built for the audience. A talk for a room of CTOs sounds different than a talk for a chamber of commerce, and it should.
Recent Engagements
Iterative AI collaboration in practice: why one-shot prompting is leaving value on the table, and what a real human-AI working relationship looks like.
Tell me about your event, your audience, and what you're hoping people walk away with. If it's a good fit, we'll figure out the rest.
contact@matthewbradford.com