The Catch Up Podcast cover art

The Catch Up Podcast

The Catch Up Podcast

Written by: Catch Resource Management
Listen for free

About this listen

 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.Catch Resource Management Economics Management Management & Leadership
Episodes
  • Samit Roy's Journey From Electrical Engineer to D365 Solution Architect

    Samit Roy's Journey From Electrical Engineer to D365 Solution Architect
    Jan 29 2026
    How do you build the experience and skills needed to become a trusted solution architect in the world of enterprise ERP? In this episode of The Catch Up Podcast, host Phil Blackmore speaks with Samit Roy, an experienced D365 Finance and Operations solution architect, about his two-decade journey from electrical engineering through Dynamics Great Plains, AX 2009, AX 2012, and into the modern D365 ecosystem. They explore the hard-won lessons from working across partner and end-customer environments, the importance of getting out of your comfort zone as a freelance consultant, and why solution architects must bring far more than product knowledge to the table.With Microsoft Dynamics 365 recently named a Leader in three Gartner Magic Quadrant reports and research showing that effective project risk management can boost on-time completion rates by up to 90%, Samit explains why early engagement of a solution architect is critical, how to avoid common ERP pitfalls like poor data migration and unchecked customisation, and what separates good architects from great ones: curiosity, empathy, and the ability to ask the right questions at the right time.From navigating the transition between product versions to putting yourself in the customer's shoes, this conversation offers a practical roadmap for aspiring solution architects and a reminder for organisations embarking on ERP transformation that investing in architectural expertise from day one pays dividends throughout the project lifecycle.(00:00) - Welcome to The Catch Up Podcast (02:03) - Early Career: From Electrical Engineer to ERP (03:36) - The Origins of Dynamics and Great Plains (05:24) - Moving to the UK and Dynamics AX (06:23) - Working at ePartners and Small Project Teams (10:00) - The Transition from AX 4 to AX 2009 (12:35) - Moving from Partner to Freelance Consulting (16:15) - The Challenge of Working Outside Your Comfort Zone (22:02) - Transitioning to Solution Architect Roles (27:42) - What Solution Architects Bring Beyond Product Knowledge (34:34) - Common ERP Pitfalls and How to Avoid Them (39:14) - What Makes a Good Solution Architect (44:45) - Advice for Organisations Embarking on D365 ImplementationSamit Roy: Samit Roy is an experienced D365 Finance and Operations solution architect with over 20 years' expertise in Microsoft Dynamics ERP implementations. His career began with Dynamics Great Plains in India before relocating to the UK in 2005 to work with Dynamics AX, progressing through AX 4, AX 2009, AX 2012, and into the modern D365 ecosystem. Samit has worked across both partner and end-customer environments, delivering complex, large-scale ERP programmes for multinational organisations in sectors including manufacturing, distribution, and professional services. His architectural approach combines deep functional and technical knowledge with a focus on business outcomes, change management, and long-term system sustainability. Samit transitioned to freelance consulting in 2011, working on implementations ranging from six-month projects to multi-year, multi-geography transformations, and is known for his pragmatic, empathetic style and ability to translate complex technical concepts into decision-ready language for boards and senior stakeholders. Episode Insights:Becoming a solution architect requires at least a decade of hands-on experience across multiple projects, environments, and product versions—there are no shortcuts to building the breadth of knowledge and pattern recognition needed for the role.The best solution architects are not necessarily experts in every feature of the product but have deep core knowledge, broad business exposure, and the intellectual curiosity to ask incisive questions and understand what the client truly needs.Early engagement of a solution architect—ideally from the discovery phase—dramatically improves project outcomes by surfacing risks, guiding phased vs big-bang decisions, and ensuring design choices support long-term resilience, not just go-live.Common ERP pitfalls such as poor data migration, unchecked customisation, and performance issues can often be avoided with experienced architectural oversight that challenges assumptions and applies lessons learned from previous projects.Transitioning from a partner environment to freelance consulting forces consultants out of their comfort zone, accelerating skill development and building the self-reliance and troubleshooting instincts that define strong solution architects.Action Points:Engage a solution architect from day one: Involve an experienced solution architect during the discovery and design phases, not as an afterthought when problems arise. Early architectural input shapes critical decisions around scope, phasing, data migration, and customisation, setting the foundation for long-term project success and helping avoid costly course corrections later.Build broad experience before specialising: If you aspire to become a solution architect, ...
    Show More Show Less
    49 mins
  • Out of the Box Only: ERP Lessons from Programme Director Mark Edwards

    Out of the Box Only: ERP Lessons from Programme Director Mark Edwards
    Dec 18 2025
    Why do so many ERP and Dynamics 365 programmes go wrong, even when the technology is sound? In this episode of The Catch Up Podcast, host Phillip Blackmore sits down with experienced D365 Programme Director Mark Edwards to unpack what really makes or breaks complex transformation. Mark traces his journey from manufacturing engineering and production management into ERP, consulting and programme leadership, showing how hands‑on operations experience shaped his approach to delivery and change.Drawing on decades of work across manufacturing, supply chain, chemicals, retail, rental, charities and more, Mark explains why vague contracts, missold projects and over‑reliance on partners leave clients exposed. He argues that too many organisations only bring in a programme manager after supplier selection, when much of the risk is already locked in. His perspective lands against a backdrop where industry research suggests that a majority of ERP programmes still fail to meet their original objectives, largely due to organisational rather than technical issues.From defining a clear vision and target operating model to insisting on “out of the box” first and investing seriously in change management, this conversation offers a practical playbook for leaders planning their next transformation.Click Here to Watch the Video Episode. (00:00) - Welcome to The Catch Up Podcast (02:17) - Early Career in Manufacturing Engineering at GEC (05:55) - First ERP Project and Discovering MFG Pro (07:20) - Seeing ERP From User, Vendor and Consultant Perspectives (11:18) - Defining Vision and Objectives Before Choosing a System (19:08) - Why Clients Must Own the Programme, Not the Partner (24:48) - Treating ERP as Business Change, Not an IT Project (28:02) - Out of the Box Only and the Risks of Customisation (31:16) - Change Management as a Shared Leadership Responsibility (35:01) - Data Quality, Cutover and Continuous Improvement (37:12) - Tough Projects, Bad News Early and Programme Integrity (44:28) - Key Advice for Leaders Starting a D365 or ERP JourneyMark Edwards: Mark Edwards is a seasoned D365 Programme Director with a career that spans manufacturing engineering, production management, ERP consulting and large‑scale programme leadership. Starting in manufacturing engineering with GEC, he moved through roles in production management and supply chain before leading his first ERP workstream on a mid‑market system. He went on to join ERP vendor QAD as a manufacturing consultant, later moving into pre‑sales, marketing and running a consulting practice back to profitability through value‑based selling. Since then, Mark has delivered and overseen ERP and Dynamics programmes from multiple perspectives: as a vendor, as a management consultant, and as a client‑side programme leader. His experience covers manufacturing, supply chain, retail, rental, third‑sector charities and chemicals, with a consistent focus on clear vision, honest communication, realistic contracts and rigorous change management.Episode Insights:Successful ERP and D365 programmes start with a clear, business‑led vision and target operating model, not with software features or vendor demos.Vague contracts and scopes of work create downstream conflict; precise deliverables and roles protect both client and partner.Clients must own the programme: partners bring solution expertise, but only the client can supply true process ownership and decision‑making.“Out of the box” should be the default; unnecessary customisation quickly multiplies risk, cost and long‑term complexity.Change management is a shared leadership responsibility, not a single person’s job, and must start well before go‑live.Action Points:Define a business‑led vision before talking to vendors: Bring your senior team together to answer why you are changing systems and what success looks like in business terms, not technology terms. Capture the key objectives, from risk reduction to productivity and customer service, and use them as the non‑negotiable brief for any vendor conversations.Tighten contracts and scopes of work: Review existing or draft contracts to check how clearly outcomes, responsibilities and deliverables are defined. Challenge vague language around scope, roles and assumptions, and insist on documentation that spells out who does what, by when, and to what standard.Build a client‑side programme spine: Identify and appoint internal process owners and workstream leads across planning, procurement, operations, finance and other core areas. Make them accountable for defining processes, signing off designs and owning change, rather than leaving all decisions to the implementation partner.Apply the “out of the box” test to customisation: For every requested change to standard D365 or ERP behaviour, ask whether the same business outcome could be achieved using the default process. Treat customisation as an exception that requires a clear business case, ...
    Show More Show Less
    51 mins
  • Lessons from the Front Line of D365 with Chris Lalley

    Lessons from the Front Line of D365 with Chris Lalley
    Nov 27 2025
    What does it actually take to land a complex ERP or Dynamics 365 transformation without becoming another horror story? In this episode of The Catch Up, host Phillip Blackmore sits down with seasoned programme leader Chris Lalley to unpack the realities of delivering large‑scale finance and D365 projects in the real world. They explore how careers evolve from operational finance into programme leadership, why variety and curiosity matter, and how personal quirks like “dishwasher‑level” OCD can be a genuine asset in delivery.Throughout the conversation, Chris returns to a consistent theme: technology‑enabled transformation is fundamentally about people, not platforms. That message is timely. Recent research shows that while ERP capabilities have advanced, 55–75% of projects still fail to hit their original objectives, with average cost overruns near 189%, largely due to organisational, not technical, issues. Chris explains how he approaches new engagements, from establishing vision and sponsorship to assessing team capability and rescuing “programmes in jeopardy”. For leaders about to embark on a D365 or ERP journey, this episode offers grounded, experience‑led guidance on what success really demands.Click Here to Watch the Video Episode. (00:00) - Welcome to The Catch Up Podcast (01:45) - From Big Five Accounting to Early Transformation Projects (03:40) - Finding the Bug for Large-Scale Change Programmes (05:00) - OCD, Attention Span and the Appeal of Programme Work (07:10) - The Dishwasher Story and Structured Thinking (09:13) - First Steps into Microsoft ERP and Dynamics 365 (13:15) - Greenfield versus Mature Organisations in ERP Delivery (17:03) - Starting a New Programme: People, Vision and Strategy (20:06) - Recovering Programmes in Jeopardy and Rebuilding Confidence (26:43) - Learning from Mistakes and Getting Capability Right (33:32) - Fixed Price vs Time and Materials in ERP Contracts (39:50) - Defining Success and the Role of Executive SponsorsChris Lalley: Chris Lalley is an experienced ERP and finance transformation programme leader with a background that spans Big Five accounting, industry finance roles and large‑scale technology‑enabled change. Starting his career in operational finance at firms such as Arthur Andersen and Ernst & Young, he led major internal projects including a global PeopleSoft implementation and the establishment of an offshore shared service centre in Bangalore. That exposure to complex programmes sparked his move into full‑time project and programme leadership, where he has since delivered and recovered high‑stakes ERP and Dynamics 365 initiatives across multiple sectors. Drawing on years of hands‑on delivery, Chris is known for his focus on people, structure and sponsorship as the real levers of success in transformation.Episode Insights:Successful Dynamics 365 and ERP programmes are driven more by people, clarity of vision and sponsorship than by the underlying technology stack.The first weeks on a programme should be spent meeting stakeholders, understanding their motivations and aligning ERP outcomes to business strategy, not rushing into Gantt charts.Change management is usually under‑invested, yet it affects not only employees but also customers when portals and digital channels are redesigned.Capability at the right time is non‑negotiable: under‑resourcing business analysts, architects or change leads early on slows delivery and magnifies risk later.Programme directors must be willing to say when “conditions for success don’t exist” and walk away, protecting both their own reputation and the client’s investment.Action Points:Define success in business terms before you start: Agree a clear vision, outcomes and measures of success with the C‑suite before mobilising your D365 or ERP programme. This includes how the transformation supports overall strategy, what benefits you expect and how you will track them over time. Without this foundation, scope, design and prioritisation quickly drift.Invest properly in change management, not just technology: Treat change, communications and training as a core workstream with its own budget, leadership and methodology. Map who is impacted inside and outside the organisation, from finance teams to customers on portals, and design their journey through the change. Under‑investing here is one of the fastest routes to user resistance and poor adoption.Build the right team and lock in key people: Identify the critical roles across business, partner and contractor resources, then secure the best people you can for a realistic duration. Use contracts and governance to minimise churn in key posts like solution architect, programme manager and lead BAs. Consistent faces and continuity of knowledge are vital for multi‑year ERP journeys.Be honest about risk and willing to make compromises: Accept that large ERP programmes are hard, will involve setbacks and will require compromises on ...
    Show More Show Less
    45 mins
No reviews yet