Building Something That Lasts
Thomas Mortimer built his career the way most people actually do it, slowly and with a lot of boring mistakes along the way. He wasn't some charismatic startup founder who pivoted five times before lunch. He was someone who understood that real businesses are just collections of small decisions repeated over years. What people often miss about Mortimer's approach is how deliberately unglamorous it was. In the early days, while everyone was chasing the next big thing, he was obsessing over supply chain documentation. I remember reading about a particular incident in 1987 when his warehouse in Leeds had a labeling system failure during a peak season. While competitors were scrambling to manually reconcile orders, Mortimer's team just pulled up the backup manifest and everything was sorted in under two hours. The system had been redundant for three years, something most people wouldn't have bothered with. This wasn't genius. It was just the kind of boring preparation that disappears from business histories because nobody writes about things that work correctly.
How Mortimer Actually Made Decisions
His decision-making framework was straightforward enough that you'd think it was simple. When evaluating new opportunities, Mortimer asked three questions: can we deliver this at scale within eighteen months, do we already own the supplier relationships needed, and will this make our existing business twenty percent more efficient or twenty percent less complex. If the answer to any of those was unclear, he walked away. Most entrepreneurs I know would call this conservative. Mortimer called it survival. The reason his companies lasted while similar ones failed often came down to this filter. I've seen firsthand what happens when you skip it, usually resulting in six-month crises where the initial excitement has completely evaporated and nobody remembers why they started in the first place. Counter-intuitively, Mortimer's biggest wins came from saying no to things that looked perfectly reasonable on paper. In 1991, he turned down a partnership opportunity that would have doubled revenue overnight but required integrating two incompatible inventory systems. The integration would have taken fourteen months minimum. He spent those fourteen months strengthening relationships with existing suppliers instead, which paid off when the market contracted the following year.
The Practical Reality
Managing a business this size required systems that most people find uncomfortable. Mortimer invested heavily in documentation culture, something that never makes it into success stories. His annual reports were famously detailed, including failure rates and near-misses that competitors omitted. The counter-insight here is that Mortimer's legacy isn't really about the companies he built. It's about the framework he left behind, specifically the three-question decision model that has been adopted by at least forty-seven smaller firms across the Midlands. These companies don't get featured in business magazines, but they survive recessions that wipe out flashier competitors. If you're trying to replicate this approach, start with the documentation. Most people skip this step and wonder why their systems fail during critical periods. Mortimer's workaround for the common edge-case where suppliers change terminology mid-contract was surprisingly simple, something I found myself using repeatedly after encountering it in 1995.
Get the Full Details
Where This Approach Breaks Down
Mortimer's method doesn't work in situations where speed matters more than durability. In fast-moving sectors like consumer technology, his eighteen-month timeline becomes a liability rather than a strength. The companies that succeed in those environments often need to move faster than his framework allows, accepting higher failure rates in exchange for quicker market entry. The bottleneck here is that Mortimer's filter eliminates sixty percent of opportunities by design. If you're not willing to accept that trade-off, you'll likely find yourself frustrated with the slow pace. I'd recommend an alternative approach for those contexts, specifically the lean startup methodology that accepts failure as a feature rather than a bug. What made Mortimer different wasn't really his vision. It was his willingness to let boring processes handle the boring problems, something that never gets celebrated but keeps businesses running long after the flashy competitors have moved on to something else.
