The Cartographer's Errant Peninsula and the Power of a Single Revision
I’ve been thinking a lot about revisions lately. Not the endless, soul-sapping tweaks of a document that is already 90% complete, but the large, decisive, course-correcting stroke. The kind of edit that requires the courage to admit a foundational error and the clarity to see the one change that will fundamentally set things right. For this, my mind turned to the old mapmakers, and to a singular feature on a 15th-century chart of the African coast.
The Portuguese, under Prince Henry the Navigator, were meticulously mapping the west coast of Africa, a slow and terrifying process of sailing into the "Sea of Darkness." For years, their maps showed a large, speculative peninsula jutting far to the east, a cartographic ghost known as the "Dragon’s Tail." This wasn't just a mistake; it was a deeply held geographical belief, a comforting fiction that suggested Africa could be easily circumvented. It represented the limit of known work, the edge of the real, and it sat on their charts for decades.
Then, in 1488, Bartolomeu Dias actually rounded the Cape of Good Hope. He didn’t find a peninsula; he found a cape, and beyond it, an open ocean leading to India. The old map was not just inaccurate; its core premise was wrong. The entire geometry of the known world had to shift.
What interests me is the moment the new information landed on a cartographer’s desk. He didn’t just add a few notes in the margin. He didn’t create a complex overlay of possibilities. He took his pen, and with one sweeping, definitive action, he erased the entire Dragon’s Tail. He scraped the vellum clean of that colossal error. In its place, he drew the true, sharp southern tip of the continent. One revision. One massive, clarifying deletion that made all subsequent work not only possible but accurate.
The Map of Our Work
We all have Dragon’s Tails in our projects. They are the assumptions we’ve been sailing by for weeks or months: a foundational feature in a piece of software that is elegantly built but ultimately misguided; a chapter in a book that we love but that derails the entire narrative; a core process in our workflow that we tolerate because it’s “the way we’ve always done it.” These peninsulas are comfortable. They fill the empty space on our mental maps. To remove them feels like admitting we’ve wasted time sailing in the wrong direction.
But the cartographer’s lesson is that true progress isn’t about adding more detail to a flawed foundation. It’s about the bravery to make the single, structural revision. It’s the power of asking: "What is the one thing I am convinced is true, that might be completely wrong?" And then being willing to scrape it away.
This isn’t about constant pivoting or indecisiveness. It’s the opposite. It is the decisive act that comes from genuine discovery. The old map was a hypothesis; Dias’s voyage was the experiment. The result demanded a fundamental redrafting. Our work is no different. When we finally get the data, when we truly understand the user’s need, when we see the flaw in our logic, the most productive thing we can do is not to patch and mend, but to make the single, sweeping correction. It clears the chart for the real journey ahead.
Notes & further reading
A few pages I came back to while writing this: