Senior leaders do not drop out of development programmes because they do not value development. They drop out because the programme was designed for an availability profile that no executive has, and because attending it costs them something in front of their peers.
Understanding both of those things changes the design considerably.
The three reasons attendance collapses
The diary. A five-day residential is not five days. It is five days plus the work that accumulates, and for an operational executive it is also five days of decisions being escalated to someone else. The second and third modules are where attendance falls apart, because by then a genuine crisis has occurred and development is the only thing in the diary that can be moved.
Exposure. A general manager sitting in a room being taught something they are expected to already know is in an uncomfortable position, particularly if their direct reports are in the same room. I have watched capable people disengage entirely rather than ask the question they came to ask.
Irrelevance at the level of examples. Case material drawn from a Fortune 500 restructuring lands badly with an executive whose actual problem is a union relationship at a plant in Rustenburg. The principles may transfer. The credibility does not survive the mismatch.
What completion-friendly design looks like
Short modules, spaced. Two days maximum in any single block, spaced four to six weeks apart, with the dates set six months ahead and protected by the sponsor. Spacing also gives the application period that makes the learning stick.
Cohorts that are peer-level and cross-organisational or cross-divisional. Peers of similar seniority who do not report to one another produce candour. Mixed-level cohorts produce performance.
A real problem as the spine. The most consistently completed executive programmes I have run were built around a live business problem each participant brought, with the content sequenced to help them work it. Completion rates are high because dropping out means abandoning your own project, not missing a class.
Visible executive sponsorship, expressed in behaviour rather than an opening address. If the CEO attends the first module in full and returns for the final presentations, the programme becomes something senior people do not skip. If the CEO sends a video message, it becomes optional.
The content question
Senior technical leaders in South African industry consistently need the same three things, and they are rarely what the brief asks for.
Financial fluency sufficient to argue for capital against a CFO's framing — not accounting, but the ability to build and defend a business case with sensitivities that survive challenge.
Governance literacy specific to their exposure: what their statutory appointments actually oblige them to do personally, and where the personal liability sits. This is consistently the most valued session and the least requested.
Structured decision-making under incomplete information, practised on their own cases. Most technical executives were promoted for technical judgement and have never been taught to make and communicate a decision when the data is genuinely insufficient.
Measuring it honestly
Not satisfaction. Satisfaction is highest for the most entertaining facilitator and correlates with nothing.
Use the project. Each participant's live problem has a defined outcome, and the sponsor confirms three to six months later whether it moved. It is imperfect and attributable enough to argue for. Alongside that, track internal appointment rates into the next level from the cohort over two years.
The programmes worth repeating are the ones where a participant, eighteen months later, describes a specific decision they made differently. That is a small claim and a real one, which is roughly the right standard for this kind of work.