The Golden Cage and the Empty Pond: On Experience, Location, and the Stories Founders Don't Tell

Diary of an Innovator is a daily journal posting. It is an abridged, sanitised metaphor or reflection on a specific day in the life in innovation land pulled directly from my experiences that day. I write it for my own benefit, but hope it is useful for anyone else who stumbles across it too. With so much happening everywhere and all at once, I find it useful to reflect on each day. I hope you find it useful too in some small way.

A conversation about podcasting turned into a conversation about epistemology, specifically, about what kinds of knowledge can only be acquired by having been somewhere, and why the organisations best placed to learn from that knowledge tend to overlook the people who carry it.

The Myth of the Hub

There's a broadly held assumption in technology and innovation circles that proximity to other innovators accelerates progress. The logic runs something like this: ideas collide, talent clusters, capital follows, and the whole system compounds. Silicon Valley, Berlin, London: the geography of innovation is treated as self-evidently concentrated.

The assumption deserves more scrutiny than it usually gets. Concentration produces certain advantages, density of talent, ease of recruiting, social legitimacy, but it also produces costs that are rarely counted. In a major hub, differentiation is hard. Everyone has access to the same pool of advisors, investors, and press contacts. The signal-to-noise ratio for any individual company is low. What gets through is often the product of connections rather than quality.

In a large hub, you are one of a thousand. In a smaller market, you may be the only one and that singularity opens doors that no amount of product quality would.

A deliberate choice to build outside the major clusters can produce a different kind of advantage: local singularity. When no other player in a region is doing what you do, the landscape changes. Industrial partners who would never return a cold email from a Berlin startup will invite the only digital-native company in their region to participate in strategic forums. The same value proposition, positioned differently, produces an entirely different reception. The question worth asking is not just "where is the best talent?" but "where will our signal be loudest?"

What Experience Is Actually Worth

The startup ecosystem has a persistent and largely unexamined bias toward youth. The reasons for this are partly cultural, partly structural: younger founders are cheaper to fund, easier to romanticise, and fit more cleanly into a narrative about disruption being the province of people unburdened by how things work. The venture capital industry has optimised heavily around this archetype.

The problem with this bias is that it systematically miscalibrates which founders can solve which kinds of problems. For software products aimed at consumers, the case for young founders is reasonable as they often are the users. For applied technology aimed at industrial sectors such as manufacturing, energy, logistics, healthcare, the case collapses. These sectors have peculiar physics. Their decision-making processes are long, their buying centres are complex, their problems are often opaque to outsiders. The only way to understand them from the inside is to have worked inside them.

What experienced founders bring is not just knowledge but credibility earned through shared context. A founder who spent fifteen years inside an industry doesn't need to explain why a problem is hard as the customer already knows they know. This shortens sales cycles, deepens trust, and produces products that fit the actual workflow rather than the imagined version of it.

Experience is not just a repository of facts, it's a set of instincts about which problems are real, which solutions will actually work in practice, and which objections are genuine rather than performative.

The implication for how innovation ecosystems evaluate and support founders is significant. The current filtering mechanisms, pitch competitions, accelerator programmes, venture investment criteria, are optimised for a particular founder archetype that may be the wrong one for a substantial share of the most important problems.

The Incentive Problem in Complex Sales Organisations

One of the persistent challenges in building a sales organisation around a complex, high-value product is the incentive alignment problem. New business and renewals require different skills, different relationships, and different time horizons, but they are often compensated with the same structure, or with a structure that implicitly values one over the other.

The practical consequence is predictable: people optimise for the thing that is more richly rewarded. If new business commissions are substantially higher than renewal commissions, salespeople will chase new logos and treat the existing base as secondary. This is individually rational and collectively destructive, particularly when the renewal base represents a significant share of total revenue and carries structural advantages (shorter sales cycles, established trust, lower customer acquisition cost) that should make it highly efficient to manage.

The design challenge is to build a compensation structure that reflects the actual strategic value of each activity, not just the historical convention. This requires a clear-eyed assessment of what it actually costs to retain a customer versus acquire a new one, and what the business would lose if retention rates fell by a meaningful percentage. That analysis is almost always more sobering than organisations expect.

When Administration Becomes Intelligence

The boundary between administrative work and analytical work is shifting. For most of the history of software platforms the administration,creating organisations, configuring communities, setting up campaigns, was manual, time-consuming, and required trained users to navigate interfaces designed for human comprehension rather than efficiency.

Natural language interfaces are beginning to dissolve that boundary. When an AI assistant can create an organisation with proper enrichment, prevent duplicates, set up a community with contextually appropriate defaults, and scrape a website for branding assets, all from a single conversational instruction, the economics of platform management change substantially. Tasks that previously required dedicated administrator time become ambient background operations.

When administration becomes conversational, the barrier between having a platform and using a platform effectively drops to almost nothing and what was previously a training and adoption problem becomes an engagement problem.

The broader implication is that the value delivered by a complex platform is no longer tightly coupled to the expertise of its administrators. Organisations that previously couldn't afford to staff a dedicated platform manager, or couldn't maintain the institutional knowledge required to operate one effectively, can now participate fully. This is not a marginal efficiency gain, it's a structural change in who the platform serves and how deeply it embeds into their operations.

On Writing as a Thinking Technology

There is a recurring pattern in how people describe the value of journalling, note-taking, and written reflection: they describe it as "therapeutic" or "clarifying," as though the primary benefit were emotional rather than cognitive. This undersells what's actually happening. Writing is a thinking technology, not just a communication medium.

The act of writing forces the imposition of a linear structure on material that exists, in the mind, as a network of loosely associated fragments. That process of linearisation, deciding what comes first, what depends on what, how one thing connects to another, is itself a form of analysis. What feels tangled and circular in the mind becomes, on the page, a problem with a discernible shape and therefore a solvable structure.

For leaders in particular, this matters because the cognitive load of operating at senior levels is disproportionately about managing complexity and ambiguity. Exactly the domains where linear thinking is hardest to sustain without external scaffolding. A daily writing practice doesn't just document what happened; it processes it into a form that can be reflected on, updated, and eventually generalised into something worth sharing.

Thank you for taking the time to read or listen to the Diary of an Innovator, you can find these daily snapshots and more at www.infinite-loop.co.