Why Strong Fleets Need Every Generation at the Table

Workforce turnover removes more than headcount. It can remove diagnostic memory, operating history, vendor knowledge, and practical judgment that may never have been fully documented.

At the same time, new vehicles require current electrical, digital, software, data, and high-voltage capabilities. No single age group owns all of that knowledge. The operational advantage comes from making it transferable.

A February 2026 transportation-industry fact sheet from the U.S. Department of Labor identified an aging workforce, difficulty recruiting younger workers, rapidly changing technology, retention, and upskilling among the industry’s major workforce challenges. It also reported that 27,418 registered apprentices were served in transportation occupations during fiscal year 2025. [1]

BLS projects that labor-force participation among older Americans will continue rising through 2034. Participation among people ages 65 to 74 is projected to increase from 27.1 percent in 2024 to 29.6 percent in 2034. Participation among people age 75 and older is projected to increase from 8.6 percent to 10.2 percent during the same period. [2]

Many fleets will therefore continue operating with several generations in the same workplace while the work itself becomes more technically complex. That reality makes knowledge transfer, reciprocal development, and shared standards operating requirements rather than optional culture initiatives.

It is tempting to summarize employees according to the generation into which they were born.

Baby Boomers may be described as loyal but resistant to change. Gen X employees may be portrayed as independent and skeptical. Millennials are often associated with collaboration, purpose, and career mobility. Gen Z may be characterized as highly digital, impatient, or dependent on technology.

Those descriptions may sound familiar. They are also too broad to guide serious workforce decisions.

Two employees born in the same year may have completely different technical strengths, communication preferences, family responsibilities, ambitions, and learning styles.

A 24-year-old technician may prefer printed diagrams and hands-on instruction. A 67-year-old supervisor may be the operation’s strongest user of the fleet-management system. A mid-career technician may embrace electric vehicles while a recent graduate prefers conventional diesel work.

Fleet managers should manage the person, not the label.

This principle matters beyond workplace culture. The Age Discrimination in Employment Act prohibits discrimination against people age 40 and older in hiring, assignments, training, promotion, compensation, termination, and other conditions of employment. [3]

Even when no unlawful decision occurs, age-based assumptions can still weaken an operation.

An experienced employee may be excluded from new-technology training because retirement is assumed to be near. A younger employee may be denied meaningful responsibility because commitment is assumed to be temporary.

Both decisions reduce capability. Both can encourage good employees to leave.

Vehicle technology is advancing faster than many organizations’ systems for developing people.

The automotive and transportation sectors are adding electric propulsion, automated features, high-voltage systems, software-based functions, advanced sensors, connected diagnostics, and greater dependence on vehicle data. Industry reporting has identified a growing need to retrain workers in digital skills, battery systems, high-voltage safety, software, and data analysis as vehicle technology changes. [4]

School transportation offers a practical example.

A workforce-training program developed by the California Energy Commission and Cerritos College created electric school bus courses covering high-voltage familiarization, heavy-duty electrical systems, batteries, sensors, charging equipment, network communication, and operator familiarization. Developed with input from colleges, manufacturers, fleet stakeholders, and technicians, the program had trained more than 300 technicians by late 2024. [5]

The lesson extends beyond electric buses.

When fleets adopt new technology, considerable attention goes to vehicle specifications, grants, infrastructure, warranties, and procurement. The workforce plan may receive far less attention.

Who will diagnose the vehicle?

Who understands the older equipment that remains in service?

Who will train drivers and technicians?

Who knows which repairs can be completed internally?

Who recognizes when manufacturer support is required?

Who can connect a new platform to the fleet’s existing procedures?

The answer is rarely one person. It is even less likely to be one generation.

A fleet can purchase new technology in a budget cycle. Developing the judgment required to support it takes considerably longer.

Every fleet has at least one person everyone quietly depends on.

It may be the technician who remembers why a maintenance interval changed twelve years ago, the supervisor who knows which replacement part never fits correctly, the parts employee who knows which vendor will answer after hours, or the dispatcher who can reorganize service when multiple vehicles fail before sunrise.

None of that knowledge appears on an organization chart. Much of it may never appear in an official manual. Yet it helps keep the operation running.

An experienced employee may know which vehicles repeatedly develop the same fault, which routes produce unusual brake or tire wear, which components have been revised, which specifications caused problems in prior purchases, and which repair procedures work under actual fleet conditions.

That knowledge has measurable operational value.

The problem is that many fleets store institutional knowledge in people rather than systems. When a senior employee retires, changes departments, becomes ill, or accepts another position, the organization may discover that no one else understands a critical process.

