The Same Data, Wearing Different Clothes

Imagine walking through a large company.

A CFO is reviewing a sales dashboard. A salesperson is working through a list of prospects. A customer is browsing a website, deciding whether to buy.

These appear to be different activities. Different people. Different tools. Different products.

But there is a good chance they are all interacting with the same data.

We tend to focus on the interface because it is what we can see. The charts. The website. The app. The workflow. Yet the interface is often the least durable thing about it.

Websites are redesigned. Dashboards are rebuilt. Applications are replaced. Every few years, what once felt modern begins to look dated.

The data has a different life expectancy.

A trusted dataset can outlive multiple generations of products. Today's dashboard becomes tomorrow's customer portal. The customer portal becomes an API. The audience changes. The interface changes. The underlying data remains.

Seen this way, many products are not separate products at all. They are different expressions of the same asset.

A product answers a question.

A trusted dataset can answer the next one.

The companies that create lasting advantage are often not those building the most products, but those finding new ways to put the same data to work.

The Unit of Execution

As organisations grow, getting things done often becomes harder, not easier. The problem is rarely a shortage of talent. It is that talented people become separated by reporting lines, functional boundaries, and competing priorities. Work slows as coordination expands. The most effective teams organise around an outcome rather than an

The Data Quality Paradox

Data quality has an unusual characteristic: success removes the evidence of the problem. At first, the issues are obvious. Reports disagree. Fields are empty. Three labels describe the same thing. The defects announce themselves. Then a good team goes to work. Definitions become consistent. Pipelines become reliable. Errors disappear. Complaints

The Cost of Learning Too Slowly

Imagine two companies making the same mistake. The first discovers it after three weeks. The second discovers it after three years. The mistake is identical. Yet one survives and the other may not. Why? Because mistakes have a peculiar property. They grow while nobody is looking at them. A product

Why Masters Ask Different Questions

We tend to think mastery is a function of instruction. Find the best school, the best course, the best teacher, and excellence will follow. But that is not how we learn most things that matter. Nobody becomes a master tailor by studying cloth. Nobody becomes a great manager by reading

Read more

The Unit of Execution

The Data Quality Paradox

The Cost of Learning Too Slowly

Why Masters Ask Different Questions