What should your business achieve before you call an AI rollout a success?
In this episode of The Catch Up Podcast, Phillip Blackmore speaks with Jonathan (Johnny) Rowley, co-founder of Mission AI, about the lessons that connect Microsoft Dynamics projects with AI adoption. Drawing on his work in Microsoft customer success and internal technology adoption, Johnny explains why listening to customers and defining measurable benefits should come before a product demonstration.
Johnny discusses the investment needed to help employees change how they work, why training must continue as products develop, and how agent usage can generate costs that need measuring against the benefit delivered. He also reflects on his RAF reserve service, career changes and the value of meeting people in person. For leaders planning Copilot adoption, the conversation offers a practical starting point: agree the outcome and prepare the people who will deliver it.
- (00:00) - Welcome to The Catch Up Podcast
- (04:37) - Listening Before Selling Technology
- (09:30) - Learning through Career Changes
- (14:44) - Why Projects Break Down
- (19:30) - Funding Change and User Adoption
- (24:14) - The Value of Meeting in Person
- (29:15) - RAF Service alongside Microsoft
- (34:49) - From Microsoft Digital to Mission AI
- (39:06) - Starting AI Adoption with Business Value
- (44:25) - AI Agent Costs and Usage Controls
- (49:24) - Helping People Solve Business Problems
- (53:27) - What to Do Before an AI Rollout
Jonathan Rowley: Jonathan Rowley is co-founder and Principal, AI Delivery at Mission AI, an independent AI consultancy supporting organisations with strategy, adoption planning and training. His current work includes AI delivery across defence, education and enterprise. A former Microsoft director, he describes working in Dynamics customer success before joining Microsoft Digital, where he supported internal adoption of Teams, Viva and Copilot in the UK and Ireland. His earlier career includes industrial automation at Siemens and roles across technology sales, consulting and management. Johnny also served in the Royal Auxiliary Air Force alongside his Microsoft career. That combination of enterprise delivery and military experience informs his focus on clear objectives, practical learning and the people responsible for making technology useful.
Episode Insights:- AI adoption should begin with a business problem and measurable benefit, using the same discipline that successful ERP and CRM projects require.
- A customer’s value often starts after go-live, so partner delivery milestones and business success should not be treated as interchangeable.
- Ongoing training, communication and resistance management need proper funding; a single training session cannot deliver lasting adoption.
- AI agent costs need assessing against the value of the work completed, especially when repeated tasks spread across a large workforce.
- Johnny argues that in-person workshops and regular face-to-face conversations help build trust and accountability during difficult projects.
Action Points:
- Define a measurable outcome: Write down the business problem before selecting an AI tool or building an agent. Agree what improvement would count as success and how you will measure it. Use those measures to review benefits after deployment, rather than closing the discussion at go-live.
- Fund ongoing adoption: Give change management and training their own budget and accountable people. Ask employees what concerns them and include communication and resistance management in the plan. Keep learning active as the tools change, rather than treating the first training session as completion.
- Check the cost of useful work: Choose a specific task and compare its usage cost with the benefit it delivers. Consider how that cost changes when many employees repeat the task. Agree suitable limits and review actual spending before extending access.
- Review data access before expansion: Bring the people responsible for security and governance into the adoption plan early. Review which information the tools can access and what controls the organisation needs. Give employees clear guidance before they use AI with business information.
- Make time to listen: Begin customer and partner discussions by asking about the problem and letting people explain it. Use in-person sessions where they help teams build trust or resolve difficult issues. Keep returning to the agreed outcome when conversations become dominated by features or delivery dates.
The Catch Up Podcast brings you candid conversations with industry leaders, consultants, and change-makers from the Microsoft Dynamics and tech ecosystem. Hosted by Phillip Blackmore, Sales Director at Catch Resource Management, each episode dives into the real stories behind business transformation, career pivots, and scaling success. Expect thoughtful interviews, practical insights, and honest reflections.
Brought to you by
Catch Resource Management, a leading UK recruitment specialist for Microsoft Dynamics and ERP talent, this podcast is your inside track to the people shaping the future of enterprise technology. Tune in for new episodes and stay ahead of the curve.
The Catch Up Podcast is produced by
Story Ninety-Four in Oxford, UK.
What is The Catch Up Podcast?
The Catch Up Podcast brings you candid conversations with industry leaders, consultants, and change-makers from the Microsoft Dynamics and tech ecosystem. Hosted by Phillip Blackmore, Sales Director at Catch Resource Management, each episode dives into the real stories behind business transformation, career pivots, and scaling success. Expect thoughtful interviews, practical insights, and honest reflections. Brought to you by Catch Resource Management, a leading UK recruitment specialist for Microsoft Dynamics and ERP talent, this podcast is your inside track to the people shaping the future of enterprise technology.