Hybrid Methodology Adoption Challenges

𝐄𝐦𝐛𝐫𝐚𝐜𝐢𝐧𝐠 𝐇𝐲𝐛𝐫𝐢𝐝 𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: 𝐈𝐧𝐬𝐢𝐠𝐡𝐭𝐬 𝐟𝐫𝐨𝐦 𝐭𝐡𝐞 𝐅𝐢𝐫𝐬𝐭 𝐆𝐥𝐨𝐛𝐚𝐥 𝐒𝐮𝐫𝐯𝐞𝐲 In today's dynamic and complex business environment, hybrid project management has emerged as a pivotal approach for achieving success. Antonio Nieto-Rodriguez comprehensive survey, involving 1,168 professionals across various industries and regions, reveals critical insights into the adoption, benefits, and challenges of hybrid methodologies. 𝐊𝐞𝐲 𝐇𝐢𝐠𝐡𝐥𝐢𝐠𝐡𝐭𝐬 𝐟𝐫𝐨𝐦 𝐭𝐡𝐞 𝐒𝐮𝐫𝐯𝐞𝐲 1̳.̳ ̳W̳i̳d̳e̳s̳p̳r̳e̳a̳d̳ ̳A̳d̳o̳p̳t̳i̳o̳n̳ : 89% of respondents reported using a mix of project management methodologies, underscoring a 𝐬𝐡𝐢𝐟𝐭 𝐭𝐨𝐰𝐚𝐫𝐝𝐬 𝐟𝐥𝐞𝐱𝐢𝐛𝐥𝐞 𝐚𝐧𝐝 𝐚𝐝𝐚𝐩𝐭𝐢𝐯𝐞 𝐩𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬 over single-method approaches. 2̳.̳ ̳C̳r̳o̳s̳s̳-̳I̳n̳d̳u̳s̳t̳r̳y̳ ̳U̳t̳i̳l̳i̳z̳a̳t̳i̳o̳n̳: The survey shows hybrid methods are adopted across diverse sectors, with notable participation from Information Technology (20%), Consulting (25%), and Healthcare and Pharmaceuticals (20%). 3̳.̳ ̳I̳m̳p̳r̳o̳v̳e̳d̳ ̳S̳u̳c̳c̳e̳s̳s̳ ̳R̳a̳t̳e̳s̳: 48% of the respondents noted significant improvements in project success rates post-adoption of hybrid methods. 4̳.̳ ̳N̳e̳e̳d̳ ̳f̳o̳r̳ ̳C̳o̳m̳p̳r̳e̳h̳e̳n̳s̳i̳v̳e̳ ̳T̳r̳a̳i̳n̳i̳n̳g̳: While 43% of respondents indicated that some team members received formal training, there is a clear need for more comprehensive training programs to ensure widespread proficiency. 5̳.̳ ̳C̳h̳a̳l̳l̳e̳n̳g̳e̳s̳ ̳i̳n̳ ̳I̳m̳p̳l̳e̳m̳e̳n̳t̳a̳t̳i̳o̳n̳: Common issues include resistance to change (58%) and difficulties in synchronizing different methodologies (43%). 6̳.̳ ̳A̳I̳ ̳I̳n̳t̳e̳g̳r̳a̳t̳i̳o̳n̳: 37% believe that AI will accelerate the adoption of hybrid methods, while 36% expect AI to assist in optimizing the mix of methodologies. 7̳.̳ ̳E̳n̳h̳a̳n̳c̳e̳d̳ ̳F̳l̳e̳x̳i̳b̳i̳l̳i̳t̳y̳ ̳a̳n̳d̳ ̳R̳e̳s̳o̳u̳r̳c̳e̳ ̳M̳a̳n̳a̳g̳e̳m̳e̳n̳t̳: The primary reasons for adopting hybrid approaches were greater flexibility (84%) and improved resource management (88%). 8̳.̳ ̳C̳o̳m̳m̳o̳n̳ ̳M̳e̳t̳h̳o̳d̳o̳l̳o̳g̳i̳e̳s̳: Agile-Scrum/Kanban (84%) and Waterfall (88%) are the most frequently combined methodologies, demonstrating a preference for integrating iterative and structured approaches. 9̳.̳ ̳P̳r̳o̳d̳u̳c̳t̳i̳v̳i̳t̳y̳ ̳G̳a̳i̳n̳s̳:̳ A majority observed increases in team productivity, with 33% reporting moderate improvements and 41% noting significant gains. 1̳0̳.̳ ̳I̳m̳p̳r̳o̳v̳e̳d̳ ̳O̳r̳g̳a̳n̳i̳z̳a̳t̳i̳o̳n̳a̳l̳ ̳A̳g̳i̳l̳i̳t̳y̳: Adopting hybrid methods has moderately (42%) to significantly (25%) improved organizational agility, enhancing the ability to respond to changes and challenges. As the landscape of project management continues to evolve, embracing hybrid approaches and leveraging emerging technologies like AI will be key to staying ahead. #ProjectManagement #HybridApproach #AI #Agile #Waterfall #Flexibility #ResourceManagement #OrganizationalAgility #SurveyInsights

