DELSOLGROUPLet’s talk
← All perspectives

Leadership & Human Capital

The Story Is Not the Complete Asset - What Marcus Aurelius can teach us about evidence, judgement and intangible-asset management & strategy

A practical approach inspired by Marcus Aurelius to separate strategic narratives from evidence, examine intangible assets and improve leadership decisions without demanding certainty before action.

Dear Readers, Strategists and Game-Changers,

Hope you are doing great!

A patent is granted. The team says: "Our technology is protected."

A customer signs a pilot. The board hears: "The market has validated us."

An AI system produces an impressive report. Someone concludes: "We have captured the expertise."

Each opening statement may describe something real. Each conclusion adds something that still needs to be demonstrated. The distance between those two sentences is where I would begin this week's IP Meditations. Before asking whether a company has enough intellectual property, I would ask whether it understands what its existing assets actually establish.

That is not an argument against ambition. It is an argument against allowing ambition to become evidence.

The judgement we add

In Meditations 8.49, Marcus Aurelius writes: "Say nothing more to thyself than what the first appearances report." His example separates receiving an unfavourable report from deciding that one has therefore suffered harm. The important move is the pause between what has been observed and what the mind adds to it.

He was not writing a manual for IP strategy. The application here is mine: organisations should distinguish an asset, the evidence supporting it and the business story built around it. Those three things can reinforce each other. They should not be allowed to become interchangeable.

Suppose a leadership team believes a proprietary method will make its product difficult to copy. That is a useful strategic hypothesis. But which part is proprietary? What performance difference does it create? What would a competitor have to reproduce? What evidence would show that an alternative route is good enough? Asking these questions does not weaken the hypothesis. It gives it somewhere to stand.

The discipline is especially valuable when the story is attractive. We rarely need help noticing uncertainty in an idea we dislike. We need help noticing it in the idea on which our next investment depends.

Name the thing before praising it

Consider the phrase "we own our technology". It sounds clear until we try to identify its object. Do we mean patent rights, source code, laboratory records, a university licence, manufacturing instructions or access to a supplier's platform? Are we talking about a current product or an architecture still being developed?

Patents are territorial rights. The relevant invention, scope and countries matter; a patent is not a universal entitlement to everything associated with a technological field. That legal precision should shape the management conversation, rather than disappear when the board presentation begins.

I would ask a team to replace its broad statement with a sentence that an engineer, lawyer and commercial director could all examine. For example: "We control the code for this module, hold these patent rights in the relevant territories, and depend on a licensed component for deployment." That sentence is less dramatic. It is also much more useful.

It identifies both the asset and its boundaries. Once the boundaries are visible, management can decide whether to strengthen them, negotiate around them or deliberately accept them. A reassuring label cannot support those decisions because it conceals the very distinctions that matter.

A hypothetical company, and three different truths

Imagine a scientific-instrument company preparing its next funding round. Its researchers have developed a method that improves measurement consistency. The company has filed a patent application, documented part of the process and demonstrated the result to two potential customers.

The pitch says: "Our proprietary platform creates an unassailable advantage." Nothing in this example proves that statement. Equally, nothing proves that the company has no advantage. The sensible position lies between dismissal and certainty.

There is a technical question: under which conditions is the improvement reproducible? There is a control question: which parts can the company use, protect or restrict? There is a commercial question: does the improvement matter sufficiently to change a customer's decision?

A positive answer to one does not automatically answer the others. A reproducible result may be commercially marginal. A commercially valuable result may depend on a third-party component. A protectable feature may be avoidable through a different design. These are alternative possibilities to investigate, not accusations against the founders.

Now imagine the company rewrites its internal narrative: "We have demonstrated an improvement under specified conditions. We are testing its value in the target workflow and assessing how our rights and know-how support differentiation." The company has not become less ambitious. It has become more precise about the work between present evidence and future advantage.

Put a claim through four questions

My proposed discipline is a short review of four things: the observation, its interpretation, the missing evidence and the decision affected. This is a modern management exercise, not a framework attributed to Marcus Aurelius, but inspired by his teaching.

Take "our dataset is a moat". The observation may be that the company possesses a collection of measurements unavailable on its public website. The interpretation is that this collection improves performance in a way competitors cannot readily reproduce. The missing evidence concerns its permitted uses, uniqueness, quality, incremental contribution and replacement difficulty. The decision might be whether to invest in expanding it.

The exercise becomes useful when it leads to a test. Compare performance with and without the dataset. Identify which records contribute something distinctive. Check whether the company has the permissions it needs for the intended use. Ask whether an alternative source could produce an equivalent result.

