The Beach That Became a Shipyard: Building in Africa, For Africa and the World

In 1971, a Korean businessman walked into a British bank and asked for money to build ships. The bank asked a reasonable question: where is your shipyard? He did not have one. He had a photograph of an empty beach.

He also had a 500 won note in his pocket, which carried a picture of a turtle ship, an ironclad warship Korea had built in the 1590s. He put it on the table and said, more or less, we were building ironclads while you were still figuring out wooden hulls, we just took a few centuries off.

He got the loan. That man was Chung Ju-yung, the beach became Hyundai Heavy Industries, and within a decade Korea was one of the largest shipbuilders on earth.

I love this story, and not for the hustle. I love it because he was not selling a ship. He was selling the claim that his people could learn to build one. That is the whole argument of this piece.

We have become very good at buying answers

Here is a scene you have witnessed, whatever industry you are in.

A machine stops. Nobody in the building can open it. There is a service contract, so someone files a ticket, and a specialist is flown in from somewhere with better weather. He arrives, opens a laptop, changes a setting, closes the laptop, and leaves. The invoice has four zeroes. Three local engineers stood there and watched, and learned exactly nothing, because the diagnostic software is licensed and the manual is "proprietary."

We call this maintenance. It is closer to rent.

Africa is home to about 18 percent of the world's people and produces roughly 2 percent of the world's manufacturing output. That gap is not a talent gap. I have met the engineers. It is a capability gap, and capability is not something you can order.

The recipe problem

Think about the difference between having a recipe and knowing how to cook.

With a recipe you can make one dish, once, if you have every ingredient listed. Take away the buttermilk and you are stuck, standing in your kitchen googling "buttermilk substitute" like the rest of us.

Someone who can actually cook shrugs, adds lemon to milk, and carries on. They are not following the recipe. They understand what the buttermilk was doing.

Now scale that up. Most of our industrial base is running on recipes. Excellent recipes, expensively acquired, but recipes. So when the grid browns out twice a day, when the harmattan puts dust where the designer assumed clean air, when the diesel price doubles in a quarter, when the sensor is discontinued, the recipe fails and there is nobody in the room who knows what the buttermilk was for.

A recipe gives you one dinner. Knowing how to cook gives you every dinner, including the ones nobody has written down yet.

Sovereign does not mean building everything yourself

Whenever someone says sovereign, half the room hears "make everything locally, import nothing," and quite reasonably decides this person has lost it.

That is not the claim. Nobody makes everything. Not Germany, not Japan, not the United States, and certainly not us.

Sovereignty is a much smaller and much sharper thing. It is the ability to solve your problem without asking permission.

Buy the sensor. Please, buy the sensor. But if that supplier disappears on Monday, you need a Tuesday answer. Can you specify it, test it, repair it, or swap it for something else? If yes, you are sovereign in that domain and you happen to be importing. If no, you do not have a supply chain, you have a landlord.

Four countries that climbed the ladder, and what it cost them

Korea. In the early 1960s, Korea was poorer than Ghana. Today it spends around 4 to 5 percent of GDP on research and development, one of the highest rates anywhere. Samsung, before the phones, was a trading company dealing in dried fish, vegetables and noodles. Nobody was born a chipmaker.

Taiwan. A government research institute, ITRI, spent the 1970s and 80s deliberately absorbing semiconductor process knowledge and pushing engineers out into companies. One of those spinoffs, founded in 1987, was TSMC. Taiwan now makes the overwhelming majority of the world's most advanced chips, which is why an island of 23 million people is a permanent item on every geopolitical agenda on earth.

Japan. Toyota was a loom company. Their famous principle of a machine that stops itself when something goes wrong came from an automatic loom, decades before it was ever applied to a car. They did not import the philosophy. They derived it on their own factory floor, from their own broken thread.

India. In 2014, India put a probe into Mars orbit for roughly 74 million dollars. The film Gravity, which is about being in space, cost more than 100 million dollars to make. India reached actual Mars for less than Hollywood spent pretending to. They did it by being ruthless about first principles, using a smaller rocket and a longer, cleverer orbital slingshot instead of brute force.

Notice what none of these are. None of them are a country that bought its way to capability. Every one is a country that decided to be bad at something in public for about fifteen years until it got good.

The ladder itself

Capability is not a switch you flip. It is a ladder, and there are no helicopters to the top.

• Operate. You can run it. Most organisations stop here and put it on a slide as competence.
• Maintain. You can fix it, which means you know why it works, not just which button glows.
• Adapt. You can modify it for conditions its designer never imagined. Local advantage starts here.
• Design. You can specify and build the next one, starting from your constraints, not someone else's.
• Tool. You can build the machines that build the machines. Nobody puts this on a billboard. It is the rung that compounds.

Every shortcut on offer, and there are many, quietly keeps you on rung one while producing a very nice ribbon cutting photo.

Our constraints are a specification, not a handicap

This is the commercial argument, and I think it is the one we undersell.

Roughly 600 million people on this continent live without reliable electricity. Cost sensitivity here is not a preference, it is physics. Dust, heat, humidity, thin bandwidth, repair culture instead of replacement culture, distribution through people rather than infrastructure.

Engineer something to survive all that and you have not built a lesser product. You have built a harder one. Robust, cheap to run, easy to fix. That product travels anywhere. The reverse is not true: a thing built for perfect conditions works only where conditions are already perfect, which is a shrinking market.

Two proofs, both African.

M-Pesa. Kenya did not build mobile money because it was ahead on fintech theory. It built it because card infrastructure was thin and everyone had a basic phone. The value moving through it grew to something on the order of half of Kenya's GDP. The rest of the world then spent a decade studying it. Nobody pitied us into that.

Zipline. Drone delivery of blood and medicine got serious in Rwanda, because the roads and the terrain made it the sensible answer rather than a novelty. Having been hardened on hills and rain and real clinical urgency, the same system is now flying deliveries in the United States. Built here first, exported after. That is the direction of travel we want.

Four things you can start on Monday

None of these need a policy change, a grant, or anyone's permission.

Train problem setters, not just problem solvers. Our schools are excellent at handing students a tidy question. Reality never arrives tidy. The rare skill is looking at a mess and deciding what the question actually is, and it is only learned on real broken things with someone experienced asking why.

Write your own specification. Even when you are buying. Whoever writes the spec controls the system. Accept the vendor's spec and you have outsourced your strategy to a sales team who has never seen your site.

Document like you plan to leave. Capability that lives in one person's head is not capability, it is a hostage situation with a salary. Write the drawing. Log the failure. Record the decision and, more importantly, why.

Teach what you learn. Solve a problem quietly and you have helped one company. Publish the method and you have moved an ecosystem, and you will understand it better yourself, because explaining is where you find the holes.

The beach is the point

Chung Ju-yung did not have a shipyard. He had a beach, an old banknote, and an argument that his people could learn.

We have a great deal more than a beach. What we have not fully decided is whether we are willing to be visibly, publicly mediocre at something difficult for long enough to become genuinely good at it. Because that is the actual price, and it is the only currency this particular thing is sold in.

Nobody is going to hand us the capability to solve our own problems. Honestly, why would they. It is ours to build, and the first step is refusing to accept a black box.

Open the casing. Ask why until you hit something that is actually true. Then build up from there.