Preventing ERP Implementation Misunderstandings

I’ve killed 50+ ERP rollouts before kickoff. Always for the same 6 reasons. And your vendor will never tell you these. If you're about to start an ERP project, pause. Run this 6-question checklist first. (1) Is your CFO actively leading this project or is IT running the show? If Finance isn't in charge, you're building the wrong thing for the right price. (2) When was the last time your Chart of Accounts was redesigned? If it’s older than your finance manager, you're about to migrate legacy chaos. (3) Are you asking for a “like-for-like” system or rethinking broken workflows? If the goal is to copy-paste the past, why even switch? (4) Is Procurement part of your ERP planning team? No? Who’s mapping landed cost, freight margins, supplier controls? (5) Have you audited your master data before selecting the ERP? Or are you planning a $1M migration with duplicate SKUs and ghost vendors? (6) Did the vendor say, “You can customize that later”? That means they don’t understand your business. At all. If you answered “No” or “Not sure” to even 2 of these, stop the rollout. You’re not ready.

Article 2 The Preparation Phase: The Most Underrated Success Factor in ERP Programs In ERP projects, the preparation phase is often misunderstood. Some organizations think of it as: • A kickoff meeting • A project charter • A high-level timeline • A contractual formality before “real work” starts This misunderstanding alone explains why so many ERP programs struggle later. ⸻ Preparation ≠ Project Kickoff The preparation phase is not about starting fast. It is about answering the hardest questions before execution begins: • Why are we doing this transformation? • Who truly owns the ERP program? • Are the right people available full time? • Do we have decision authority and escalation clarity? • Are business users involved early or surprised later? In my research, preparation emerged not as an administrative phase, but as a strategic alignment engine. ⸻ What the Research Confirms The applied study evaluated several preparation-phase activities, including: • Conducting structured business workshops • Ensuring full-time dedication of project team members • Selecting an experienced ERP project manager (Digital Transformation leader) • Defining communication and escalation mechanisms • Early involvement of key users • Communicating the transformation vision across the organization Each of these activities showed a significant positive relationship with ERP project success. The conclusion was unambiguous: Preparation is not a single activity it is a system of leadership decisions. ⸻ Why Organizations Skip Proper Preparation From experience, preparation is often rushed because: • Leadership wants to “see progress” • Sponsors fear slowing momentum • Budgets are focused on implementation, not readiness • Preparation outcomes are less visible than configuration deliverables Ironically, the phase that looks least productive on paper is the one that prevents the most waste later. ⸻ Preparation Creates Predictability Strong preparation delivers: • Clear scope boundaries • Faster decision-making during execution • Lower resistance from business users • Fewer surprises after go-live • Higher executive confidence Weak preparation creates: • Firefighting • Escalations • Blame games • “Phase 2” promises that never materialize ⸻ Executive Perspective ERP programs don’t need more speed at the beginning. They need more clarity, ownership, and discipline. In the next article, I will zoom into the first proven success driver from the research: Why structured ERP workshops are not meetings but success accelerators. #ERP #DigitalTransformation #ERPImplementation #ERPLeadership #ThoughtLeadership #ERPStrategy #TransformationLeadership #PreparationPhase #ERPReadiness #ProgramGovernance #ERPBestPractices #TransformationStrategy

Many SAP projects go off track because of poor understanding between stakeholders. Here are the most common misunderstandings and how to prevent them 🤔👇 🧠 Assuming the Client Is Ready for SAP Many clients aren't strategically or operationally ready. Consultants should assess readiness and help close gaps before delivery, including data quality, process maturity, executive buy-in, and change readiness. 🎯 Misaligned Expectations on Scope and Deliverables Clients may expect too much too soon. Consultants may downplay complexity. Transparent scoping and expectation-setting should be a formal, early project activity. 🔍 Assuming Technical Solutions Alone Drive Success Technical excellence without process alignment and user engagement will fall flat. SAP must support real-world business outcomes. 📢 Underestimating Change Management You can’t implement transformation without managing the human response to it. Change enablement should run parallel to configuration, as neglect often results in resistance and poor user adoption. 📚 Overlooking Continuous Learning and Adaptation SAP systems evolve, and so must users and internal teams. Ongoing training and self-led learning are essential. A one-time training session is never enough in a dynamic SAP environment. 🛠️ Over-Customization Trying to mimic every legacy process adds risk and cost. Start with standard, and customize only where there is a clear business case. Every line of custom code potentially adds long-term technical debt. 🗣️ Poor Communication Between Stakeholders Lack of clarity leads to scope creep and distrust. Use structured check-ins, feedback sessions, and visual materials to keep everyone aligned. Don’t assume everyone interprets documentation or terminology the same way. 🧭 Unclear Governance Structures Cause Project Drift Without decision hierarchies, escalation paths, or steering committees, momentum stalls. Define a governance model on day one for faster decisions, fewer disputes, and smoother collaboration. 🔗 Disjointed Handovers Break Momentum Handovers without proper documentation and walkthroughs create confusion. Standardize them like any other critical process. 🌍 Cultural and Language Differences in Global Teams Multinational setups require carefully designed communication structures. Clarify expectations across time zones and cultures to avoid ambiguity. Don’t assume silence means agreement. 📈 No Metrics Means No Alignment If you’re not measuring what success looks like, you’ll never know when you’re off course. Use shared KPIs to stay aligned and build trust. A shared dashboard of business-focused KPIs keeps the project centered on value. 🤝 Lack of Collaboration Between Client and Consultant Teams A strong partnership creates shared ownership of outcomes. Invite consultants into business conversations and clients into solution design. What misunderstandings have you seen, or helped resolve in SAP projects? ⬇️ #IgniteSAP #SAPConsulting #SAPProjectSuccess

