Author: Roni Essex
There is a particular kind of confidence that comes from watching a product survive a laboratory test. A machine applies a carefully measured load, sensors record what happens, a computer produces a graph and somebody in the engineering department confirms that everything falls within the expected limits. The results look reassuring, especially when the product has survived thousands of repetitions without showing any obvious signs of failure. You have numbers, documentation and a repeatable process. From a technical perspective, that's exactly what you want.
Then you give the product to an athlete, and three days later they come back with a problem nobody anticipated.
It's one of the more frustrating realities of product development. You can spend months designing something, analysing its behaviour, testing materials and refining details, only to discover that a person using it in the real world has found a weakness your entire development process overlooked. Sometimes the problem is serious. Sometimes it's something almost embarrassingly simple, like a component that becomes uncomfortable after an hour, a connection that gradually loosens or a surface that behaves differently when wet. The product hasn't necessarily failed because the engineering was poor. It may have failed because the assumptions behind the testing were incomplete.
Laboratory testing is essential, particularly for equipment that must withstand repeated physical loads. Engineers need controlled conditions to understand how materials behave, how components interact and where structural weaknesses might develop. Without those measurements, product development would involve far too much guesswork. But laboratory tests are only as useful as the conditions they reproduce, and the real world has a remarkable talent for introducing conditions nobody thought to include.
Consider a pair of carbon freediving fins. In a controlled environment, you can examine blade stiffness, measure deflection under load, assess the integrity of the laminate and investigate how the structure responds to repeated bending. These tests can tell you a great deal about the material and the consistency of the manufacturing process. They can help identify defects, compare designs and establish whether a product meets specific engineering requirements.
What they cannot automatically tell you is how the complete system will behave when an experienced freediver uses it across hundreds of dives, with different kicking techniques, varying water conditions, changing temperatures and the occasional less-than-gentle encounter with a boat ladder.
The athlete introduces variables that are difficult to reproduce in a laboratory because human movement is rarely as consistent as a testing machine. Two divers with similar body weight and strength can place very different demands on the same pair of fins. One may use a compact, controlled kick, while another produces a larger movement with a more aggressive change of direction. One may spend most of their time descending along a line, while another regularly dives in currents, manoeuvres around rocks or swims considerable distances on the surface.
Even within the same individual, technique changes with fatigue, depth, equipment configuration and the demands of a particular dive. The loading pattern that looks perfectly reasonable during a controlled test may become considerably more complicated when the product is used by somebody who is tired, moving awkwardly or reacting to an unexpected situation.
This doesn't make laboratory testing less valuable. It makes it incomplete by itself.
A good development process needs both controlled measurement and uncontrolled reality. The laboratory helps engineers understand what a product is designed to do. Real-world testing reveals what actually happens when people start using it. The most useful information often comes from the difference between those two things.
And that's where athletes become much more than people who demonstrate a product. They become an important part of the engineering process.
Athletes Are Very Good At Finding Problems
If you want to discover the limits of a piece of sports equipment, giving it to somebody who uses that equipment occasionally is not necessarily the most efficient approach. Recreational users are extremely important because they represent the conditions in which many products will spend most of their lives. But experienced athletes often expose weaknesses much faster, simply because they use equipment more frequently, more intensively and with a level of technical awareness that makes small differences easier to identify.
An elite freediver may complete more demanding dives in a training period than a recreational diver performs in an entire season. A competitive cyclist can accumulate extraordinary mileage under conditions that place continuous stress on components. A professional climber may repeatedly load equipment in ways that reveal details a casual user would never notice. These athletes are not necessarily trying to damage anything. They are simply operating closer to the boundaries of what the equipment is expected to handle.
That makes them particularly useful during development.
The important distinction is that an athlete doesn't need to break a product to reveal a problem. Sometimes the most valuable feedback concerns something that remains structurally intact but doesn't perform as intended. A fin may survive every test while still feeling unstable during a particular phase of the kick. A foot pocket may provide excellent energy transfer but create uncomfortable pressure after repeated dives. A component may be strong enough to withstand the expected load while gradually becoming difficult to use as sand, salt and repeated handling begin affecting it.
These aren't necessarily dramatic failures, and that's precisely why they matter. A product doesn't have to snap in half to disappoint somebody. It can fail by being uncomfortable, inconsistent, unnecessarily complicated or simply less effective than it should be.
Experienced athletes can also identify differences that are difficult to describe using conventional measurements. They may notice that a fin responds immediately at the beginning of a kick but feels less controlled during the return movement. They may describe a connection as slightly vague, even when the measured structural movement appears small. They may feel that a particular configuration works beautifully during relaxed diving but becomes less predictable when they increase their effort.
That feedback can be frustrating for engineers because it doesn't always arrive in a form that can be entered directly into a spreadsheet. An athlete might say that something feels wrong without being able to explain precisely why. The challenge is to translate that observation into a technical question that can be investigated.
Is the problem related to stiffness distribution? Is there unwanted movement between components? Does the geometry affect the way force is transmitted? Is the sensation caused by fit, technique or the interaction between several parts of the system?
These are useful questions, and they may never have been asked if the product had remained in the laboratory.
Of course, athletes are not infallible. Exceptional performance doesn't automatically make somebody an expert in materials science, manufacturing or mechanical design. An athlete may correctly identify a problem while proposing a solution that would introduce several new ones. They may prefer a configuration because it suits their technique, even though it would be less appropriate for most other users. Personal preference can also influence feedback, particularly when athletes have spent years adapting to a particular type of equipment.
This is why listening to athletes doesn't mean allowing them to design products by committee. It means taking their experiences seriously while applying engineering judgement to understand what those experiences reveal.
A particularly useful approach is to look for patterns. If one athlete reports an unusual sensation, the observation deserves investigation. If several athletes with different techniques independently describe the same issue, the evidence becomes more compelling. If a problem appears only under certain conditions, those conditions may point toward a design limitation that can be reproduced and measured.
Sometimes the athlete is wrong about the cause but absolutely right that something needs attention.
The best testers are not always the most famous athletes either. A technically demanding competitor can provide valuable performance feedback, but so can an instructor who spends hundreds of hours in the water, a spearfisher who regularly uses equipment around rocky coastlines or a recreational diver who notices a recurring inconvenience that experienced professionals have simply learned to tolerate.
Different users reveal different problems. The important thing is to choose testers according to what you need to learn rather than how impressive their names will look in a marketing campaign.
Because there is a considerable difference between using athletes to validate a design and using athletes to advertise one.
The Problems Nobody Thought To Simulate
One of the most interesting things about real-world testing is how often problems emerge from combinations of perfectly ordinary circumstances. Individually, none of the conditions seems particularly demanding. Together, they create a situation that the original testing programme may never have considered.
Take temperature, for example. Materials can behave differently as temperatures change, and the effect may extend beyond simple strength or stiffness measurements. A component that fits perfectly in a workshop may feel different after spending time in cold water. A material that provides comfortable contact during a short test may become irritating during prolonged use. A connection that functions smoothly when clean and dry may behave differently after repeated exposure to salt, sand and moisture.
None of these possibilities is especially surprising. Engineers understand that environmental conditions influence material behaviour. The difficulty lies in reproducing the enormous number of combinations that occur during actual use.
Equipment is also rarely treated with the consistency that testing procedures assume. It gets packed into bags, transported in vehicles, stored on boats, left in the sun, rinsed imperfectly and occasionally handled by somebody who is more interested in getting into the water than following the manufacturer's ideal maintenance routine.
This is not necessarily misuse. Much of it is simply normal life.
A pair of freediving fins may spend hours inside a protective bag, be carried across uneven ground, placed on the deck of a boat and used repeatedly throughout a training day. They may encounter accidental impacts, changing temperatures and loads that differ considerably from those produced during a controlled bending test. The fins might perform beautifully underwater but reveal a weakness during transport or handling. From the user's perspective, that weakness is still a product problem worth understanding.
A good design needs to account for the environment in which the equipment actually exists, not just the moments when it is performing its primary function.
This is particularly important when several components are designed to work together. Testing an individual part can provide valuable information about its strength and durability, but the complete assembly may behave differently. Loads are transferred between components, small movements can accumulate and the way a person interacts with the system can influence the performance of every part.
With freediving fins, for example, the relationship between the blade and foot pocket matters enormously. A well-designed carbon blade can only deliver its intended performance if the connection allows force to be transferred effectively. At the same time, the foot pocket must fit securely and comfortably enough for the diver to maintain a consistent kicking technique. Improving one characteristic without considering the others can produce a technically impressive component that doesn't work particularly well as part of the complete system.
This is where real-world feedback becomes especially useful. Athletes don't experience isolated components. They experience the entire product, often without knowing which individual part is responsible for what they feel.
And sometimes they reveal problems that have very little to do with structural strength.
Imagine a piece of equipment that requires a complicated adjustment before use. In a workshop, the process takes thirty seconds and works perfectly every time. On a moving boat, with wet hands and several people preparing to enter the water, the same adjustment becomes annoying. Nothing has broken, and the mechanism may be operating exactly as designed. But the product is making the user's life more difficult than necessary.
That matters.
Good product development should investigate not only whether something can withstand demanding conditions, but whether people can use it reliably and comfortably within those conditions. Ease of use, maintenance, consistency and practical handling are all part of performance, even if they don't appear on the most impressive engineering graphs.
There is also a distinction between testing until something breaks and deliberately exposing people to unnecessary risk. For safety-critical equipment, destructive testing belongs in controlled environments where failure can be examined without endangering anyone. Athletes should never be expected to discover structural limits by pushing equipment beyond established safety margins during a dive.
Instead, real-world testing should operate within an appropriate safety framework, using carefully selected prototypes, defined operating limits, inspection procedures and a clear process for reporting concerns. When a problem appears, engineers can investigate it through controlled testing and, where appropriate, deliberately reproduce the failure away from the athlete.
The goal is not to see how much abuse somebody can survive. It's to understand how the product behaves under realistic demands and identify weaknesses before those weaknesses become somebody else's problem.
That approach may be less dramatic than handing a prototype to an athlete and telling them to destroy it, but it's considerably more useful.
And it produces better products.
A Product Is Finished When The Real World Agrees
There is a temptation in product development to treat testing as the final stage of a largely completed process. The design has been approved, the materials have been selected, the manufacturing method is established and the prototype looks exactly as intended. Testing becomes something that confirms the decisions already made.
The problem with that mentality is that it makes unexpected feedback feel like an inconvenience rather than an opportunity.
If an athlete identifies a weakness late in development, the discovery may require changes to tooling, materials, geometry or manufacturing procedures. Those changes can be expensive, and they may delay a launch that people have already spent months preparing. Nobody particularly enjoys hearing that a product needs another round of development when everything appeared to be going according to plan.
But discovering a problem before release is almost always preferable to discovering it after customers have started paying for the product.
There is also a cultural element to this. Companies need to create an environment in which testers feel comfortable being critical. If an athlete believes their role is to support a brand, they may hesitate to describe a product as uncomfortable, inconsistent or disappointing. They may soften their observations because they appreciate the relationship or don't want to seem difficult.
That's understandable, but it undermines the purpose of testing.
The most valuable feedback is often the feedback nobody wanted to hear. A tester who says everything is fantastic may be genuinely enthusiastic, but they haven't necessarily provided much information. Somebody who can explain exactly where a product feels less effective, when the problem occurs and how it compares with other equipment is contributing something much more useful.
Companies should want that kind of criticism, particularly from people who understand the activity well enough to distinguish a genuine design issue from unfamiliarity with a new product.
They should also be willing to discover that their original assumptions were wrong.
Perhaps a feature that looked promising during development provides little practical benefit. Perhaps an apparently minor detail has a much greater influence on comfort than expected. Perhaps the configuration preferred by the engineering team works beautifully for a small group of athletes but creates difficulties for a broader range of users.
These discoveries aren't evidence that the development process has failed. They are evidence that the process is working, provided the company is prepared to act on them.
At Alchemy, the philosophy behind developing high-performance freediving equipment has to account for both sides of this relationship. Carbon construction, blade geometry, manufacturing consistency and component design require technical understanding and controlled evaluation. But those decisions ultimately exist to serve somebody moving through the water. The experience of the diver is not a secondary consideration that can be addressed once the engineering is finished. It is one of the reasons the engineering exists in the first place.
This is particularly relevant when developing equipment for athletes whose demands are exceptionally high. Small differences in fit, responsiveness or control can become significant when somebody is performing repeated deep dives or spending long periods training. Their feedback can reveal details that deserve closer investigation, even when the product appears to satisfy its original technical specifications.
At the same time, the objective should never be to create equipment that works beautifully for one exceptional athlete and nobody else. The challenge is to understand which improvements reflect genuine advances in design and which are simply preferences associated with a particular individual.
That requires testing across different users, conditions and levels of experience. It also requires accepting that no single test, athlete or laboratory measurement can provide a complete picture.
There is a broader lesson here that applies well beyond freediving. The best products are rarely the result of one brilliant idea executed perfectly on the first attempt. They emerge through a process of assumptions being challenged, problems being identified and decisions being revised. The engineer contributes technical understanding. The athlete contributes experience. Manufacturing contributes its own constraints and possibilities. And the final product improves when those perspectives are allowed to influence one another.
Sometimes that means adding something. Often it means removing something that seemed clever but didn't actually help. Occasionally it means starting again because the original approach wasn't as good as everyone hoped.
None of those outcomes is particularly glamorous, and they don't always make interesting marketing stories. A product that works reliably after years of refinement may look almost identical to one that was developed much more quickly. The difference is often hidden in details that customers will never consciously notice.
Perhaps that's how it should be.
Most people don't buy sports equipment because they want to appreciate the complexity of its development process. They buy it because they want to do something they enjoy, and they expect the equipment to help rather than get in the way. They shouldn't need to understand material fatigue, load distribution or manufacturing tolerances to trust that a product has been designed with their needs in mind.
They simply want it to work.
And when equipment performs so naturally that the athlete stops thinking about it, that's often a very good indication that somebody has spent a considerable amount of time thinking about it on their behalf.
Laboratories can tell us whether a product meets the requirements we know how to measure. Athletes can help us discover requirements we didn't know we were missing. Neither approach replaces the other, and the strongest development processes recognise the value of both.
Ultimately, a product shouldn't be considered successful simply because it survived the tests its designers expected it to pass. It should earn that confidence through the conditions, people and unpredictable situations it was actually created for.
That's why you give equipment to people who are capable of exposing its weaknesses. Not because you want them to break it, but because you want to find out what needs improving before anyone else has to.
Products Should Be Tested By People Who Can Break Them
Author: Roni Essex
There is a particular kind of confidence that comes from watching a product survive a laboratory test. A machine applies a carefully measured load, sensors record what happens, a computer produces a graph and somebody in the engineering department confirms that everything falls within the expected limits. The results look reassuring, especially when the product has survived thousands of repetitions without showing any obvious signs of failure. You have numbers, documentation and a repeatable process. From a technical perspective, that's exactly what you want.
Then you give the product to an athlete, and three days later they come back with a problem nobody anticipated.
It's one of the more frustrating realities of product development. You can spend months designing something, analysing its behaviour, testing materials and refining details, only to discover that a person using it in the real world has found a weakness your entire development process overlooked. Sometimes the problem is serious. Sometimes it's something almost embarrassingly simple, like a component that becomes uncomfortable after an hour, a connection that gradually loosens or a surface that behaves differently when wet. The product hasn't necessarily failed because the engineering was poor. It may have failed because the assumptions behind the testing were incomplete.
Laboratory testing is essential, particularly for equipment that must withstand repeated physical loads. Engineers need controlled conditions to understand how materials behave, how components interact and where structural weaknesses might develop. Without those measurements, product development would involve far too much guesswork. But laboratory tests are only as useful as the conditions they reproduce, and the real world has a remarkable talent for introducing conditions nobody thought to include.
Consider a pair of carbon freediving fins. In a controlled environment, you can examine blade stiffness, measure deflection under load, assess the integrity of the laminate and investigate how the structure responds to repeated bending. These tests can tell you a great deal about the material and the consistency of the manufacturing process. They can help identify defects, compare designs and establish whether a product meets specific engineering requirements.
What they cannot automatically tell you is how the complete system will behave when an experienced freediver uses it across hundreds of dives, with different kicking techniques, varying water conditions, changing temperatures and the occasional less-than-gentle encounter with a boat ladder.
The athlete introduces variables that are difficult to reproduce in a laboratory because human movement is rarely as consistent as a testing machine. Two divers with similar body weight and strength can place very different demands on the same pair of fins. One may use a compact, controlled kick, while another produces a larger movement with a more aggressive change of direction. One may spend most of their time descending along a line, while another regularly dives in currents, manoeuvres around rocks or swims considerable distances on the surface.
Even within the same individual, technique changes with fatigue, depth, equipment configuration and the demands of a particular dive. The loading pattern that looks perfectly reasonable during a controlled test may become considerably more complicated when the product is used by somebody who is tired, moving awkwardly or reacting to an unexpected situation.
This doesn't make laboratory testing less valuable. It makes it incomplete by itself.
A good development process needs both controlled measurement and uncontrolled reality. The laboratory helps engineers understand what a product is designed to do. Real-world testing reveals what actually happens when people start using it. The most useful information often comes from the difference between those two things.
And that's where athletes become much more than people who demonstrate a product. They become an important part of the engineering process.
Athletes Are Very Good At Finding Problems
If you want to discover the limits of a piece of sports equipment, giving it to somebody who uses that equipment occasionally is not necessarily the most efficient approach. Recreational users are extremely important because they represent the conditions in which many products will spend most of their lives. But experienced athletes often expose weaknesses much faster, simply because they use equipment more frequently, more intensively and with a level of technical awareness that makes small differences easier to identify.
An elite freediver may complete more demanding dives in a training period than a recreational diver performs in an entire season. A competitive cyclist can accumulate extraordinary mileage under conditions that place continuous stress on components. A professional climber may repeatedly load equipment in ways that reveal details a casual user would never notice. These athletes are not necessarily trying to damage anything. They are simply operating closer to the boundaries of what the equipment is expected to handle.
That makes them particularly useful during development.
The important distinction is that an athlete doesn't need to break a product to reveal a problem. Sometimes the most valuable feedback concerns something that remains structurally intact but doesn't perform as intended. A fin may survive every test while still feeling unstable during a particular phase of the kick. A foot pocket may provide excellent energy transfer but create uncomfortable pressure after repeated dives. A component may be strong enough to withstand the expected load while gradually becoming difficult to use as sand, salt and repeated handling begin affecting it.
These aren't necessarily dramatic failures, and that's precisely why they matter. A product doesn't have to snap in half to disappoint somebody. It can fail by being uncomfortable, inconsistent, unnecessarily complicated or simply less effective than it should be.
Experienced athletes can also identify differences that are difficult to describe using conventional measurements. They may notice that a fin responds immediately at the beginning of a kick but feels less controlled during the return movement. They may describe a connection as slightly vague, even when the measured structural movement appears small. They may feel that a particular configuration works beautifully during relaxed diving but becomes less predictable when they increase their effort.
That feedback can be frustrating for engineers because it doesn't always arrive in a form that can be entered directly into a spreadsheet. An athlete might say that something feels wrong without being able to explain precisely why. The challenge is to translate that observation into a technical question that can be investigated.
Is the problem related to stiffness distribution? Is there unwanted movement between components? Does the geometry affect the way force is transmitted? Is the sensation caused by fit, technique or the interaction between several parts of the system?
These are useful questions, and they may never have been asked if the product had remained in the laboratory.
Of course, athletes are not infallible. Exceptional performance doesn't automatically make somebody an expert in materials science, manufacturing or mechanical design. An athlete may correctly identify a problem while proposing a solution that would introduce several new ones. They may prefer a configuration because it suits their technique, even though it would be less appropriate for most other users. Personal preference can also influence feedback, particularly when athletes have spent years adapting to a particular type of equipment.
This is why listening to athletes doesn't mean allowing them to design products by committee. It means taking their experiences seriously while applying engineering judgement to understand what those experiences reveal.
A particularly useful approach is to look for patterns. If one athlete reports an unusual sensation, the observation deserves investigation. If several athletes with different techniques independently describe the same issue, the evidence becomes more compelling. If a problem appears only under certain conditions, those conditions may point toward a design limitation that can be reproduced and measured.
Sometimes the athlete is wrong about the cause but absolutely right that something needs attention.
The best testers are not always the most famous athletes either. A technically demanding competitor can provide valuable performance feedback, but so can an instructor who spends hundreds of hours in the water, a spearfisher who regularly uses equipment around rocky coastlines or a recreational diver who notices a recurring inconvenience that experienced professionals have simply learned to tolerate.
Different users reveal different problems. The important thing is to choose testers according to what you need to learn rather than how impressive their names will look in a marketing campaign.
Because there is a considerable difference between using athletes to validate a design and using athletes to advertise one.
The Problems Nobody Thought To Simulate
One of the most interesting things about real-world testing is how often problems emerge from combinations of perfectly ordinary circumstances. Individually, none of the conditions seems particularly demanding. Together, they create a situation that the original testing programme may never have considered.
Take temperature, for example. Materials can behave differently as temperatures change, and the effect may extend beyond simple strength or stiffness measurements. A component that fits perfectly in a workshop may feel different after spending time in cold water. A material that provides comfortable contact during a short test may become irritating during prolonged use. A connection that functions smoothly when clean and dry may behave differently after repeated exposure to salt, sand and moisture.
None of these possibilities is especially surprising. Engineers understand that environmental conditions influence material behaviour. The difficulty lies in reproducing the enormous number of combinations that occur during actual use.
Equipment is also rarely treated with the consistency that testing procedures assume. It gets packed into bags, transported in vehicles, stored on boats, left in the sun, rinsed imperfectly and occasionally handled by somebody who is more interested in getting into the water than following the manufacturer's ideal maintenance routine.
This is not necessarily misuse. Much of it is simply normal life.
A pair of freediving fins may spend hours inside a protective bag, be carried across uneven ground, placed on the deck of a boat and used repeatedly throughout a training day. They may encounter accidental impacts, changing temperatures and loads that differ considerably from those produced during a controlled bending test. The fins might perform beautifully underwater but reveal a weakness during transport or handling. From the user's perspective, that weakness is still a product problem worth understanding.
A good design needs to account for the environment in which the equipment actually exists, not just the moments when it is performing its primary function.
This is particularly important when several components are designed to work together. Testing an individual part can provide valuable information about its strength and durability, but the complete assembly may behave differently. Loads are transferred between components, small movements can accumulate and the way a person interacts with the system can influence the performance of every part.
With freediving fins, for example, the relationship between the blade and foot pocket matters enormously. A well-designed carbon blade can only deliver its intended performance if the connection allows force to be transferred effectively. At the same time, the foot pocket must fit securely and comfortably enough for the diver to maintain a consistent kicking technique. Improving one characteristic without considering the others can produce a technically impressive component that doesn't work particularly well as part of the complete system.
This is where real-world feedback becomes especially useful. Athletes don't experience isolated components. They experience the entire product, often without knowing which individual part is responsible for what they feel.
And sometimes they reveal problems that have very little to do with structural strength.
Imagine a piece of equipment that requires a complicated adjustment before use. In a workshop, the process takes thirty seconds and works perfectly every time. On a moving boat, with wet hands and several people preparing to enter the water, the same adjustment becomes annoying. Nothing has broken, and the mechanism may be operating exactly as designed. But the product is making the user's life more difficult than necessary.
That matters.
Good product development should investigate not only whether something can withstand demanding conditions, but whether people can use it reliably and comfortably within those conditions. Ease of use, maintenance, consistency and practical handling are all part of performance, even if they don't appear on the most impressive engineering graphs.
There is also a distinction between testing until something breaks and deliberately exposing people to unnecessary risk. For safety-critical equipment, destructive testing belongs in controlled environments where failure can be examined without endangering anyone. Athletes should never be expected to discover structural limits by pushing equipment beyond established safety margins during a dive.
Instead, real-world testing should operate within an appropriate safety framework, using carefully selected prototypes, defined operating limits, inspection procedures and a clear process for reporting concerns. When a problem appears, engineers can investigate it through controlled testing and, where appropriate, deliberately reproduce the failure away from the athlete.
The goal is not to see how much abuse somebody can survive. It's to understand how the product behaves under realistic demands and identify weaknesses before those weaknesses become somebody else's problem.
That approach may be less dramatic than handing a prototype to an athlete and telling them to destroy it, but it's considerably more useful.
And it produces better products.
A Product Is Finished When The Real World Agrees
There is a temptation in product development to treat testing as the final stage of a largely completed process. The design has been approved, the materials have been selected, the manufacturing method is established and the prototype looks exactly as intended. Testing becomes something that confirms the decisions already made.
The problem with that mentality is that it makes unexpected feedback feel like an inconvenience rather than an opportunity.
If an athlete identifies a weakness late in development, the discovery may require changes to tooling, materials, geometry or manufacturing procedures. Those changes can be expensive, and they may delay a launch that people have already spent months preparing. Nobody particularly enjoys hearing that a product needs another round of development when everything appeared to be going according to plan.
But discovering a problem before release is almost always preferable to discovering it after customers have started paying for the product.
There is also a cultural element to this. Companies need to create an environment in which testers feel comfortable being critical. If an athlete believes their role is to support a brand, they may hesitate to describe a product as uncomfortable, inconsistent or disappointing. They may soften their observations because they appreciate the relationship or don't want to seem difficult.
That's understandable, but it undermines the purpose of testing.
The most valuable feedback is often the feedback nobody wanted to hear. A tester who says everything is fantastic may be genuinely enthusiastic, but they haven't necessarily provided much information. Somebody who can explain exactly where a product feels less effective, when the problem occurs and how it compares with other equipment is contributing something much more useful.
Companies should want that kind of criticism, particularly from people who understand the activity well enough to distinguish a genuine design issue from unfamiliarity with a new product.
They should also be willing to discover that their original assumptions were wrong.
Perhaps a feature that looked promising during development provides little practical benefit. Perhaps an apparently minor detail has a much greater influence on comfort than expected. Perhaps the configuration preferred by the engineering team works beautifully for a small group of athletes but creates difficulties for a broader range of users.
These discoveries aren't evidence that the development process has failed. They are evidence that the process is working, provided the company is prepared to act on them.
At Alchemy, the philosophy behind developing high-performance freediving equipment has to account for both sides of this relationship. Carbon construction, blade geometry, manufacturing consistency and component design require technical understanding and controlled evaluation. But those decisions ultimately exist to serve somebody moving through the water. The experience of the diver is not a secondary consideration that can be addressed once the engineering is finished. It is one of the reasons the engineering exists in the first place.
This is particularly relevant when developing equipment for athletes whose demands are exceptionally high. Small differences in fit, responsiveness or control can become significant when somebody is performing repeated deep dives or spending long periods training. Their feedback can reveal details that deserve closer investigation, even when the product appears to satisfy its original technical specifications.
At the same time, the objective should never be to create equipment that works beautifully for one exceptional athlete and nobody else. The challenge is to understand which improvements reflect genuine advances in design and which are simply preferences associated with a particular individual.
That requires testing across different users, conditions and levels of experience. It also requires accepting that no single test, athlete or laboratory measurement can provide a complete picture.
There is a broader lesson here that applies well beyond freediving. The best products are rarely the result of one brilliant idea executed perfectly on the first attempt. They emerge through a process of assumptions being challenged, problems being identified and decisions being revised. The engineer contributes technical understanding. The athlete contributes experience. Manufacturing contributes its own constraints and possibilities. And the final product improves when those perspectives are allowed to influence one another.
Sometimes that means adding something. Often it means removing something that seemed clever but didn't actually help. Occasionally it means starting again because the original approach wasn't as good as everyone hoped.
None of those outcomes is particularly glamorous, and they don't always make interesting marketing stories. A product that works reliably after years of refinement may look almost identical to one that was developed much more quickly. The difference is often hidden in details that customers will never consciously notice.
Perhaps that's how it should be.
Most people don't buy sports equipment because they want to appreciate the complexity of its development process. They buy it because they want to do something they enjoy, and they expect the equipment to help rather than get in the way. They shouldn't need to understand material fatigue, load distribution or manufacturing tolerances to trust that a product has been designed with their needs in mind.
They simply want it to work.
And when equipment performs so naturally that the athlete stops thinking about it, that's often a very good indication that somebody has spent a considerable amount of time thinking about it on their behalf.
Laboratories can tell us whether a product meets the requirements we know how to measure. Athletes can help us discover requirements we didn't know we were missing. Neither approach replaces the other, and the strongest development processes recognise the value of both.
Ultimately, a product shouldn't be considered successful simply because it survived the tests its designers expected it to pass. It should earn that confidence through the conditions, people and unpredictable situations it was actually created for.
That's why you give equipment to people who are capable of exposing its weaknesses. Not because you want them to break it, but because you want to find out what needs improving before anyone else has to.