Give people reasons to believe the company

Here, thought leadership means making an interpretation public that helps decision-makers understand a market problem. Its contribution lies in the distinctions, knowledge and choices it makes examinable. An author’s prominence and publishing frequency do not establish that contribution by themselves.

An executive explaining a market development and a supplier promising a shorter implementation time make different kinds of claim. The first needs to make the reasoning open to scrutiny. The second needs to show under what conditions the promised result is achievable. General market research does not demonstrate the performance of the supplier’s offer.

Choose evidence around the uncertainty that remains. A case can document delivery capability, comparable data can support a trend and a testimonial describes a particular experience. Their value depends on the question they help resolve.

This changes the task of thought leadership. The company needs to offer an explanation grounded in its knowledge: possible choices, overlooked constraints or reasons to prefer one option in a particular setting. Assembling familiar statistics leaves its own contribution unclear.

For someone recommending a supplier, an analysis can provide a first way to assess competence before a meeting. It reveals how the company frames a problem and addresses its difficulties. That judgement needs to be followed by examination of its work: sound reasoning and the ability to deliver an assignment each require evidence.

Experts, projects and company data can provide material that is difficult to find elsewhere. But what the material shows may be narrower than what the company wants to conclude. Data from its customer base describes that customer base before it describes a market.

A case should explain the starting situation, the company’s exact role, the choices made and the results available. When no effect has been measured, an account of implementation can still be useful. It needs to explain a difficulty and how it was addressed, without adding an assumed improvement.

Comparing difficulties across projects, explaining a design choice or the conditions in which a solution fails lets readers assess the company’s experience. An account of success needs to show the constraints and decisions that mattered.

A continuing research programme can also sustain attention to a subject. Microsoft’s Work Trend Index is a public example. The programme’s continuity does not make its editions automatically comparable: each finding retains its question, sample and period. It is discussed here as a published programme, with no claim to have worked on it.

A company knows its own decisions and benefits from presenting them favourably. A client’s outside perspective may confirm an experience without being independent. An expert or certification body provides a different examination whose method, scope and conditions need to be specified. Being external does not by itself establish freedom of judgement.

Certification does not validate every commercial promise. A selected testimonial does not represent all customers. Press coverage does not establish that the journalist verified every result. A third party’s standing should not be used to expand what that party actually confirms.

Make these sources accessible. If the main promise rests only on an internal assertion, establish how it could be verified before distributing it more widely.

For a purchasing decision, I distinguish three questions: did the result occur, could it be repeated in my context, and who will respond if conditions change? A customer case addresses the first; deployment conditions, a trial or a comparison may help with the second; service arrangements and contractual commitments concern the third. More testimonials will not resolve uncertainty about implementation.

A source may establish a fact; the company still needs to explain its implications for the problem. Readers should be able to distinguish data, interpretation and the proposed decision. A series of statistics cannot make that connection for them.

The contribution may be a comparison of options, an overlooked failure condition or a verification method. It becomes useful when someone can apply it to their own choice. That requires visible assumptions and the circumstances in which the recommendation would change.

A documented objection is then something to examine. If it limits the argument, revise the conclusion; if it concerns a different setting, explain the distinction. Credibility depends on sustaining that discussion beyond the initial publication.

A finding can be accurate in a report and become excessive in a sales presentation when a condition disappears. Review the materials using it with the people who understand the result. Keep essential qualifications beside the finding and make the detailed method available in the linked source.

A product, scope or method change should trigger a review of the affected claims. This goes beyond updating a date. Insufficient evidence may require a narrower promise or further work to substantiate it.