Why preparation is where most complexity should be managed.
Why preparation is where most complexity should be managed. Technical diving rewards preparation because underwater is the worst place to discover that a small detail was never organised.
Preparation before complexity
Technical diving becomes simpler underwater when more thinking happens before the diver leaves home. I want cylinders identified, regulators configured, computers set, backup information available, lights selected and spares organised before the waterline.
The exact checklist depends on the dive and training system, but the philosophy is stable: preparation should reduce improvisation. The more complex the dive, the less attractive 'I'll fix it in the water' becomes.
The practical point
The objective is not to look technical. It is to make the dive understandable before it becomes demanding.
My technical dive begins at home
Before leaving, I want to know that the suit, buoyancy system, regulators, computers, lights and stage hardware match the plan. Batteries are checked, cylinders/gases are analysed and marked at the appropriate stage, and written backup information is prepared rather than scribbled while somebody waits to enter the water.
This does not remove the on-site team check. It moves preventable problems earlier, where there is time, light, tools and less pressure.
Technical diving punishes forgotten small things
A technical configuration can involve gas analysis, labels, stages, wetnotes, backup plans, lights, regulators and exposure equipment that all have to agree with the plan. That is why I keep a small technical box rather than rediscovering the same checklist at the dive site. Writable tape and a marker for gas identification, a multi-page wrist slate/wetnotes and mission-specific small spares are part of that organisation.
The purpose is not to carry a miniature dive shop. It is to make predictable preparation repeatable. Gas-analysis information should be recorded clearly; planned stops or contingency notes should be available in a form I can actually read; and the equipment that supports the plan should be checked before the car leaves home.
Preparation reduces task loading later
The more complex the dive, the less I want to improvise basic equipment decisions at the water. A disciplined pre-dive process catches configuration errors while they are still cheap to fix. That connects directly with the problems that often begin before a diver enters the water: many underwater problems were already created on land.
Written backup still has value
Modern computers are extraordinarily capable, but a slate with planned information is independent of a battery, display or menu. In my technical strategy the Perdix 2 can be the primary computer while another instrument in gauge mode and written tables provide a different form of backup. The point is not nostalgia for paper; it is independence between failure modes.
The checklist exists to protect attention
Technical dives already contain enough decisions. If a marker, slate, battery or label can be prepared earlier, I do not want it competing for attention at the entry point. Preparation is therefore a form of task-loading management: move predictable work to the quietest possible moment.
Explore related topics
This article stands on its own, but these pages go deeper into the parts that connect directly with it:
