The Gray Wave is a looming risk for organizations across the globe, and many are already beginning to feel its impact. For organizations relying on IBM i, the effect is even greater.
As IBM i veterans retire in large numbers and fewer new professionals enter the field, people who understand why these environments run the way they do are becoming harder to find — and the numbers prove it. Additionally, when these people leave, much of what walks out with them often exists nowhere else.
By now, you may already understand the challenge. Although awareness is a good start, it doesn’t protect your business. The real question is: what do we do about it?
In this article, we’ll show why a plan matters and walk through a four-part playbook to reduce Gray Wave risk and position your IBM i environment for long-term success.
Why Do You Need an IBM i Gray Wave Plan?
The Gray Wave rarely arrives all at once. It builds slowly with each retirement, often over several years, which makes it easy to assume there’s still plenty of time to prepare.
As a result, action gets postponed. Documentation slips down the priority list, hiring plans stay unchanged, and knowledge transfer is delayed until a retirement date is officially announced. By then, the window to prepare has already shrunk.
Organizations then end up making reactive decisions instead of strategic ones. They compete for a shrinking pool of IBM i talent, often at a premium. They try to squeeze decades of tribal knowledge into a few weeks of last-minute sessions. And they may bring in outside help in a hurry, without time to vet it. These approaches tend to fail more often and cost more than planned ones, because there’s simply no time to do the job well.
A plan changes the timeline. It lets you act on your terms, not your expert’s retirement date. And it works at any scale, whether you have one IBM i professional or a hundred.
So, what does a good plan include? It comes down to four parts.
The 4-Part IBM i Gray Wave Plan
While every organization's business priority, IBM i environment, and team structure are different, an effective Gray Wave plan typically consists of four key parts. Below, we'll explore what each part looks like in practice, why it matters, and how to get started.
1. Document What Only Your Experts Know
Some of the most valuable knowledge about your IBM i environment isn’t in a manual, system, or ticket. It lives with the people who have run it for decades.
Over the years, these professionals have accumulated far more than technical expertise. They understand why certain business rules exist, how integrations were configured, which workarounds keep critical processes running, and what to do when something unexpected happens. Much of this knowledge was gained through years of hands-on experience and often exists nowhere but in their heads.
That’s why IBM i system documentation is the foundation of any IBM i Gray Wave plan. Without it, organizations risk losing context that is difficult, expensive, or even impossible to recover once an expert retires.
What does it look like in practice?
The goal isn’t to capture everything at once, it’s to capture information that only your experts know and that would create the greatest disruption if they left tomorrow. This often includes:
- Application and integration architecture
- Business logic and rules embedded within RPG and CL programs
- Disaster recovery and backup procedures
- Job schedules and operational procedures
- Monthly and annual routines
- Security and access management processes
- Troubleshooting guides and common issue resolutions
- Undocumented fixes and workarounds
- Vendor contacts and support processes
How do you get started?
Start by identifying your most business-critical applications and assigning an owner to each. Then ask your experts to record a walkthrough of what they'd want a new team member to know during their first week on the job.
Most importantly, treat IBM i/AS400 system documentation as an ongoing practice rather than a one-time project. The organizations that preserve knowledge most effectively are those that make documenting and updating information part of their everyday operations.
2. Hire Beyond Experienced IBM i Professionals
Many organizations wait to replace retiring experts with equally experienced IBM i professionals. In theory, that sounds reasonable. In practice, it’s becoming increasingly difficult.
Experienced professionals are scarce, and most are already employed. If your hiring plan depends on finding someone with decades of experience, you may have to compete for talent in a pool that is shrinking every year. This, in turn, drives up hiring costs and extends recruitment timelines.
That’s why another key part of a Gray Wave plan is rethinking who qualifies as an IBM i candidate.
IBM i skills can be taught. Experienced developers in .NET, COBOL, Java, Python, SQL, and other technologies already understand programming fundamentals. With the right onboarding and mentorship, they can learn the platform and its core programming languages.
What does it look like in practice?
Rather than limiting your search to experienced IBM i professionals, consider:
- Hiring junior developers with strong aptitude and problem-solving skills
- Inviting internal candidates for IBM i training initiatives
- Looking for professionals experienced in modern languages and platforms
- Recruiting recent graduates from colleges, universities, and training programs
How do you get started?
Review your most recent IBM i job posting and rewrite it around potential instead of years of experience.
3. Recruit Before Your Expert Walks Out
IBM i system documentation can tell someone what to do. Working alongside an experienced IBM i professional teaches them how and why it’s done.
When organizations begin hiring only after a retirement is announced, new hires are expected to absorb decades of experience through a handful of documents, meetings, or walkthroughs. This approach rarely captures the full picture.
That’s why another key part of a Gray Wave plan is creating an overlap period between experienced professionals and their successors.
An overlap period gives new team members the opportunity to learn through observation, day-to-day problem solving, and collaboration. They can understand business context, participate in routine operations, gain exposure to real-world situations, and ask questions that documentation alone cannot fully answer.
What does it look like in practice?
An effective overlap often includes:
- Conducting job-shadowing sessions to help new hires learn how experts handle day-to-day responsibilities and unexpected situations
- Performing reverse shadowing to allow new hires to take the lead while experts observe and provide guidance
- Reviewing applications, business rules, code, and processes one-on-one
- Working through incident resolution, operational support, and troubleshooting activities together
- Transferring responsibilities over time
How do you get started?
Identify one or two roles that would cause the greatest disruption if they became vacant in the next few years. Based on the expected retirement timeline, onboard successors or hire suitable candidates for those roles. This gives new team members enough time to learn alongside the people who know the environment best.
4. Build Relationships with Trusted IBM i Partners
Even well-run IBM i teams are often small. When one person is on leave, transitioning out of the organization, or stretched across too many priorities, support requests pile up and strategic plans stall. During the Gray Wave, that pressure only grows, because your team is losing experience while the workload stays the same.
Many organizations begin searching for external support only after a critical issue arises, a key employee retires, or a project falls behind schedule. By then, they have little time to evaluate providers, transfer knowledge, or establish an effective working relationship.
That’s why another key part of a Gray Wave plan is building a relationship with a trusted IBM i solutions provider before you urgently need one.
A well-vetted, experienced IBM i solutions provider can supplement your internal team, provide specialized expertise, and strengthen operational resilience. Rather than replacing your existing staff, the right provider serves as an extension of your team, helping ensure critical knowledge and support remain available when needed.
What does it look like in practice?
A strong partnership often helps you assess existing environments, systems, and processes, and plan for future growth in line with business strategy. This can include:
- Access to specialized IBM i experts on demand
- Day-to-day IBM i maintenance and support operations
- IBM i system documentation and knowledge transfer initiatives
- IBM i/AS400 modernization, integration, and enhancement efforts
How do you get started?
Identify areas where your team is most dependent on a small number of individuals or lacks specialized expertise. Then begin evaluating IBM i partners based on those findings. Look for IBM i solutions providers with proven experience, strong references, and a track record of long-term client success.
Once you've selected a provider, start with a small, low-risk engagement, such as addressing a support backlog or conducting an application review. This allows you to evaluate the partner's IBM i expertise and how effectively they work with your team before relying on them for business-critical initiatives.
How the 4-Part IBM i Gray Wave Plan Works
It's easy to read a plan like this as a way to replace experienced IBM i professionals who are approaching retirement.
Fortunately, that's not the goal. The real goal is continuity: keeping your critical operations running while ensuring your business knowledge and technical expertise within reach, no matter who joins, moves on or retires.
Navigating the Gray Wave isn’t about finding a perfect replacement for every departing expert. It's about building the documentation, systems, and teams needed to remain resilient when key individuals leave.
This is where the four-part plan works together:
| Planning Component | What It Helps Accomplish |
|---|---|
| Documentation | Protects critical knowledge before it is lost |
| Broader Hiring | Expands the pool of potential future talent |
| Overlap Period | Transfers experience, context, and practical knowledge that documents can’t capture |
| Trusted Partnership | Adds expertise, operational resilience, and support |
Each part addresses a different aspect of Gray Wave risk, but none is fully effective on its own. IBM I system documentation preserves knowledge, but it can’t capture every lesson learned over decades. Hiring expands your talent pipeline, but new team members need time to learn. An overlap period speeds up that learning, while trusted partners provide additional support and stability when internal resources are limited.
Together, these parts help turn retirements into manageable transitions rather than business disruptions.
Where Should You Start with the IBM i Gray Wave Plan?
You don't need to tackle all four parts of the IBM i Gray Wave plan at once. In many cases, the most important step is simply getting started. Begin with one question: which of these four areas is our biggest gap today?
If your most experienced developer is a few years from retirement, documentation and an overlap period likely come first. If hiring has stalled, consider broadening your search. If your team is already stretched thin, a trusted IBM i partner can help ease the pressure while you build the rest of your plan.
Every document created, every new team member mentored, and every succession conversation held today can help prevent costly disruptions tomorrow.
If the plan feels overwhelming, you don't have to navigate it alone. Our IBM Champions can help assess where you stand and build a Gray Wave plan that aligns with your organization's needs. Start the conversation with our IBM i experts today.
Not sure what you should be documenting? In the next post in our Gray Wave series, we'll take a closer look at the things you should document before your most experienced developer retires.