Replacing the position does not replace the knowledge.

Procedure records an action. Judgment explains the decision behind it.

Useful knowledge-transfer records may include diagnostic case studies, recurring-failure notes, photographs, short repair videos, specification lessons, vendor-performance notes, route-specific maintenance concerns, decision trees, common mistakes, parts cross-references, seasonal procedures, and explanations of why policies changed.

The goal is not to turn experienced employees into full-time technical writers. It is to capture the information the fleet cannot afford to lose.

Knowledge transfer should therefore be treated as preventive maintenance for the organization. It should happen continuously, not after a retirement announcement or resignation letter arrives.

Traditional mentorship assumes that the experienced employee teaches and the newer employee learns. That relationship remains valuable, but useful knowledge does not move in only one direction.

A senior technician may teach practical diagnosis, repair judgment, safe habits, tool control, failure patterns, and the discipline required to complete work correctly. A less experienced or more digitally fluent employee may help colleagues use mobile work orders, telematics dashboards, digital inspections, online service information, scan-tool features, vehicle software, or charging-management systems.

Every employee should be both a teacher and a learner.

The strongest pairings begin with a specific operational need rather than a birth year.

Pair an employee who understands recurring chassis failures with another who can help document those failures in the fleet-management system. Pair a technician experienced in conventional electrical diagnosis with someone trained in network communication and multiplex systems. Pair a supervisor who understands the fleet’s emergency procedures with an employee who can turn that knowledge into a usable digital checklist.

The assignment should be connected to real work. Employees are more likely to exchange useful knowledge while diagnosing an actual failure, completing an inspection, reviewing a specification, or improving a process than during a generic conversation about mentorship.

The relationship works best when neither person is positioned as obsolete and neither is treated as incapable.

Telling experienced employees to “show the new person how things work” is not a workforce-development system.

Without structure, teaching becomes inconsistent. Important lessons are missed. Responsibility remains unclear. The employee doing the training may receive no additional time, recognition, or preparation.

A stronger approach defines what the learner should be able to do, who is responsible for teaching it, how progress will be evaluated, and where the resulting knowledge will be recorded.

Registered apprenticeships, internal technician-development tracks, job shadowing, cross-training, and defined competency checklists can all provide that structure. The precise model will vary by operation.

The fleet should also prepare mentors for the responsibility. Technical expertise does not automatically make someone an effective teacher. Mentors may need guidance on communication, feedback, documentation, and how to allow another employee to perform the work without compromising safety or quality.

The objective is not simply to transfer tasks. It is to develop judgment.

Newer employees often become the unofficial technology department.

They may be expected to troubleshoot tablets, manage digital forms, explain software, organize shared files, or help others navigate new systems simply because they are assumed to be comfortable with technology.

That may solve an immediate problem. It is not a sustainable training plan.

Technology should become part of the fleet’s shared operating capability. Training should be documented, repeatable, and available to everyone whose role requires it.

The same expectation applies in the other direction. An experienced technician should not become the permanent owner of every difficult diagnosis simply because others have not yet developed the required judgment.

Knowledge concentration creates dependency regardless of whether that knowledge is mechanical or digital.

Strong fleets distribute capability.

Multigenerational teams will not always communicate, learn, or approach work in the same way.

They do not need to.

One employee may prefer a conversation. Another may want written instructions. One may learn best by watching. Another may want time to study the service information before beginning.

Those preferences can coexist when the fleet is clear about its standards.

Safety procedures are not generational.

Repair quality is not generational.

Accurate inspections are not generational.

Documentation, accountability, tool control, and respectful conduct are not generational.

A fleet does not need every employee to work identically. It needs every employee to produce work that meets the same operational standard.

Managers should therefore distinguish between preferences that can be accommodated and requirements that cannot be negotiated.

Flexibility in how people learn can strengthen the workforce. Ambiguity about safety, quality, or accountability will weaken it.

Strong multigenerational fleets do not spend much time debating which generation has the strongest work ethic. They identify the capability the operation needs and determine where that capability currently resides.

They make knowledge transfer routine, provide technology training according to job responsibilities, and create opportunities for experienced employees to learn new systems while newer employees earn meaningful responsibility.

They document not only what happened, but why the decision was made. Most importantly, they establish shared standards that allow different people to contribute without requiring everyone to think, communicate, or learn in the same way.

The advantage does not come from having several generations on the payroll. It comes from creating an operation in which their knowledge can reinforce one another.