One of the biggest reasons ERP implementations fail isn’t the software. It’s the requirements process. The traditional method is broken: weeks of workshops, piles of documents, and a “sign-off” that means nothing because no one has seen the system. Then, three months before go-live, reality hits. What people said they needed is not what they actually do. There’s a better approach. Get people into a demo environment immediately, before anything is configured. As they describe their work, replicate it on the screen in real time. The moment users see their workflow in context, everything changes. They catch missing fields, misdescribed steps, undocumented dependencies, and the informal workarounds they forgot to mention. 𝐈 𝐜𝐚𝐥𝐥 𝐭𝐡𝐢𝐬 𝐄𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐭𝐢𝐚𝐥 𝐃𝐢𝐬𝐜𝐨𝐯𝐞𝐫𝐲. It shifts the question from “What do you need?” to “What’s missing?” The accuracy jumps, the blind spots disappear, and you eliminate the expensive rework that normally shows up right before launch. From there, load the environment with sample customers, products, and orders. Give SMEs continuous access. Let them test, break things, and explore. Early friction is cheap. Late friction is catastrophic. This approach works for any major system: ERP, CRM, AMS, ecommerce, you name it. The catch: it only works if the facilitator understands both the business and the technology. Not an IT person guessing at operations. Not a business user guessing at system constraints. Someone who can translate in real time and guide the discovery instead of documenting assumptions. If organizations changed only this one part of their implementation process, failure rates would drop fast, and adoption would improve even faster. Flip the process. Show the system first, document later. Requirements become real, not theoretical. If you'd like the framework I use or want to discuss an upcoming project, message me.

ERP won't streamline operations effortlessly. Without planning, it creates chaos instead. Most founders assume an ERP implementation will automatically fix revenue leakage and improve decision-making. The reality? Without proper planning, you get tangled data and frustrated teams. I've watched a founder plug in their ERP expecting magic. Instead: → Data became a mess → Employees grew frustrated → Decision-making got worse, not better The gap between expectation and execution comes down to three things: • No clear strategy before implementation • Lack of team buy-in from day one • Underestimating the complexity of system integration ERP systems are powerful tools for reducing revenue leakage and enabling better decisions - but only when you treat implementation as a strategic project, not a plug-and-play solution. The best founders don't assume technology will solve their problems. They build the strategy, align the team, and execute with precision. That's how you turn an ERP from a headache into a competitive advantage.

Culture eats ERP for breakfast, and most leaders don’t even know it’s on the menu. ERP implementations succeed or fail long before the first workshop or line of code is written. Leadership sets the tone and often unknowingly sets traps. Here’s what I often see: Leaders chase flashy project names instead of aligning culture and strategy. They skip defining actionable business objectives. They select advisors blindfolded because they don’t know what they don’t know. They ignore change management, requirements governance, and stakeholder buy-in. They assume their already overburdened team can “just figure it out.” The result? Overruns, resistance, and a system that doesn’t deliver value. How do you mitigate these risks? Start with clarity: Define business strategy and objectives before tech. Vet advisory partners like you would a CFO, experience matters. Build governance for requirements and change management early. Allocate time and upskill your team; don’t just hand them a new system and hope for the best. If this resonates, share it with a leader who’s about to start an ERP journey. It might save them millions.

