In short. The attenders who did not cascade do not all tell the same story. Every one of them (: , , , , , ) said time or workload held delivery back. Every one () also had trouble reaching learners. Beyond that, their reasons differ:
- was held up waiting for slides to be signed off;
- and were interrupted by illness or personal events soon after the course;
- and left the session unsure how to start;
- for , and , delivering sat outside their job.
and had backing and a plan, and have sessions booked but not yet run. Those who did cascade met many of the same difficulties, so the barriers alone do not separate the two groups. Two things the cascaders had in place do separate them clearly in these interviews:
- delivering was part of their job, or their organisation was commissioned or paid to do it;
- they had a ready route to learners, such as a CPD slot, an induction programme or a contract.
Cascaders also more often had someone to deliver with or to turn to, but with this few interviews that difference is unclear. The MECC leads among the interviewees give the same reasons, role and time, for the attenders they trained who did not deliver.
What this rests on. This rests on all attender interviews in the corpus. Each was read in full and coded against a fixed list of themes. Every passage where the interviewee says something stopped, delayed or helped delivery was coded with a theme. Each passage was also coded for whether it concerns their own delivery or other attenders they trained, managed or met. A second coder coded the same interviews independently, and each difference was ruled on against the documents. Counts are of interviews, split by the document list's record of whether the person cascaded, and the interviews behind each count are named. These are interviews chosen for the evaluation, not a sample of all attenders. So a count shows how widely a factor came up among them, not how common it is among attenders generally. A difference between the groups is called clear only where it would still hold if any one interview were read the other way; otherwise it is called unclear. Most themes were raised in some form by nearly everyone. The useful contrasts are the themes where the two groups differ.
Who went on to deliver
Of those the list records as having cascaded:
- deliver MECC training routinely (, , , ) (, );
- have delivered only once or twice, or a limited version (, , ). For example, one co-delivered a single finance module: "So, I did the finance module, so we had 17 people on that one." () Another said: "I delivered my first training the other day." ()
Of those recorded as not having cascaded:
- have delivered nothing and have nothing arranged (, , ) (, , );
- have sessions planned or booked but not yet run (, ) (, ).
One person the list records as not having cascaded (: ) now delivers an induction-level version of MECC. They do this only since moving into a public health job (). The list's "No" holds for their original post, not for their current one.
What stopped them
Time and workload. Every interviewee who had not cascaded (: , , , , , ) said time or workload held them back, against of those who had (, , , , ). The difference is unclear. Typical accounts:
- "time has been a huge factor because we’ve had loads of sickness in our team so we’ve been really short staffed." ()
- "it’s just in the real world that extra sometimes is just the extra bit you haven’t got time for." ()
- "I came back to work and actually had a backlog of probably more pressing things" ()
For , time came second to waiting for sign-off. For , the time went on organising sessions that are now booked ().
Delivery was not part of the job, and the backing was thin. of those who had not cascaded (, , ) said delivering fell outside their job:
- "Because this isn’t a core part of my job, it’s something that I’ve chosen to do because it feels like it’s the right thing." ()
- "that’s out with either two things, my pay grade and my remit because this is proper public health." ()
also counts it as part of their own health inequalities role ().
(, , ) said their manager or organisation set no expectation or plan, showed no interest, or held up sign-off. 's manager asked them by email: "we need to tick a box, yes, I’ll do it." () After that, their manager did not expect them to deliver: "from my manager there was no expectation and when we discussed it at appraisal, she just said oh that’s fine." () The trust did expect it, as had been told at the training. They add: "there was certainly no plan put in place from my department." () For , two things held up delivery. The first was waiting for a busy line manager to sign off the slides: "Getting signed off from the line management was the main issue" (). The second was that bespoke slides being prepared by a partner organisation "just took forever." () Against this, and describe managers who backed their delivery (, ).
Left the session unsure how to start, and short of support afterwards. of those who had not cascaded (, , ) faulted how the session prepared them to deliver. and left not knowing how to start:
- "There was a void where I would say right, I’m ready to do what." ()
- "I’d like to deliver it, but I don’t know how." ()
wanted practice at delivering, but still left feeling able to deliver (). Against this, , and praised the session, and said: "Oh, I was really confident. I would have done it the next week." ()
(, , , ) described missing or unusable support afterwards:
- "there hasn’t been any positive communication to go on from, from the end of the course" ()
- "I didn’t know who to ask as well." ()
could not join the forums while ill. felt unable to take part while still waiting for slides (, ). Against this, said the regional coordinator had "always been on hand quite quickly" (). said the regional team "would signpost us a hundred per cent in the right direction." () Some were followed up: was emailed to ask when they planned their sessions ().
Confidence. of those who had not cascaded (, , ) spoke of nerves or fading confidence. For , the doubt was about teaching experienced colleagues what they already do: "it’s like teaching your granny how to suck eggs, like this doesn’t feel right, it’s what they’re doing day in and day out. So, I think confidence dropped off quite quickly." () , and describe themselves as confident trainers (, , ).
Reaching learners. All of those who had not cascaded () described difficulty reaching learners:
- learners not being released: "It’s hard enough for them to get the mandatory training done" ()
- venues: "Trying to book training venues is very hard" ()
- staff on shifts across several centres ()
- for , colleagues who already do what MECC teaches ()
Platforms and materials. of those who had not cascaded (, , , ) raised problems here, for example "I do find the Futures platform really clunky." () found the resources good ().
Interruptions. of those who had not cascaded (, , ) were interrupted. and had illness or personal events soon after the course (, ). In 's team, colleagues moved on, and themselves left while still waiting for sign-off (). COVID had earlier stopped the first attempts of and : "I did the training, COVID kicked in and I never got around to delivering any" (, ).
The cascaders faced most of the same barriers. Among those who did cascade, the counts were:
- for reaching learners;
- for platforms and materials;
- for confidence;
- for support after the session.
So these barriers were raised by both groups and do not by themselves separate them.
What cascaders report of other attenders. Several cascaders reported on other attenders: people they trained or manage, or met on the course. , , and lead MECC in their organisations. spoke of fellow attenders on their course. These are their readings of why others did not deliver, not those attenders' own accounts. Among the cascaders:
- said delivery was not in those attenders' roles (, , , , );
- said those attenders lacked time (, , , ).
In their words:
- "I just haven’t got the capacity to deliver this at the moment or it’s not…it’s not my role" ()
- "they’re not necessarily trainers in their roles, so that’s probably a big issue as well." ()
named those attenders' confidence (, , , , ) (, , ). Those who did not cascade say similar things of fellow attenders. and spoke of time (), and and of confidence ().
Across all interviews, said the session itself left other attenders struggling (, , , , , , , ). Of these, , and said some attenders did not realise they were expected to deliver (, , ). said some attended for the course itself, a qualification or their CV (, , , ) (, , ). suspected the course looks good on a CV because "nobody is going to really ask you whether you actually delivered any sessions or not." () put the result plainly: "I suppose of a lot of people are doing the train the trainer they’re not doing anything with it afterwards" ().
What helped those who did
Delivery built into the job or a contract. This is the clearest difference, and it would still hold if any one interview were read the other way. All of those who cascaded () described delivery as part of their job or remit, or their organisation's paid contract. This compares with of those who did not (, , ):
- "It was part of my job description as well" ()
- "it’s my job to deliver that training, so I have time set aside to do that" ()
- a council contract won to deliver core MECC ()
- an organisation that commissioned a charity to deliver it for two years ()
Against this finding, , and also saw delivery as within their role, yet had not cascaded. now delivers at induction level. Among the cascaders, and said delivering sits at the edge of their job (, ). and saw the same pattern in others (): "it's probably the ones where there's opportunities within their job already to deliver education" (, ).
Time set aside. of those who cascaded (, , ) said they had time or staff for delivery. This compares with of those who did not (, ), so the difference is unclear. said: "I have the time to set up the app, I have the time to evaluate and go and look at the sessions." ()
A ready route to learners. All of those who cascaded () had one, against of those who did not (, , ). This difference is clear, though those who delivered were bound to describe the route they used. The routes included:
- a standing CPD hour: "had we not had that slot already kind of pencilled in and had (name) not sort of given me the support she was, it would have been a lot more difficult." ()
- induction programmes with "a bit of a captive audience" ()
- requests from teams ()
- a contracted number of sessions a year ()
Against this finding, and had a route but had not delivered. has sessions set during site closures (). had "all the infrastructure there on actually booking it and arranging to go out" ().
Backing that expects delivery, not only attendance. Manager support was reported by of those who cascaded and by of those who did not (, , , , ). Support as such does not separate the groups. What the backing covered differs between people more than between groups. For , it was support to attend: "initially my boss asked us because I’m the health and wellbeing champion" (). No expectation followed (). and , by contrast, had backing to deliver and have sessions booked (, ). Among cascaders, managers asked them to lead and to arrange sessions (), or MECC was written into strategy (). , and said the same of others (): "if you’ve got a manager who’s saying come on" (, )
Someone to turn to and someone to deliver with. of those who cascaded (, , , , , ) described help after the session. This compares with of those who did not (, , , ); the difference is unclear. The help included:
- a quick regional coordinator: "And if I’m struggling, I just get in touch with (name of regional MECC at scale coordinator)." (, )
- a local MECC lead who coached them ()
- a former manager they could call on as a mentor ()
of those who cascaded (, , , , ) delivered with a colleague or a team. This compares with of those who did not (, , ), and the difference is unclear. For those who did not cascade, co-delivery was planned or proposed rather than done:
- "We double teamed to do it" ()
- "my colleague sometimes will deliver with me" ()
's team also offers to co-facilitate with trainers who lack confidence: "we'll always offer to co-facilitate if people aren't feeling massively confident." () A new trainer asked to co-deliver "without feeling like I’m thrown into the deep end." () , a routine deliverer working alone, said "it definitely would have, I think helped to have a buddy to deliver it." ()
Ready-made slides that may be adapted. All of those who cascaded () valued the materials, mostly because they could tailor them: "you can adapt it slightly if you need to add a few slides or take a few slides out" (). of those who did not cascade (, , , ) valued them too (). The difference is unclear.
What did not separate the groups. Several themes were raised about equally by both groups:
- prior training experience or a health background ( of those who cascaded, of those who did not);
- personal motivation (, );
- a good session (, ).
, and left the session keen and confident, and left it keen; did not. was stopped by sign-off. lacked follow-up, and had no expectation from their manager. and have sessions booked.
Limitations
The cascade split comes from the document list. One interviewee it records as not cascading now delivers in a new post (). and , who had not delivered, have sessions planned (, ). Accounts of other attenders come mostly from MECC leads, and are their reading of why others did not deliver. A theme that came up in an interview counts as raised whether it was mentioned once or many times. Silence on a theme means the interviewee did not raise it, not that it was absent.