A machine can arrive with manuals, a completed course and a project report showing every contracted training day delivered. The receiving team may still be unsure how to connect a real symptom with the next diagnostic question. This is not necessarily a failure of effort by the technicians or bad faith by the supplier. It may mean the purchase described the transfer of information more clearly than the development of usable local capability.
I believe maintenance learning belongs inside the equipment investment from the beginning. The enterprise is buying a system it expects to operate after the installation specialists leave. The knowledge, access and practice required to support it are therefore part of the operating proposition. They should not appear later as an optional improvement funded only if the equipment happens to expose a gap during service.
Our recent exercise involved thirty-six technicians at two depots. After a supplier course, twenty completed a selected fault-diagnosis task without prompting and sixteen needed support. The finding concerned that task and that learning experience. It did not classify the technicians' general ability. We used it to revise documentation and provide supervised practice, while keeping the next equipment introduction pending its capability review. The follow-up assessment is still being evaluated, so I make no claim about its final result.
### Specify the knowledge that must arrive
The first procurement question is often how many training days the supplier will provide. That is a practical commercial measure, but it does not establish what the receiving team should be able to explain or do afterwards. I want the project to identify the maintenance responsibilities the organisation will retain, the specialist support it will continue to buy and the conditions under which an issue must be escalated. The learning arrangement should follow those decisions.
This does not require the customer to reproduce every part of the supplier's expertise. Some work may properly remain with a specialist service organisation. The important point is that the boundary is understood. Local technicians need to recognise their scope, obtain usable information and reach the appropriate support when the problem extends beyond it. A project can create risk by implying complete self-sufficiency just as easily as by leaving the customer unnecessarily dependent on a supplier for ordinary tasks.
Documentation should be examined through the receiving team's work. A technically accurate manual can assume familiarity that an experienced technician from another equipment family does not yet possess. The supplier and customer can identify those assumptions together. Examples, terminology and the relationship between symptoms and system functions may need explanation. I would rather discover that during preparation than hear, after handover, that all the necessary information existed somewhere in a large document set.
Access also has an organisational dimension. The right people need the agreed material and support route during the shifts when they will use it. That requires planning around staffing, language and the actual service arrangement, without publishing confidential technical details. The CTO's job is to ensure those questions are addressed in the investment account. It is not to prescribe a repair method or encourage staff to work beyond their authorisation because a project promised reduced dependence on external help.
### An exercise should improve the learning design
Practical assessment becomes less useful when everyone expects it to certify the project as successful. Participants may feel that asking for help will be treated as failure, while sponsors may prefer a simple completion total. I want the exercise designed to reveal where preparation needs improvement. That requires clarity about its purpose, the task being examined and the support available. People should not have to protect the investment narrative by pretending that a question is already understood.
In our case, sixteen technicians needed prompting on the selected diagnosis. I did not ask supervisors to publish a ranking. We examined where the explanation and practice had fallen short, including assumptions in the material. Additional supervised work cost money and took time away from other activity. Those consequences belonged in the programme account because they were part of making the introduction credible, not a private remedial burden for the people expected to receive the system.
The exercise itself has limits. One successful task does not establish readiness for every fault, and one request for support does not demonstrate broad incompetence. The next review must retain the scope of what was attempted and the conditions under which it was done. Specialists remain responsible for authorisation and safe working arrangements. A management presentation should not turn a learning observation into a qualification claim that the assessment was never designed to support.
The sponsor's disagreement was understandable: the supplier had delivered the course that the contract required. My recommendation was to fund more work before extending the footprint. That meant acknowledging a weakness in our original purchase definition as well as asking the supplier to improve its material. A useful executive response accepts the organisation's part in creating the gap. It does not make the newest equipment programme someone else's failure simply because the cost appears late.
### Do not outsource the receiving organisation
Even an excellent supplier cannot decide how the customer's supervisors allocate practice time or retain knowledge when experienced staff move. The receiving organisation has responsibilities of its own. I want a named owner for capability after the project team closes, with a practical connection to maintenance planning and the equipment's expected changes. Otherwise a successful initial course can become a historical document while the workforce and system continue to develop.
That continuing responsibility should influence the next purchase. Lessons from supported exercises can improve the specification of manuals, service access and training arrangements. They can also reveal when too many equipment variants create a learning burden that procurement has not priced. I would not make uniformity an absolute goal, since different applications may justify different machines. I would ask that the cost of maintaining several knowledge bases be visible alongside the immediate equipment comparison.
A board considering automation investment can ask whether the receiving organisation is included in the proposal. The question is broader than the number of training days. It concerns the responsibilities retained, the evidence expected before introduction and the resources available when an unfamiliar problem appears. Directors should not run the maintenance programme themselves, but they can challenge an investment case that treats people as ready by assumption while examining every mechanical component in detail.
For my own leadership record, the unfinished follow-up is part of the account. We have identified a gap, funded a response and kept the next introduction dependent on its review. That is the position in October 2026. The story will become stronger through evidence, not by writing its ending early. A maintainable system includes people who can question what they are seeing and obtain the help they need; the purchase should make that possible before the machine becomes an everyday obligation.