I've rescued a few troubled ERP projects in my time. One of the best predictors of implementation failure isn't your System Integrator's experience list.  It's how they talk about YOUR business. 𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 𝟯 𝗿𝗲𝗱 𝗳𝗹𝗮𝗴𝘀 𝘁𝗵𝗮𝘁 𝘀𝗶𝗴𝗻𝗮𝗹 𝘁𝗿𝗼𝘂𝗯𝗹𝗲 𝗮𝗵𝗲𝗮𝗱: 🚩 Red Flag #1: They lead with their methodology, not your business challenges. You're explaining your job costing workflow and how change orders ripple through your operation.  They're nodding along, waiting to tell you about their "proven 7-phase implementation approach." If they're more excited about their process than your problems, they're going to force-fit you into their playbook. What to ask: "What's different about how you'd approach our implementation versus your last three clients?" 🚩 Red Flag #2: They can't tell you who's actually doing the work. You're about to spend 12-18 months on this project.  But when you ask who's leading workshops or configuring your system, you get vague answers about "our experienced team." If they're selling a concept instead of introducing actual people, that team either doesn't exist yet or they're juggling too many projects. What to do: Demand to meet the actual team members before you sign.  Not the partner selling you - the actual people doing the work. 🚩 Red Flag #3: Post-go-live support is an afterthought in the proposal. Their scope has 30 pages about requirements. Post-go-live support gets two paragraphs about "ongoing assistance as needed." I've watched contractors struggle through 90 days after launch because nobody planned for what happens when issues emerge at 7am on a job site. What to ask: "What does your support structure look like months 1-6 after go-live? Who's accountable when we have issues?" Every implementation partner relationship is different. 𝗪𝗵𝗮𝘁 𝗿𝗲𝗱 𝗳𝗹𝗮𝗴𝘀 𝗵𝗮𝘃𝗲 𝘆𝗼𝘂 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 𝘁𝗼 𝘄𝗮𝘁𝗰𝗵 𝗳𝗼𝗿? The implementation partner you choose matters more than the software you select.  Bad software with a great partner recovers.  Great software with a bad partner fails. #ERP #ImplementationPartner #ConstructionTech

1,000 ERP implementations. 1,000 lessons learned. When I started, I made rookie mistakes. Missed requirements. Rushed testing. Underestimated change management. We see this often—especially in professional services. The result? Confusion, rework, lost hours. Sound familiar? But here’s what actually works: → Structured planning from day one → Real-world testing before go-live → Clear change management for every user group → Start data migration ASAP No shortcuts. Not after 10 projects. Not after 1,000. Every project reinforced the basics: - Gather requirements with the real users (not just the loudest voices) - Test with real data (not just demo sets) - Align stakeholders early and repeat often - Don't underestimate data migration The good news? Mastering these steps means predictable outcomes, better margins, and happier teams. ERP isn’t just tech—it’s a transformation for your people, your processes, your bottom line. We’ve seen it happen over and over. The projects that skip the basics always pay more—sometimes for years. If you’re rolling out ERP, don’t shortcut the essentials. How does your team keep project planning and testing front and center? Lessons learned welcome.

Unpopular opinion: Your ERP implementation didn’t fail because of the software. It failed because you treated it like a tech project instead of a business transformation. I see it constantly: Companies drop $200K–$500K+ on NetSuite, hand the whole thing to IT, and hope for the best. Six months later? Broken customizations. Reports no one uses. Processes that are more complicated than before. Then the excuses roll in: “NetSuite is too complex.” “Our partner didn’t get our business.” “We should’ve stayed on QuickBooks.” But here’s the truth: Your CFO should’ve owned this from day one. Not IT. Not ops. Not the NetSuite admin who got voluntold. Your finance leader. Because ERP isn’t a tech decision—it’s a financial operating model decision. Workflows impact your close. Reports impact decisions. Integrations impact visibility. We run a $3B accounting practice on NetSuite. We’ve seen it play out hundreds of times. Successful implementations? Finance + IT as equal partners from requirements through go-live. Failed ones? IT builds what they think finance needs, and finance inherits a system they never wanted. The software isn’t the problem. Ownership is. Curious—who do you think should lead an ERP implementation: finance or IT? Charles #TheBaldNetSuiteGuy

Most ERP rollouts fail—not because of tech, but hidden roadblocks nobody talks about. Our blueprint for breaking through them ↓ 1. Change Resistance: People fear the unknown. Address concerns early. Involve key stakeholders from day one. Communicate benefits clearly and consistently. 2. Data Migration Nightmares: Clean your data before migration. Map fields meticulously. Test, test, and test again. 3. Customization Creep: Stick to out-of-the-box features when possible. Evaluate each customization request critically. Remember: More customization = More complexity. 4. Training Oversight: Invest heavily in user training. Create role-specific guides. Offer ongoing support post-launch. 5. Scope Expansion: Define clear project boundaries. Use a phased approach. Resist the temptation to add "just one more thing." 6. Leadership Misalignment: Secure executive buy-in early. Establish a clear project champion. Keep leadership engaged throughout the process. 7. Resource Underestimation: Plan for the long haul. Budget for unexpected costs. Don't skimp on expert consultants. Navigating these roadblocks requires experience. We've guided countless businesses through successful ERP implementations. Take the first step toward transforming your ERP rollout into a game-changing success. Let's talk.