Making ERP Seamless for Your Team

A machine operator taught me more about ERP in one hour than I had learned from 25 years of tech consulting. I thought ERP was about technology. Then a factory worker proved me wrong. We were rolling out a new ERP module at a manufacturing plant. Flawless on paper. ✓ Clean data. ✓ Tight integrations. ✓ Seamless training. But something was OFF. The line supervisor pulled me aside and said... “This system might be perfect for your screen… but it’s slowing us down.” So I shadowed one of the operators for an hour. No slides. No dashboards. Just observation. What I saw changed how I approach ERP forever. 𝐇𝐞𝐫𝐞’𝐬 𝐰𝐡𝐚𝐭 𝐭𝐡𝐞 𝐨𝐩𝐞𝐫𝐚𝐭𝐨𝐫 𝐬𝐡𝐨𝐰𝐞𝐝 𝐦𝐞: 🚩 He had to memorize 6 extra clicks to complete a job entry. 🚩 The screen timeout was cutting him off mid-task. 🚩 The dropdowns weren’t sorted by frequency of use. 🚩 The barcode scanner worked technically, but needed two hands—slowing the line. And the kicker? → They stopped trusting the system because of one bug that went unresolved for weeks. → Not once did he mention “data models,” “integrations,” or “APIs.” But what he showed me was everything ERP is meant to be about: ☑️ Process. People. Flow. Friction. Trust. That day, I stopped thinking like a consultant. I started thinking like a user. 🧠 And here’s the uncomfortable truth we don’t talk about in ERP consulting ⤵️ ↳ A factory worker’s 3-second delay is more expensive than a 3-month delay in your data migration. ↳ If you want ERP success, don’t just talk to the CIO or the CFO. ↳ Go to the floor. Watch the workflow. Listen to the friction. 𝐁𝐞𝐜𝐚𝐮𝐬𝐞 𝐫𝐞𝐚𝐥 𝐄𝐑𝐏 𝐢𝐧𝐬𝐢𝐠𝐡𝐭𝐬 𝐝𝐨𝐧’𝐭 𝐜𝐨𝐦𝐞 𝐟𝐫𝐨𝐦 𝐝𝐢𝐬𝐜𝐨𝐯𝐞𝐫𝐲 𝐜𝐚𝐥𝐥𝐬. 𝐓𝐡𝐞𝐲 𝐜𝐨𝐦𝐞 𝐟𝐫𝐨𝐦 𝐛𝐨𝐨𝐭𝐬, 𝐠𝐥𝐨𝐯𝐞𝐬, 𝐚𝐧𝐝 𝐠𝐫𝐞𝐚𝐬𝐞 𝐬𝐭𝐚𝐢𝐧𝐬. Are we spending too much time perfecting the tech and not enough time watching how humans actually use it? Would love to hear your thoughts. P.S. The image is created from ChatGPT and is for representation purpose.

Are you considering implementing a new ERP system? Lately, I've engaged in a number of discussions regarding the selection of ERPs, their capabilities, and the intricacies of their implementation process. For any business embarking on this journey, it's a significant decision, but one that holds the potential to transform operations. Drawing from my experience as a CFO, I've witnessed the impact that new ERP implementations can have on businesses. It can present remarkable possibilities to streamline operations, enhance decision-making, and stimulate growth. However, it can also come with its own set of challenges and complexities. So, what exactly does it take to ensure a successful ERP implementation? 1️⃣ Process-Oriented Strategy   - Prioritise Processes: Instead of getting lost in features, focus on your business workflows. Identify areas for enhancement, pinpoint bottlenecks, and imagine how the ERP can boost agility.   - Thorough Mapping: Take stock of current processes and spot any gaps. Consider factors like mobile accessibility, real-time alerts, and data analytics as you modernise. 2️⃣ Harnessing Team Potential   - Team Dynamics: The team driving any ERP implementation is of great importance. You will need to gather a diverse group of executives, project managers, end users, and IT specialists. Their collective insights and dedication will be key to a successful implementation.   - Skills and Expertise: Look beyond job titles. Recruit team members with relevant expertise, industry knowledge, and a knowledge of your chosen ERP platform. 3️⃣ Selecting the Right Implementation Partner   - Industry Understanding: Your chosen partner should be able to grasp the fundamentals of your industry. Seek referrals and validate their track record.   - Methodology: What is their implementation approach? It should reflect their own learning and not just be a generic template. 4️⃣ Avoiding Common Pitfalls   - Robust Governance: Establish strong project governance from the outset.   - Clear Scope Definition: Set precise objectives and requirements - avoid scope creep!   - Data Integrity: Ensure your data is clean and reliable.   - Training: Invest in comprehensive user training, during implementation and after.   - Executive Support: Secure backing from leadership. 5️⃣ People-Centric Strategies   - Inclusive Teams: Engage stakeholders at all levels. Everyone should feel accountable for success.   - Promote Collaboration: Foster open dialogue and teamwork.   - Risk Awareness: Acknowledge potential risks and address them early. Oh, and finally, as the CFO ensure the budget is appropriate and costs controlled! Remember, a successful ERP implementation hinges not only on technology but also on people, processes, and collaboration. I would love to hear about your implementation stories and the key to success. 👇 #ERPImplementation #DigitalTransformation #BusinessGrowth #CFOInsights 

