When organizations embark on implementing new systems, the expectation is often seamless integration, that application owners have done their legwork, and immediate value will be realized. Yet, reality rarely aligns with those ideals. No matter how robust the planning or how experienced the team, gaps and defects are an unavoidable part of all software. These issues can manifest in ways that are noted below.
- Incomplete Functionality: Missing features or modules that were expected but not delivered
- Elusive Bugs: Intermittent or hard-to-reproduce errors that disrupt workflows
- Configuration Mismatches: Incorrect settings leading to unexpected behavior
- User Experience Gaps: Interfaces that are unintuitive or fail to meet usability standards
- Workflow Misalignment: Processes that don’t fit the organization’s operational needs
- Dependency Conflicts: Issues caused by incompatible libraries or versions
- Reporting Inaccuracies: Dashboards or analytics producing incorrect or incomplete data
- Vendor Support Gaps: Delays or lack of clarity in resolving critical issues because the application is lacking
These overwhelmingly only come to the surface during implementation and after deployment, never during negotiations or contracting. For project managers, these challenges are not just technical; they are deeply operational and strategic.
In a Past Blog I Noted the Following for Reference
No matter how thorough the project planning or how skilled the implementation team is, gaps and defects in the systems we implement are inevitable. As a Project Manager, I am often the first to be impacted by these challenges, and it is my responsibility to ensure they are addressed quickly, appropriately, and transparently.
The complexity is magnified when the organization is forging new ground by implementing solutions as an early adopter and innovating beyond current industry models. In these cases, there are no blueprints to reference and no established best practices to lean on. The team must navigate ambiguity, experiment, and learn iteratively. This pioneering attitude is thrilling, but it also means that gaps and defects are more likely to emerge, simply because the system is built for off-the-shelf requirements that cannot anticipate the specific needs of each client.
Adapting to a system that was not designed for the organization often leads to compromises, workarounds, and frustration. Instead of settling for a “good enough” fit, I advocate for a collaborative approach where stakeholders, developers, and end users work together to shape the system to truly support business goals. Managing these challenges requires not only technical problem-solving but also vision, resilience, and the ability to unite diverse perspectives. Ultimately, dealing with gaps and defects is not just about fixing what is already built; it is about learning from each issue, strengthening future projects, and ultimately, managing gaps is about more than fixing flaws; it’s about building trust.
Why Gaps Happen and Why They Matter
The root of these imperfections often lies in the complexity of modern solutions. Systems are designed to meet broad, generalized requirements, but every organization has unique workflows, priorities, and cultural nuances. When you’re an software developer working as an early builder or pushing beyond industry norms, the challenge intensifies since one only has their knowledge and the knowledge of your first customer. There are no established playbooks, no proven templates, and merely blank canvases with a bold vision. This pioneering approach is exciting, but it also means navigating ambiguity and accepting that the system may not fit perfectly. for everyone, out of the box.
The Cost of “Good Enough”
Faced with these gaps, many teams resort to quick fixes and workarounds building to one customer’s needs. While these may keep the initial operation afloat, it often introduces inefficiencies and erodes confidence in a solution built for one. Settling for “good enough” is tempting, but it rarely supports long-term success. Instead, the focus should shift toward collaboration with all current and potential customers by bringing developers, project managers, scrum masters, product owners, leadership, testers, outside stakeholders, and end users together to co-create solutions that align with business objectives.
From Problem-Solving to Strategic Leadership
Addressing system defects isn’t just about patching code or tweaking configurations. It demands vision and resilience while listening to customer needs. A project manager must balance technical problem-solving with the ability to unite diverse perspectives, foster transparency, and maintain momentum. Every gap is an opportunity to learn about your customers, the system, the organization, and the processes that underpin success models. By documenting lessons learned and feeding them into future projects, teams can transform setbacks into steppingstones.
Tracking and Monitoring Issues for the Life of the Product
Effective management of defects, enhancements, gaps, and other issues establishing a tracking and monitoring system that persists beyond the initial implementation phase. This system will serve as a single source of truth, enabling immediate reference to the status of any item noted including critical defects, requested enhancements, or a process gap throughout the entire product lifecycle.
Key Practices
Centralized Issue Repository: Use a dedicated platform (such as Jira, Azure DevOps, or ServiceNow) to log all defects, enhancements, and gaps. Each entry should include a clear description, severity, owner, and relevant documentation or links.
Lifecycle Status Tracking: Assign and update statuses (e.g., New, In Progress, Resolved, Deferred, Closed) to each item. This allows stakeholders to instantly see the current state and history of every issue.
Persistent Documentation: Ensure that all issue records are retained and accessible for the life of the product, not just during the implementation. This supports root cause analysis, compliance audits, and knowledge transfer to new team members.
Enhancement and Gap Visibility: Track not only defects but also enhancement requests and identified gaps. This holistic approach ensures that opportunities for improvement are not lost and can be prioritized alongside defect remediation.
Automated Notifications and Dashboards: Implement automated alerts for status changes and dashboards that provide real-time visibility into open issues, trends, and resolution timelines.
Linkage to Releases and Changes: Connect issues to specific releases, patches, or configuration changes, creating a traceable history of how and when each item was addressed.
By institutionalizing these practices, organizations ensure that knowledge about system issues and improvements is never lost, and that teams can quickly reference the status and history of any item which supports transparency, accountability, and continuous improvement.
Remediation of System Implementation Issues
1. Root Cause Analysis (RCA)
The first step in remediation is conducting a thorough RCA. This involves gathering all relative stakeholders including project managers, developers, end users, testers, sales teams, and leadership to collaboratively investigate the underlying causes of gaps or defects. RCA should go beyond technical troubleshooting to include operational, process, and communication factors. Documenting lessons learned from each issue not only resolves the immediate problem but also strengthens future projects and builds organizational resilience.
2. Adjust Licensing if Needed
If the RCA reveals that licensing constraints contributed to incomplete functionality or dependency conflicts, organizations are best suited to review and adjust their licensing needs and then agreement. This may involve upgrading to a higher tier, adding modules, or renegotiating terms with vendors to ensure the system meets business needs. Proactive licensing adjustments can prevent recurring issues and support long-term scalability.
3. Receive Credits for Deficiencies or Unmet Service Levels
When gaps or defects result in service levels not being met such as downtime, inaccurate reporting, or workflow misalignment organizations should engage vendors to seek remediation. This often includes negotiating service credits or financial compensation for deficiencies. Transparent documentation of issues and their impact, supported by RCA findings, strengthens the case for receiving credits and ensures accountability from vendors.
Real World Examples
1. Morrisons’ Payroll System Failure (2020)
Context: Morrisons, one of the UK’s largest supermarket chains, implemented a new payroll system to modernize employee payment processes.
What Went Wrong:
- Insufficient Testing: The system was rushed into production without comprehensive real-world testing.
- Data Migration Issues: Errors during migration led to incorrect pay calculations for thousands of employees.
- Lack of Training and Support: Employees were not adequately trained on the new system, creating confusion and inefficiency.
Impact:
Widespread employee dissatisfaction and legal challenges.
Significant reputational damage and financial costs to correct payroll errors and compensate affected staff.
Lesson Learned: Thorough testing, careful data migration planning, and robust training programs are essential before going live with critical systems. [redpilllabs.com]
2. Revlon’s SAP S/4HANA Implementation Failure (2018)
Context: Revlon adopted SAP S/4HANA to streamline operations and improve supply chain efficiency.
What Went Wrong:
- Scope Creep: The project expanded beyond its original plan, increasing complexity.
- Integration Issues: The new system struggled to integrate with existing platforms.
- Poor Change Management: Inadequate communication and training led to user resistance.
Impact:
Severe supply chain disruptions, missed sales, and a sharp decline in stock price.
Legal repercussions from investors due to operational failures.
Lesson Learned: Clear scope definition, strong integration planning, and proactive change management are critical for large-scale ERP implementations. [redpilllabs.com]
Building Trust Through Adaptability
Ultimately, managing gaps is about more than fixing flaws; it’s about building trust. When teams see that issues are handled openly and constructively, confidence grows—not just in the system, but in the leadership guiding the implementation. This trust becomes the foundation for innovation, enabling organizations to chart new territory with confidence.