The Hidden Systemics of Useless Information

In this episode of Little Fish, the hosts explain that seemingly trivial facts, from the chromosome count of humans to the design of soccer balls, are rarely isolated data points. They are entry points into complex feedback loops where technical choices, historical accidents, and human incentives collide. A recurring pattern emerges: attempts to solve a problem often introduce new, hidden variables that fundamentally change how a system behaves. For the reader, this analysis provides a tactical advantage in recognizing how obvious solutions in software architecture, logistics, or project management frequently trigger downstream complications that are ignored during planning. Understanding these systemic ripples allows practitioners to anticipate failure modes before they become operational nightmares.

The Hidden Cost of Optimal Design

We often treat design as a linear path from problem to solution. The hosts discuss World Cup soccer balls, which contain chips to track movement, to reveal how a smart addition creates a ripple effect in physics. The ball’s new panel design, intended to improve accuracy, inadvertently triggers a drag crisis at specific speeds, causing the ball to behave unpredictably.

Basically, at a certain speed, it undergoes drag crisis and it moves faster, it speeds up and it is because the air around it goes into a turbulent state and that disrupts the drag on the ball.

-- James Harkin

The lesson here is systemic: adding a technical layer to solve a measurement problem altered the fundamental performance of the object itself. In any system, you cannot change one variable in isolation. When you introduce a fix, you must map how that fix changes the environment in which the system operates. If your solution solves the immediate problem but introduces new, volatile behavior, you have not improved the system. You have simply shifted the burden of failure.

Why the Obvious Fix Makes Things Worse

The hosts discuss the rational approach to jigsaw puzzle manufacturing, which highlights the friction between mathematical reality and standardized infrastructure. Because standard puzzle boxes are A4 sized, manufacturers must produce puzzles with 1,026 pieces rather than exactly 1,000 to maintain the correct aspect ratio.

This is a case of infrastructure dictating output. The obvious solution of making a 1,000 piece puzzle is rendered impossible by the constraints of the packaging system. When teams attempt to force a clean solution into a dirty system, they often create hidden complexities, such as the need for non-standardized boxes or specialized production lines. The takeaway for the practitioner is clear: before you propose the ideal solution, audit the existing infrastructure constraints. If the infrastructure cannot support the ideal, you are not just failing to reach the goal. You are creating a legacy of inefficiency that will compound every time you repeat the process.

The 18-Month Payoff: When Discomfort Creates a Moat

The conversation touches on the D-Day landing preparations, where the Allies used condoms to collect soil samples from Normandy beaches. This is an example of using unconventional tools to solve a high-stakes information problem. The immediate discomfort, the absurdity of using prophylactics for intelligence gathering, was a necessary trade-off for the strategic advantage it provided.

As part of the preparation for the D-Day landings, the Allies used condoms to collect soil and sand from the Normandy beaches.

-- Andrew Hunter Murray

Most systems fail because participants are unwilling to engage in the absurd work required to gather accurate data. The Allies did not look for a standard way to sample sand; they looked for the most effective way, regardless of how it looked. In a professional context, the most durable competitive advantages are often found in the tasks others find too strange, tedious, or embarrassing to perform. If your competitors are avoiding a method because it feels unprofessional or non-standard, that is exactly where your opportunity for a structural advantage lies.

Key Action Items

• Audit your Smart Additions: Over the next quarter, review any recent technical or process upgrades. Ask: What secondary behavior did this introduce? If you see erratic performance, you may be experiencing a drag crisis of your own making.
• Map the Infrastructure Constraint: Before proposing a new project, identify the A4 box, the rigid infrastructure that will force your solution to become sub-optimal. If you cannot change the infrastructure, stop trying to force the ideal solution.
• Seek the Absurd Data Point: Identify one critical piece of information your team lacks. Spend the next 12 to 18 months finding an unconventional, low-cost way to collect it, even if it feels unprofessional. The discomfort is the barrier to entry for your competition.
• Identify Systemic Overrides: Look for processes that have buckled under long-standing usage despite official rejection, like the Another Lake naming example. Document these. They are often your most resilient, yet most confusing, operational patterns.
• Challenge the Obvious Naming: When you see a process named after a person or a gift, like the Greek Gift in chess, verify the origin. Understanding the history of your tools prevents you from misapplying them based on a misunderstanding of their original purpose.