Are you able to convey some more general or high-level understanding, such as: "A procedure has a starting point, steps in sequence, possible repeated steps, and an end point." For example, one could start with trying to describe/document how to move physically in a room to get from one place to another. Then suggest, e.g. as a bridge, most computers can only work with a written descriptions of a procedure.
The code club lessons come with fairly explicit instructions that tell the kids what they need to do - mostly they only need help from the tutors when they can't find something (e.g. a particular command in whatever IDE they're using) or work out why they're not getting the expected result (usually because they've mistyped something). The super high level concept of "you have to provide explicit steps for the computer to follow" isn't really the blocker.