Do not turn this into a giant register of every uncertainty in the organisation. Select the claims carrying the largest decisions. A ten-minute discussion of one expensive assumption can be more valuable than a beautifully completed spreadsheet of peripheral facts.

Confidence is not a control measure

The same approach applies to confidential knowledge. "Everyone knows this is secret" expresses confidence. It does not tell us what the information is, who may receive it, where it is stored or how its confidential treatment could later be demonstrated.

DELSOL Group's guidance connects trade-secret protection with reasonable measures, including access restrictions, confidentiality commitments and periodic attention to who needs to know. It also explains that protection does not prevent independent development. The label and the protection are therefore not the same thing.

For our hypothetical instrument company, the practical response might be quite modest. Identify the calibration instructions that matter. Record their versions. Define who needs access. Check the relevant agreements. Ensure that the business can still use the method when the original researcher is unavailable.

None of this requires the company to become suspicious of everyone. It requires the company to replace a feeling of control with observable arrangements. Trust and verification are not opposites when verification is proportionate and its purpose is clear.

Correction is a strategic event

Marcus returns to another useful discipline in Meditations 6.21: willingness to change when someone demonstrates that his thinking or action is mistaken. For an organisation, the difficult part is often not finding someone capable of challenging an assumption. It is making the correction operationally possible.

Imagine that the most celebrated patent family no longer maps well to the next product generation. The filing effort may have been entirely reasonable at the time. That does not settle its current role. The decision should concern the future value of maintaining, licensing, adapting or retiring the position, not the need to defend yesterday's judgement.

I would separate respect for the original work from commitment to the original conclusion. A researcher can have done excellent work and still discover that the market needs something else. An IP team can have executed a sound filing plan and still need to revise it when the business changes.

That distinction protects people from being confused with their hypotheses. It also lets the company redirect effort without turning every change of course into a referendum on someone's competence.

Do not replace optimism with permanent suspicion

There is a bad version of this article: demand complete proof before doing anything. That would make strategy impossible. Companies must act before all uncertainty disappears, particularly when they are developing unfamiliar technologies or entering emerging markets.

The aim is not certainty. It is calibrated commitment. A reversible experiment can proceed on less evidence than a broad exclusive licence, an irreversible disclosure or a major acquisition. The level of confidence should be proportionate to what the decision puts at risk and how easily it can be corrected.

In practice, I would pair a decision with its review condition: We will proceed with this application while the customer need remains relevant. We will expand this dataset if the next evaluation shows incremental value. We will depend on this supplier while a specified continuity condition remains credible.

Those statements allow action without pretending uncertainty has vanished. They also give future colleagues permission to revisit the decision, rather than treating an old approval as an instruction that must last forever.

A boardroom exercise for this week

At the next leadership meeting, choose one sentence that appears frequently in your strategy discussions. Perhaps it is "our IP is strong", "our experts are irreplaceable" or "our AI system captures our knowledge". Ask everyone to write, privately, the evidence they believe supports it.

Then compare the answers: Are people referring to the same asset? Do they mean the same use, territory, product version or time horizon? Which conclusions are supported directly, and which depend on another assumption? Agreement on the slogan can conceal disagreement about almost everything underneath it.

End with one action, one owner and one date. Not a general instruction to improve governance. A concrete step: test the replacement route, verify the licence scope, document the method, review the claim coverage or challenge the performance baseline.

The most valuable outcome may be a more defensible version of the original sentence. It might also be the discovery that the company's real strength lies somewhere else. Either is progress, because management is now directing attention towards something it can examine and develop.

For example, "our experts are irreplaceable" might become "two people currently perform the final diagnostic step; we will document the decision criteria and test whether a trained colleague can apply them". The revised sentence respects the experts while making continuity a management responsibility. It does not pretend that writing a document transfers all their judgement.

Likewise, "our AI captures our knowledge" could become "the system retrieves approved documents accurately on these evaluated questions; we have not yet tested its handling of contradictory records". That is a much stronger basis for deciding where the system may be used, what a reviewer must check and which capability deserves further investment.

The asset beneath the story

In intangible-asset strategy, an attractive narrative can draw attention to something valuable. It cannot substitute for the rights, knowledge, relationships or capabilities that make the narrative true. My preference is not to remove the story, but to give it an evidence trail. Stories backed by evidence are the most impactful!

That is the lesson I take from returning to Marcus Aurelius this week. Before reacting to an apparent threat or celebrating an apparent advantage, examine the judgement being added. Before protecting an asset, identify it. Before relying on a position, understand its boundaries. Before defending a conclusion, remain willing to improve it.

The question is not whether your company can tell a compelling story about its invisible value.

It is whether the company underneath that story can carry the weight you are placing on it.

Back to all perspectives