My recent post on hybrid project methodology triggered good discussion about the roles IT and OT should play. Here’s what we’ve seen work—and what doesn’t. MES projects create more friction than any other industrial technology deployment because it’s the only system that straddles both worlds—IT and OT. IT’s World: Infrastructure, security, scalability, enterprise integrations (ERP, PLM, quality systems), data governance, vendor management, and budget accountability. A poorly architected MES creates security vulnerabilities, integration nightmares, and compounding technical debt. OT’s World: Shop floor operations, equipment integration, real-time production decisions, operator usability, and manufacturing process expertise. An MES that doesn’t work for operations becomes expensive shelfware, no matter how well it integrates with ERP. The Problem: When IT leads alone → You get a system that checks enterprise boxes but doesn’t work on the floor When OT leads alone → You get a system that works locally but creates enterprise integration and security problems Why MES is Different: Every other industrial technology sits clearly on one side: SCADA/HMI and PLCs are OT domain. ERP and identity management are IT domain. But MES collects real-time data from PLCs while posting to ERP. It manages shop floor workflows while enforcing enterprise compliance. It makes split-second production decisions while maintaining audit trails for regulators. It needs both perspectives from day one. What we’ve seen work: - IT defining architecture, security, and integration standards - OT defining workflows, usability, and operational requirements - Both collaborating on vendor selection and implementation - Clear accountability: IT owns infrastructure and enterprise integration, OT owns operational outcomes The worst deployments? One side decides, the other lives with it. The Challenge: In many organizations, IT reports to Finance, driving consolidation, standardization, and cost reduction. But manufacturing is about managing variability, responding to real-time conditions, and continuous improvement. MES sits at the intersection. It fails when we pretend it belongs to just one world. Less than 10% of manufacturers globally have achieved true MES maturity. The gap isn’t technology capability—it’s that IT purchased an off-the-shelf “configurable” MES without understanding operational requirements, or OT built something that can’t scale or integrate. When IT alone selects MES, they often buy a solution that reduces operational efficiency rather than enhancing it. MES success requires both IT rigor and OT expertise working together from requirements through deployment.

Today, enterprises don’t know what to believe about AI adoption. - Should they trust AI agents to make decisions autonomously? - Or should they stick to deterministic workflows to avoid risk? Most are stuck between hype and hesitation, experimenting with agentic tools while still enforcing deterministic controls, often without a clear boundary or framework. It’s because there is still no clear operating model. And that’s leading to org-wide misalignment: - Engineering wants to ship fast using LLMs. - Compliance wants deterministic controls. - Sales wants automation. - Legal wants oversight. This tension pulls the org in opposite directions, a classic sign of an identity crisis in AI adoption. The real path forward is hybrid: - Agentic AI for dynamic, context-driven work: sales outreach, support follow-ups, process optimization. - Deterministic systems for mission-critical, compliance-bound tasks: financial transactions, regulatory filings, clinical trials. And the art is knowing where to draw the line. Confuse the two, and you will either end up on the wrong side of compliance or stall growth and innovation with over-control.

