“People can be infinite. Teams are always finite.”
— A lesson forged from the front lines of ERP implementation.
The Paradox of ERP Execution
After nearly three decades in ERP implementation, I’ve seen a familiar tension emerge — not just within project teams, but within people. Most employees genuinely want to grow — in skill, in scope, in the value they provide to their organizations. And many do grow. They master their functional area(s) of responsibility. They become the go-to expert in a specific function or system area. But at a certain level of competency, a decision point arises:
Do I go deeper into my silo — or do I broaden my understanding to span end-to-end business processes?
ERP, by design, invites that expansion. It connects Finance to Operations, HR to Projects, Procurement to Planning. It creates a platform to move up the value chain — from transactional expertise to strategic insight. Yet many professionals stop short. They stay inside the comfort of their domain. The result?
“They focus on crumbs — chasing customizations, defending legacy processes, or tweaking reports — while missing the full value of net new functionality designed to transform the business.”
It’s not a failure of skill. It’s a failure of perspective — often reinforced by the organizational structure around them. Roles are siloed. Success is measured locally. Incentives rarely reward cross-functional thinking.
ERP projects don’t create this mindset — they surface it. The collaborative, cross-functional nature of ERP work exposes how much of the workforce has shifted from proactive to reactive, from creative to compliant.
This is the paradox we face:
People are capable of boundless thinking — yet structure often conditions them to operate within bounds.
And unless we design ERP teams that consciously break that pattern, we risk building systems that mirror limitation instead of unlocking transformation.
The Infinite Individual or the Pessimistic Realist
Every ERP project includes individuals who see opportunities others don’t. A warehouse supervisor who knows the undocumented workaround that actually makes things flow. A finance analyst who understands the real reason month-end close takes too long. An IT developer who sees a way to automate a key process far better than spec’d. These people are infinite in their potential to improve, innovate, and inspire. But unless teams are designed to listen, capture, and act on these contributions, that potential stays latent.
Too often, individuals are reduced to roles, their insights filtered through business assessment questionnaires, checklists, timelines, and change control. We call for innovation but create environments that mute it.
Bottom line: If you, as the customer, can’t get at least a core portion of your project team and end users to expand their perspective beyond their silos, then the best you can realistically hope for is to break even on your ERP investment.
The Finite ERP Team
ERP teams, by design, are constrained. They have deadlines. They follow charters. They operate under leadership hierarchies and budget oversight. And that’s necessary. Without structure, ERP implementations would become chaos.
“But structure can be constraining – it comes with a cost.”
ERP team members often operate within narrowly defined functional swim lanes. Governance layers can potential slow decision-making. Change requests may evolve into bureaucratic bottlenecks and legacy thinking. Communication suffers as teams scale, and brilliant ideas can be lost simply because they don’t fit the agenda. As human beings, we crave influence but many times we equate influence with control. I have fallen in this trap many times as a project manager. Slowly, I have learned that this does more damage to me and the team that I lead. I still have much to learn but hopefully you can learn from my mistakes.
Even methodologies play a role:
- Waterfall locks in scope too early.
- Agile can move fast but may lack alignment at scale.
- Hybrid attempts to balance both but still struggles with surfacing individual contribution outside of planned ceremonies.
Where It Breaks Down
I’ve seen it happen over and over:
- A front-line user suggests a new configuration that would save days of manual entry. The idea dies within the project.
- A business lead deviates from the playbook to address a specific competitive and/or efficiency business need. They get pulled back into “standard process” because no one makes an investment of time to build a business case.
- A junior team member sees a risk on the horizon but hesitates to speak up, unsure if it’s their place.
- Teams are shaped by who guides them — leaders or managers.
Leaders lean into change and seek opportunity. Managers view change as disruption — something to control, contain, or avoid.
In each case, the finite nature of the team has the potential to suppress the infinite potential of the person. For example, I am leading a project team with this exact dynamic occurring. It is a balance between leveraging new ERP functionality versus “keeping the lights on”.
ERP Leadership Principle: Design for Infinity Inside the Finite
Great ERP leadership means mastering this paradox. Yes, projects must run on timelines, governance, and structure. But those structures must be designed to channel, not choke, individual brilliance.
Here are principles I’ve tried to embed infinity inside finite teams (knowing and doing are two separate competencies):
- Micro-leadership: Empower individuals to lead within their domain, even if they don’t have the title.
- Structured Listening: Use facilitated workshops, idea capture boards, and feedback loops that make it easy for individual insights to rise.
- Guardrails, not cages: Provide governance that protects the project without smothering innovation.
- The ERP Project is a safe place: Make it clear that smart challenges to the norm are not only allowed but expected.
This aligns directly with the ERP Utilization Framework, where Maximum Value Potential (MaxVP) can only be achieved when individuals are fully engaged, empowered, and heard.
What Drives Long-Term ERP Business Value?
A number of interdependent variables shape the potential of ERP to deliver value:
- Rigid structures suppress innovation and reduce resource capacity.
- These, in turn, constrain the realization of ERP-provided functionality.
- Ease of adoption and the quality of implementation execution — especially independence from poor-fit partners — play a significant role.
Following is an illustration of the key principles and relationships that drive ERP Value Realization.
This is not rocket science or any epiphany of mine. There are plenty of examples of ERP failed implementations and lessons learned. What is missing is the will to act! I will state my challenges clearly to the key ERP players:
- ERP Vendors: If you’re not providing free training to enable your customers, it’s hard to claim true partnership. And if you charge full fees before your software/service delivers business value in production, it feels more like short-term profit than long-term success.
- Implementation Partners: If your first step in understanding a client’s needs is a template or checklist, it may be time to rethink your approach. Tools are useful—but true leadership in ERP requires active listening, creative problem-solving, and domain expertise.
- Customers: If you don’t invest in backfilling key roles during implementation, it’s unlikely you’ll see the ROI you’re expecting. And if you think moving to the cloud automatically makes ERP cheaper—well, there’s a hard road ahead.
Conclusion: Leading from Both Sides
ERP leaders must live in two worlds at once. The finite world of timelines, deliverables, and structures. And the infinite world of human creativity, intuition, and vision.
The best results come not from choosing one over the other but from weaving them together. Build teams strong enough to deliver but flexible enough to adapt. Make space for the unexpected insights. Allow the infinite to breathe inside the finite.
That’s where transformation happens. That’s where value lives.
Leave a Reply