Why ERP Selection Is a People Game, Not Just a Product Hunt

You’re not just picking software. You’re building a team that will own, operate, and optimize the system for years. Especially in commercial-property construction, where supply-chain complexity often looks like a web of subcontractors, vendors, and asset managers, your ERP choice affects how people communicate and make decisions day to day.

A 2024 Deloitte report found 67% of ERP project failures trace back to poor team alignment—not software shortcomings. So before you even look at feature checklists, focus on who’s in the room and how they grow with the system.

Here are nine tips to help you nail ERP selection by building the right team structure, hiring for skills, and setting up onboarding that sticks.

1. Start by Mapping Critical Skills — Don’t Assume Everyone’s Ready

ERP projects touch multiple parts of the supply chain—procurement, inventory, project management, and finance. Each needs specific know-how.

For example, your procurement lead should understand vendor contract nuances and integration points. Your project manager must grasp job costing and scheduling modules deeply.

Build a skills matrix early: List must-have competencies (e.g., data analysis, process mapping, vendor management) and who currently holds them.

One Houston commercial property firm found only 40% of their core ERP team had project management experience. They brought in contract specialists for the gap, boosting project velocity by 18%.

Gotcha: Don’t overlook soft skills like change management and communication, essential when rolling out new systems. Technical chops alone won't move the needle.

2. Define Clear Roles and Responsibilities — Avoid ERP “Too Many Cooks” Syndrome

ERP projects often stall because everyone thinks they’re the “owner” or nobody steps up.

Assign roles like:

• ERP Project Lead: Drives timelines and coordination
• Supply-Chain SME: Ensures system fits procurement realities
• IT Liaison: Handles integrations and data security
• Change Champion: Advocates for adoption across crews and vendors

In one mid-sized commercial developer’s implementation, explicitly naming a change champion reduced user resistance from 35% to 12% within the first 3 months.

Edge case: In smaller teams, one person may wear multiple hats. Be realistic about workload and consider external consultants for niche roles to avoid burnout.

3. Hire with an Eye for Adaptability — ERP Is a Moving Target

ERP systems evolve with updates, customizations, and business growth. Your team must learn not just “how” but “how to learn.”

Look for candidates who’ve succeeded in cross-functional environments or taken formal training on multiple ERP platforms.

During a 2023 job fair, a Chicago-based commercial-property company prioritized applicants who had completed courses on SAP and Oracle, finding these hires trimmed onboarding time by 25%.

Quick tip: Use behavioral interview questions focused on past adaptability, like how candidates handled a process change mid-project.

4. Build Cross-Functional Teams Early — Break Down Silos Before Go-Live

Supply chain managers, project managers, finance, and IT often operate in silos. ERP forces collaboration.

To prep your team, run joint workshops that cover workflows—say, how purchase orders flow into project budgets.

A New York developer’s ERP rollout brought finance and supply chain staff into monthly planning sessions pre-implementation, cutting reconciliation errors by 30% post-go-live.

Challenge: Cross-functional teams can slow decisions early on. Set clear agendas and use tools like Zigpoll or Slido during workshops to quickly surface consensus or concerns.

5. Use Pilot Projects to Identify Skill Gaps and Build Confidence

Don’t dump the whole system on everyone at once. Pick a low-risk project or asset and run a pilot involving your core team.

This reveals training needs and areas of resistance without jeopardizing major operations.

One Seattle-based firm piloted ERP procurement modules on a small office renovation. They discovered their supply-chain team needed deeper training on automated reorder points, preventing costly stockouts later.

Heads-up: Pilots take extra time. Factor in 6–8 weeks and budget for iterative feedback cycles.

6. Invest in Tailored Onboarding — One Size Doesn’t Fit All

ERP onboarding isn’t just an admin walkthrough. Tailor it by role and prior experience.

For example, warehouse staff might need hands-on mobile app training, while project managers focus on reporting dashboards.

Include interactive elements like quizzes or scenario-based sessions.

Johnson & Johnson Construction (fictional example) segmented onboarding by role and saw a 42% reduction in support tickets in the first 90 days.

Caveat: Customized onboarding requires upfront planning and resources but pays off by lowering frustration and accelerating adoption.

7. Set Up Continuous Feedback Channels — Don’t Wait Until Post-Implementation Reviews

You want real-time feedback during rollout, not just after the dust settles.

Tools like Zigpoll, Culture Amp, or Typeform help gather pulse checks on usability and pain points.

A Dallas commercial-property company surveyed their supply chain every two weeks during ERP launch and identified a recurring bottleneck in purchase approvals. This allowed quick workflow tweaks before issues cascaded.

Warning: Beware survey fatigue. Keep questions short and actionable, and close the feedback loop by sharing results and next steps.

8. Plan for Knowledge Transfer — Avoid Single-Person Dependencies

ERP knowledge often concentrates in one or two “super users.” If they leave or get pulled away, your team stalls.

Create a knowledge base with process docs, video walkthroughs, and FAQs.

Schedule regular cross-training sessions so more people understand core system functions.

A 2022 Aberdeen Group study revealed teams with documented ERP knowledge bases reduced downtime by 38% when key staff turnover occurred.

Limitation: Documentation maintenance can lag. Assign clear ownership for updates or risk obsolete info misleading users.

9. Align Team Incentives with ERP Success — Encourage Ownership

People work harder when their goals align with project outcomes.

Set KPIs related to ERP usage and improvements, such as:

• Reduced purchase order cycle time
• Increased inventory accuracy
• Faster invoice reconciliation

At a Denver-based commercial-property firm, integrating ERP adoption metrics into annual reviews improved user engagement by 20% over two quarters.

Be careful: Overemphasizing metrics can backfire. Balance hard numbers with qualitative feedback and celebrate small wins.

Prioritizing Your Team-Building Efforts

If you’re pressed for time or budget, focus first on clarifying roles and mapping skills (#1 and #2). Without these, even the best ERP software stumbles.

Next, build cross-functional collaboration (#4) and invest in tailored onboarding (#6). They directly impact how well the system fits real-world workflows.

Finally, embed continuous feedback (#7) and knowledge transfer (#8) into your project DNA for sustained success beyond go-live.

ERP implementation is as much about nurturing the right team culture as it is about technology. Put people first, and the system will follow.