The Catch Up Podcast Titelbild

The Catch Up Podcast

The Catch Up Podcast

Von: Catch Resource Management
Jetzt kostenlos hören, ohne Abo

Über diesen Titel

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 Management & Leadership Ökonomie
  • From Chartered Accountant to Enterprise Architect: Rohit Bansal on Building a Dynamics Career
    Mar 26 2026
    What does it take to deliver Dynamics 365 Finance and Operations at true enterprise scale, without losing users, control, or the upgrade path?In this episode of The Catch Up Podcast, host Phillip Blackmore speaks with Rohit Bansal about a non-linear career journey from ACCA-qualified finance professional to enterprise architect working on some of the largest global programmes in the Dynamics ecosystem.Rohit shares hard-won lessons from an early AX 2009 implementation that went badly, and why negative project experiences can become a practical playbook for what not to do next time. They explore the reality of moving from end user to partner, the cultural differences between client and consultancy priorities, and why the strongest programmes keep key responsibilities in-house, particularly process definition, testing, and training.They also dig into how the product has evolved from AX into D365, why heavy customisation now creates recurring pain through frequent updates, and how the ISV ecosystem helps organisations stay closer to out-of-the-box. Finally, Rohit explains how his current programme measures success after go-live, using adoption dashboards and bug trends to spot where rollout teams need to adjust.(00:00) - Welcome to The Catch Up Podcast (02:16) - From Finance Controller to AX 2009 Project Lead (04:33) - The Bad Partner Lesson and Moving Into Consulting (07:07) - Why Methodology Matters and How Partners Differ (08:29) - End User Versus Partner: The Culture Shock (10:53) - Why Consulting Accelerates Learning Across Clients (12:25) - Users Make Projects Succeed or Fail (14:23) - Why Contracting Made Sense for Enterprise Programmes (17:12) - How D365 Became an Enterprise Rollout Platform (21:35) - What Clients Misunderstand About Handing Over Delivery (24:07) - ISVs, Customisation and the Forced Update Reality (34:20) - Measuring Success: Adoption Metrics and Bug Trajectories (36:25) - AI Agents, Upskilling and the Future SA Role (38:44) - What Makes a Great Solution Architect (41:19) - Pre-Project Strategies: Process, Data, Testing and TrainingRohit Bansal: Rohit Bansal is an enterprise architect in the Microsoft Dynamics ecosystem with a background in finance and accountancy. In this episode, Rohit describes moving from an ACCA-qualified finance career into Microsoft Dynamics after serving as an internal project lead on an AX 2009 implementation, then progressing through partner work and contracting into large, multi-country D365 Finance and Operations programmes. Episode Insights:Users determine whether an ERP programme succeeds. Project plans matter, but adoption on the floor makes or breaks the outcome.Large programmes work best with a blended model. Clients should retain process definition, training, and testing to avoid conflicts of interest.The shift from AX to D365 changed the fit. D365 F&O suits large enterprise rollouts but often prices out smaller organisations.Heavy customisation is harder to justify now. Frequent service updates increase regression testing and code merge effort.A global template with controlled localisation supports a sustainable support model and upgrade path.Action Points:Retain ownership of process definition: Define your global processes before the programme starts, ideally before partner selection. Use these processes to drive solution design, not the other way round. Expect local teams to describe different ways of working, and use the global model to converge.Separate assurance from delivery: Keep testing and training in-house where possible, even when implementation work sits with a partner. Avoid asking a partner to test their own build without independent scrutiny. Use a blended approach that leverages partner skill while retaining unbiased validation.Control customisation to protect the upgrade path: Assume you will take frequent platform updates and plan for continuous regression testing. Prefer proven ISVs over bespoke build when an established solution exists. Reserve custom code for true competitive advantage, not convenience.Design an adoption dashboard before go-live: Decide what adoption looks like per function, such as AP, AR, supply chain, and production. Track month-on-month operational volume and compare sites to spot where training or process clarity is failing. Share progress visually with users to reinforce value and momentum.Treat rollout architecture as global-first: Build a global template with limited, controlled localisation. Challenge any request that makes the core model work for only a subset of the enterprise. Protect live sites by assessing how local changes affect current and future deployments.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. ...
    Mehr anzeigen Weniger anzeigen
    46 Min.
  • Building High-Performing Delivery Teams with Musonda Veronica
    Mar 5 2026
    How do you build a career in programme management when your path is anything but linear, and what separates a successful transformation from an expensive recovery job?In this episode of The Catch Up Podcast, host Phillip Blackmore speaks with Musonda Veronica about moving from studying law into leading complex Microsoft Dynamics 365 programmes. They explore why communication is the core of delivery leadership, how to adapt your style to different stakeholders, and why integrity is what builds the trust programmes depend on.Musonda also breaks down a practical distinction many organisations miss: Dynamics 365 CE delivery often demands an iterative, agile approach because of heavier customisation, while finance and operations programmes tend to suit more structured delivery patterns.The conversation lands on the unglamorous foundations that keep budgets intact: clear decision ownership, dedicated SMEs, and change management that treats resistance as human rather than a problem to crush. This aligns with common ERP failure patterns such as under-committing internal resources, highlighted in Guidehouse analysis.Click Here to Watch the Video Episode. (00:00) - Welcome to The Catch Up Podcast (01:17) - From Law to Programme Management (03:11) - Early Roles and Finding Direction (06:36) - First Exposure to Dynamics 365 and CRM (09:19) - Why CE and FinOps Are Delivered Differently (17:08) - What Makes a Strong Programme Manager (23:34) - Gen Z in the Workforce (25:38) - Why Programmes Run Over Time and Budget (34:40) - The One Thing to Fix Before You Start (42:07) - Mentoring, Speaking, and Purpose Beyond DeliveryMusonda Veronica Malama: Musonda Veronica Malama is a UK-based transformation programme manager and programme recovery leader specialising in Microsoft Dynamics 365 delivery. She is also a career coach and professional speaker, covering topics including leading successful teams, delivering high-stakes programmes, and inclusion in the workplace. Alongside hands-on delivery work, she mentors professionals moving into project and programme roles and speaks at industry events. Episode Insights:Programme management is mostly communication: translate between technical teams and business stakeholders without needing to be the technical expert.Dynamics 365 CE programmes often require more iterative delivery because customisation tends to be higher than in finance and operations work.Readiness is not a slogan: programmes slip when decision ownership, resourcing, and governance are unclear at the start.The pace of decision-making predicts delivery outcomes: stalled decisions create delays that burn budget.Trust is an execution tool: integrity and early communication reduce churn, resistance, and rework.Action Points:Define decision ownership: Name a single accountable sponsor for the programme, backed by a small decision forum. Set a cadence where priority decisions get made quickly. Escalate unresolved items to that forum immediately, not after timelines slip.Backfill your SMEs: Ringfence the people who know the real processes and give them time to contribute. Remove BAU load or provide cover so workshops and testing do not become optional. Treat SME availability as a critical path item, not a nice-to-have.Choose a delivery model that matches the product area: Use a more iterative approach where customisation is high, particularly in CE work. Keep stakeholders close to demos and feedback loops so you reduce rework. Avoid forcing one template delivery model across all workstreams.Build trust through visible integrity: Commit to a small set of deliverables and hit them consistently. Communicate bad news early, with reasons and next steps. Make reliability part of the programme culture.Treat resistance as data: Assume uncertainty will surface as pushback. Involve impacted people early and show tangible benefits before go-live. Run simple, frequent communications that reduce speculation and corridor narratives.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.
    Mehr anzeigen Weniger anzeigen
    46 Min.
  • 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, ...
    Mehr anzeigen Weniger anzeigen
    49 Min.
Noch keine Rezensionen vorhanden