In a previous post I talked about why skill alone doesn't build real rescue experience. You need small simulations that put people under actual pressure. Skill plus pressure is what builds the pattern recognition a real incident demands. That played out just like that last weekend.
I was working with an Alpine Cliff Rescue Team on a refresher. We built the training in layers. Day one started with gear checks, then basic skills on flat ground, then an indoor wall, then out to a site with an 8 metre vertical cliff. Day two we flew onto a glacier and worked on the ice: placing anchors, team rigging, then breaking it down into smaller two-person rescue rigging.
Team Leader, Attendant and Edge are about to go operational. Fox Glacier, NZ.
With about an hour left, I asked the team what they wanted to do. They chose a slightly more complex rescue. But this time there was a real constraint attached: get to the helipad within an hour, or miss the ride down the valley.
That constraint changed how they operated. More urgency in every decision, more like an actual callout than a drill. They did the briefing, got the rescue rigged, casualty packaged, completed the tasking, the system broken down, and made the helipad inside the hour.
All that layered skill work built the foundation, but it was the constraint in that last hour that pulled a different response out of the team.
That's the micro-lesson inside the lesson:
Skill tells you what a team can do. Constraint tells you what they'll actually do when it counts.
Grant
P.S. Tech Tuesday is my own micro-lessons shared with you on a regular basis.