What if the "best" methodology... is hiding your project's biggest flaw? Hybrid models blend Scrum's agility with Waterfall's structure. They work. Here's proof. → 𝐖𝐚𝐲𝐬 𝐭𝐨 𝐂𝐨𝐦𝐛𝐢𝐧𝐞 𝐓𝐡𝐞𝐦 • Water-Scrum-Fall: Waterfall for planning/deployment, Scrum for development. • Scrum in Waterfall: Agile teams tackle specific components iteratively. • Gate-Based Scrum: Stage gates control phases, Scrum executes inside. • Parallel Teams: Some use Scrum, others Waterfall simultaneously. → 𝐊𝐞𝐲 𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬 • Predictability: Fixed schedules and budgets from upfront planning. • Flexibility: Scrum handles requirement changes fast. • Scalability: Ideal for large, regulated projects. • Engagement: Continuous stakeholder feedback. • Risk Control: Early iterations spot issues quickly. → 𝐂𝐨𝐦𝐦𝐨𝐧 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞𝐬 • Culture Clash: Agile vs. Waterfall mindsets collide. • Handoff Delays: Transitions create bottlenecks. • Slower Feedback: Loops lag behind pure Agile. • Added Complexity: Requires extra management. • Staffing Issues: Roles blur across methods. → 𝐁𝐞𝐬𝐭 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬 𝐟𝐨𝐫 𝐒𝐮𝐜𝐜𝐞𝐬𝐬 • Define clear roles and handoffs. • Maintain full transparency. • Automate docs and communication. • Educate stakeholders on the approach. • Run retrospectives for constant refinement. Hybrids deliver when executed right. Predictable yet adaptable. Follow Carlos Shoji for more insights

Hybrid Change Models? Clarity or Chaos? Some leaders mix agile and traditional methods, hoping for the best. Instead, they get confusion, misalignment, and stalled progress. Here’s how to fix the hybrid trap: 1️⃣ 𝗗𝗼𝗻’𝘁 𝗙𝗼𝗿𝗰𝗲 𝗮 𝗙𝗶𝘁 Use agile for innovation. Use traditional for compliance. One size does not fit all. 2️⃣ 𝗔𝗽𝗽𝗼𝗶𝗻𝘁 𝗮 “𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗼𝗿” Assign someone to bridge agile and traditional teams. They align priorities and clear up confusion. 3️⃣ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗢𝘂𝘁𝗰𝗼𝗺𝗲𝘀, 𝗡𝗼𝘁 𝗣𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 Stop debating how to work. Start defining what success looks like. 4️⃣ 𝗧𝗲𝘀𝘁 𝗦𝗺𝗮𝗹𝗹 𝗙𝗶𝗿𝘀𝘁 Try hybrid models on low-risk projects. Adjust before scaling up. 5️⃣ 𝗕𝗿𝗶𝗱𝗴𝗲 𝘁𝗵𝗲 𝗖𝘂𝗹𝘁𝘂𝗿𝗲 𝗚𝗮𝗽 Traditionalists value structure. Agilists thrive on flexibility. Align mindsets through open dialogue. 6️⃣ 𝗠𝗮𝗸𝗲 𝗪𝗼𝗿𝗸 𝗩𝗶𝘀𝗶𝗯𝗹𝗲 Use agile sprints and traditional milestones. Keep everyone aligned. 𝗛𝘆𝗯𝗿𝗶𝗱 𝗺𝗼𝗱𝗲𝗹𝘀 𝗱𝗼𝗻’𝘁 𝗵𝗮𝘃𝗲 𝘁𝗼 𝗯𝗲 𝗺𝗲𝘀𝘀𝘆. 𝗪𝗶𝘁𝗵 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵, 𝘁𝗵𝗲𝘆 𝗰𝗮𝗻 𝗱𝗿𝗶𝘃𝗲 𝗿𝗲𝗮𝗹 𝗰𝗵𝗮𝗻𝗴𝗲. What’s your biggest hybrid challenge? Let’s discuss below! 👇 ----- Change happens. Fractional leaders help. And coffee. All the time. 👋 I’m Lars – I deliver transformation that sticks. 🔔 Follow me for more on fractional leadership and change management. ✉️ DM me ‘READY’ for more insights