The Practical AI podcast has released a special episode featuring highlights from three talks at the Midwest AI Summit 2026. Heidi Porter argued that reliable AI-augmented workflows depend on choosing the right tools, running rigorous evaluations and putting guardrails in place. Kevin Solorio made the case that AI systems built with frontline workers, rather than simply handed to them, earn more trust and see faster adoption, with collaboration and continuous feedback central to that approach.
Chris Shinkle and Andrew Dunlap of SEP addressed how software teams should decide how much autonomy to give AI coding tools. Their framework ties the right level of autonomy to a team's goals, constraints and verification needs, and they shared lessons from teams using AI to build software more effectively. The show notes do not publish benchmark figures or measured outcomes, so the claims reflect practitioner experience rather than audited results.
For Australian businesses and professionals, the episode changes little immediately, though its principles are practical. Teams piloting AI tools should budget for evaluation and human review, not just licence fees, and involve the staff who will use a system before rolling it out. Where AI touches personal information, the Privacy Act 1988 still governs how that data is collected, used and disclosed, so verification steps matter. Worth trying: a small pilot with a clear success measure and a defined point of human sign-off.
Key Points
Reliable AI-augmented workflows depend on the right tools, rigorous evaluations and guardrails
Building AI with frontline workers, not just for them, drives trust and adoption
Software teams should set AI autonomy based on goals, constraints and verification needs
Lessons from teams using AI to build software were shared, though without published metrics