Many companies believe that once an ERP system arrives, all their process problems will disappear. IT teams often say that the current process will be implemented inside the system. The expectation is that the ERP will mirror the real workflow and improve it. The reality is very different. What actually gets implemented inside the ERP is not the process that the business needs. Instead, it is only the part that fits the system’s standard modules. As a result, the final workflow is far away from the process that the operations team expected. This creates serious gaps • The real process is complex, but the ERP captures only fragments. • The old wastes and delays continue, only now inside a digital system. • People believe the ERP will solve everything, but the output becomes even more complicated. • Everyone blames the system, yet the root cause is that the process was never fixed before digitalization. The ERP is not a silver bullet. It is only a tool. If the underlying processes are unclear, lengthy, or full of waste, the ERP will simply make those weaknesses permanent inside the system. The correct approach is very simple. First fix the process. Then simplify it. Then map it. Then implement it. This is the only way to ensure that ERP reflects the real workflow that the business needs. If the process is not corrected before digitalization, the ERP will always be far away from what the business expected.

Your ERP went live successfully. So why is your team still using spreadsheets? I once led an ERP implementation where every decision took forever.  The company's mode of operation was to build consensus on everything. It stretched the project timeline out by months.  But the client was willing to pay for the extended time to get it right. Their operations teams were involved in every design decision, which meant they understood the "why" behind every workflow. They had a perfect launch with over 85% adoption out of the gate.  No spreadsheets. No workarounds.  The team owned it because they built it. Last month I talked to a client who took the opposite approach. Leadership made all the decisions.  The operations teams weren't engaged until 4 months from go-live. Now they're experiencing massive resistance.  The team has zero interest.  And leadership doesn't know how to fix it. The difference between these 2 real-life scenarios comes down to one thing: 𝗼𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽. When your team is told "this is how you'll do it now" without understanding why, they tend to put up walls. When go-live comes, they will default back to what they know. Contractors are natural problem solvers.  If they don't like how something works, even if it works fine,  they will find a workaround. But guess what? Workarounds are why you lacked standardized processes in the first place.  Once someone uses a workaround, they'll use it again.  Then someone else does the same. This is a slippery slope, and it isn't the fault of the technology.  It's simple human nature and habit. In contrast, when your team helps design the processes, they champion the system. If, like my client, you're stuck 4 months from go-live with a resistant team, here's what you can still do:  1. Stop the train.   2. Bring your operations leaders into the room.   3. Show them what's been configured and ask: "What doesn't work for how you operate?"  4. Let them redesign workflows that don't fit.   5. Explain why certain processes need to standardize.   6. Give them ownership of the solution. It might push your go-live.  It might cost more.  But the alternative is going live with a system nobody uses. Building consensus takes longer.  But if you're seeing spreadsheets six months after go-live, you'll wish you had. #ERP #ChangeManagement #ConstructionTech

Half of ERP benefits never materialize because change management was an afterthought. Technology isn’t the barrier. People are. The most common pattern is this: the system goes live, but employees quietly cling to old workarounds. Spreadsheets resurface. Emails replace workflows. Approvals bypass the system. On paper, the ERP is live. In reality, adoption never took hold. I’ve seen companies with modern platforms still reconciling sales orders manually because teams didn’t trust the process. Not because the system couldn’t do it—but because no one invested the time to teach, test, and embed new behaviors. ERP is often treated like a technology project when it’s really an organizational one. Success depends less on configuration and more on communication. If people don’t understand why the system matters—or how their role connects to the bigger picture—efficiency gains never show up. When change management is built in from the start, adoption feels natural. Training is continuous. Leaders model the behaviors they expect. And the technology becomes the default path, not the detour.

