The Product May Change. The Way of Reading Change Should Remain.

Inspired by a recent interview with SuperbCrew.

Most companies are trained to think in terms of products.

What should we build?
What should we launch?
Which market should we enter?
Which technology should we adopt?

These are important questions.

But I have become increasingly interested in an earlier question:

How do we notice what should become a product in the first place?

That question led me to build the Kosuke Protocol.

Not as a consultancy.

Not as a single AI product.

Not as a fixed methodology for one market.

But as a protocol for reading change.

Why a Protocol?

A product is a form.

A consultancy is a form.

A report is a form.

A simulation is a form.

A business proposal is a form.

But before any of those forms exist, something usually happens first.

A fragment appears.

It may be a small behavioral shift.

A new regulation.

A change in language.

An unexpected market signal.

A technological anomaly.

A new kind of fatigue.

A strange pattern in how people use a system.

A change in how people trust, work, move, buy, remember, or decide.

Individually, these fragments may appear too weak to matter.

But they are often where change begins.

The Kosuke Protocol starts there.

Fragment → Observation → Connection → Meaning → Form

The sequence matters.

We do not begin by deciding what the final product should be.

We begin by observing what is already changing.

Then we connect those observations across domains.

Only after that do we ask what they might mean.

And only then do we decide what form that meaning should take.

This is why I prefer the word protocol.

A protocol does not prescribe one output.

It defines how something can move.

The Problem With Starting From Categories

Organizations usually operate through categories.

Marketing.

Finance.

Technology.

Climate.

Security.

Human resources.

Risk.

Culture.

Markets.

These categories are useful.

But change rarely respects them.

A climate signal can become a labor issue.

A labor issue can become a productivity issue.

A productivity issue can become an automation decision.

An automation decision can become a capital investment.

A change in AI capability can become a market-structure issue.

A change in identity can become a question of trust, memory, or institutional design.

The signal often begins in one place and becomes important somewhere else.

If we only observe within predefined categories, we may detect the change too late.

This is one reason SHIRO & Co. operates through an Observatory Network rather than a single research vertical.

The point is not to create many separate observatories.

The point is to allow observations to travel.

Observations Should Move

This is becoming one of the most important ideas in our work.

An observation should not remain where it was first discovered.

It should be able to move.

A climate observation may move into labor design.

A market observation may move into organizational strategy.

A security signal may move into procurement.

A cultural shift may move into product design.

An observation about digital identity may move into questions of memory, authorship, and institutional continuity.

This movement is where meaning begins to accumulate.

The enduring asset is not any single observation.

It is the system that allows observations to travel across domains and accumulate into meaning.

That is much harder to replicate simply by adding another AI model, another dashboard, or another research team.

AI Makes This More Important, Not Less

AI dramatically increases the amount of information organizations can process.

It can summarize.

Compare.

Classify.

Generate.

Simulate.

Search.

Recommend.

This is powerful.

But it also creates a new risk.

If many organizations use similar models, similar datasets, similar workflows, and similar analytical methods, they may gradually converge on similar interpretations of the world.

The problem is no longer only access to intelligence.

The problem becomes differentiation of interpretation.

What does your organization notice that others do not?

What relationships does it see that others fail to connect?

What does it consider meaningful?

What does it ignore?

What does it act on?

These questions are becoming more important as AI becomes more widely available.

I believe the next source of competitive advantage will not simply be better AI.

It will be a distinctive way of observing and interpreting change.

A Simple Example: Climate and Usable Human Time

One concrete example comes from our Climate Observatory.

Extreme heat is usually discussed through temperature.

How hot was it?

How many days exceeded a threshold?

How much warmer was this year than last year?

Those are valid measurements.

But for an organization, another question may matter more:

How many hours were actually usable?

In one case we examined in Kochi, Japan, extreme-heat measures effectively remove roughly two hours from a conventional eight-hour working day.

That changes the question.

Not:

How hot is it?

But:

What happens to productivity, project schedules, labor systems, and regional competitiveness when usable time contracts?

This is a small example, but it shows how the Protocol works.

An observable fragment is reinterpreted through a different lens.

That interpretation is connected to other systems.

A previously invisible business consequence becomes measurable.

The value is not in collecting more signals.

The value is in finding a connection that changes a decision.

From Signal to System

This is also why I do not think of the Kosuke Protocol as a trend-reporting framework.

Trend reports tend to stop at recognition.

Something is changing.

Something is growing.

Something is declining.

Something is emerging.

Useful, but incomplete.

The question for us is:

What can this become?

A detected signal might become:

• an Observatory
• a simulation
• a business hypothesis
• a proposal
• a new decision system
• a software application
• a narrative
• a new market definition
• a new operational model

The final form depends on what the observation requires.

This is why the final stage is simply:

Form

Not “Product.”

Not “Consulting.”

Not “Report.”

Form remains open.

Why This Matters for Organizations

Most organizations do not lack information.

They are surrounded by it.

Reports.

Dashboards.

Feeds.

Market data.

AI summaries.

Competitor intelligence.

Internal documents.

Customer feedback.

What they often lack is a coherent way to decide:

What matters?

What connects?

What is changing beneath the surface?

Which signals are weak but consequential?

Which changes belong together even though they sit in different departments or industries?

And what should we do with what we have observed?

This is where I think a protocol becomes more useful than another information source.

A protocol can become an organizational capability.

Not something you consume once.

Something you use repeatedly.

Something that helps an organization develop its own way of reading change.

Private Protocol

This is the direction we are now exploring more seriously.

Every organization has its own history.

Its own customers.

Its own language.

Its own constraints.

Its own accumulated knowledge.

Its own blind spots.

Its own risk tolerance.

Its own definition of what matters.

A generic intelligence system does not automatically understand those things.

A Private Protocol would incorporate them.

The purpose is not to create a private chatbot.

It is to create a company-specific way of observing, connecting, interpreting, and acting on change.

Over time, that could become a lasting capability.

The product may change.

The market may change.

The AI model may change.

The organizational structure may change.

But the organization’s way of reading change should become stronger.

The Product Is Not the Enduring Asset

This is the distinction I keep returning to.

Products are temporary.

Interfaces change.

Technologies are replaced.

Markets reorganize.

Business models evolve.

What matters more is the system that continues to notice what is changing and decide what those changes mean.

That is why I built a protocol rather than a single product.

The product may change.

The way of reading change should remain.

And perhaps, over time, that way of reading change becomes one of the most durable capabilities an organization can own.