Implementing an ERP system is only half the battle. Ensuring your team effectively uses it is the real challenge. Here are 5 strategies to help you optimize user adoption: 1. Involve Users Early Engage key users from the start. Include them in the decision-making and planning processes. Early involvement builds ownership and reduces resistance. 2. Provide Comprehensive Training Offer thorough training sessions tailored to different user roles. Include both initial training and ongoing refresher courses. Well-trained users feel confident and competent. 3. Communicate Clearly Communicate the benefits and changes the ERP system will bring and address concerns and provide regular updates. Transparent communication fosters trust and buy-in. 4. Make It User-Friendly Customize the ERP interface to match user needs by simplifying workflows and minimizing unnecessary steps. A user-friendly system reduces frustration and increases productivity. 5. Offer Continuous Support Set up a support system for troubleshooting and questions by collecting user feedback and making necessary adjustments. Ongoing support ensures continuous improvement and satisfaction. Without proper user adoption, you’re looking at an underutilized system and frustrated team members. With it, you’ve got a powerful tool driving your business forward. 📌 Need a hand optimizing your ERP user adoption? Drop me a message.

ERP implementation isn’t just an IT project, it’s a business transformation. And most failures happen not due to tech, but due to lack of planning, change management, and cross-functional alignment. Here's a break down of the 10 essential steps to successfully implement an ERP system from defining business needs to post-go-live support. ✅ Identify business goals and operational pain points ✅ Align your ERP scope with strategic KPIs ✅ Choose the right ERP based on integration, scalability, and functionality ✅ Build a strong implementation team with defined roles ✅ Reengineer business processes for better efficiency ✅ Migrate clean, validated, and secure data ✅ Customize modules based on user roles and workflows ✅ Test thoroughly to avoid go-live disasters ✅ Train your team and manage organizational change ✅ Provide long-term support and continuous improvement Whether you're modernizing legacy systems or rolling out your first ERP, this roadmap ensures clarity, collaboration, and control at every stage. 💡 Save this post if you're leading or advising an ERP transformation! [Explore More In The Post] For a deep dive into PLM, MES, or CAD and to elevate your understanding of PLM, connect with us at PLMCOACH and Follow Anup Karumanchi for more such information. #plmcoach #plm #teamcenter #siemens #3dexperience #3ds #dassaultsystemes #training #windchill #ptc #training #plmtraining #architecture #mis #delmia #apriso #mes

YOUR ERP IMPLEMENTATION IS DOOMED TO FAIL - UNLESS YOU FOLLOW THESE SEVEN RULES ================================================= After 27 years in ERP, I’m still haunted by one question: Why do ERP implementations fail? We refine requirements across bidding, discovery, and solution design phases, yet many projects collapse. Why? It’s simple: knowing a technical solution is not the same as delivering a seamless customer solution. These skills are worlds apart, like solving math equations versus using quantitative models to dominate the stock market. Here’s how I approach ERP success: 1. Plan Meticulously: A project plan isn’t optional—it’s essential. As Covey said, “Begin with the end in mind.” A solid plan visualizes the entire lifecycle, but too many skip this. 2. Scope Like a Hawk: I lock down scope early and treat any creep like a threat. Change requests aren’t freebies. Want me to deliver that for free? Good luck with that (And customers appreciate my rigidity) 3. Action-Oriented Reporting: My reports focus on clear deliverables and risks, keeping the team sharp. What we did so far has to be put in context of where we are going. 4. Cut-and-Dry Emails: Ownership must be crystal clear. I don't sugarcoat. I end emails with, “If I don’t hear back in three days, this issue is considered closed.” 5. Early User Engagement: Involve users from day one—they need to understand the process and share the load. 6. Follow Vendor Guidelines: It’s shocking how often companies ignore the vendor’s methodology. 7. Build One Team: When the “us versus them” gap disappears, magic happens. My deep ERP process knowledge helps me weave solutions together, but I’ve made three mistakes in my career. They still rankle. 1. Delaying Ownership of a Troubled Project: I hesitated to take control of a failing project, fearing the risks. By the time I stepped in, the damage was already significant. 2. Failing to Communicate Risks: I failed to communicate the risk of a customer decision and a perfect project turned mediocre. I still regret it. 3. Managing Projects Outside My Expertise: Attempting to lead in unfamiliar territory left me floundering. Now, I never underestimate the importance of domain expertise. ERP success isn’t about perfection; it’s about paranoia, vigilance, discipline, and learning from failure. And asking the right questions. Are you asking the right questions to avoid becoming another statistic? #ERPConsulting

What happens when the only person holding your ERP together walks out? One ERP lead traced code, fixed errors, and kept projects moving. When he left, projects stalled. Errors piled up. The whole ERP rested on his shoulders. Don’t hire another “glue person.” Build a team that holds itself up: - Redundancy in key processes - Developers own fixes - Nearshore/onshore overlap - Documented workflows Your ERP shouldn’t depend on one person. How are you making sure it doesn’t?