Article

Five Questions Your System Should Be Able to Answer

If your system cannot answer these five questions, your business may be relying on memory instead of operational continuity.

June 17, 2026

A business does not need to document everything to become more coherent.

But it does need to know what matters.

The problem is that many teams cannot tell the difference between having information and having an operating system that can use that information.

They have the notes. They have the files. They have the tools. They have the recordings. They have the project boards. They have the AI summaries.

But when the work gets complex, the same questions return:

  • What did we decide?
  • Why did we decide it?
  • Which version is current?
  • What does this affect?
  • Who has the authority to change it?

If those questions cannot be answered quickly and reliably, the system is not carrying enough meaning.

That is where Decision Drift takes hold.

The Five Questions

The first step is not a new tool.

The first step is diagnosis.

A useful system should be able to answer five basic questions.

1. What do we already know?

This sounds simple. It usually is not.

Most businesses know more than their systems can show.

The knowledge may be distributed across meetings, documents, conversations, folders, individual memory, and partially implemented tools.

If the system cannot surface what is already known, the business will keep rediscovering its own context.

That creates wasted effort and weakens confidence.

The diagnostic issue is not whether the information exists. It is whether the system can retrieve it in a usable form.

2. What have we already decided?

A decision that cannot be found will be remade.

A decision that can be found without context will be challenged or misused.

A decision that has no owner will drift.

A decision that has no status will become ambiguous.

The system should be able to distinguish:

  • proposed decisions,
  • active decisions,
  • rejected options,
  • outdated decisions,
  • decisions requiring review,
  • decisions with unresolved dependencies.

Without that distinction, the business may appear aligned while old decisions quietly lose force.

3. What is current?

This is one of the most important operational questions.

Many systems accumulate versions without making currentness visible.

There may be three versions of a strategy, four versions of an offer page, multiple onboarding flows, and several different explanations of the same concept.

If the system cannot identify what is current, people will use what is familiar, visible, or easiest to find.

That is not governance. That is convenience.

And convenience often creates drift.

4. What does this affect?

Meaningful work has relationships.

A decision may affect an offer. An offer may affect a checkout page. A checkout page may affect onboarding. Onboarding may affect client expectations. Client expectations may affect delivery. Delivery may affect proof and positioning.

If the system cannot see relationships, changes become risky.

People update one thing without knowing what else should change.

The result is fragmentation: the business says one thing in one place and something else somewhere else.

A coherent system needs relationship visibility.

5. What requires human judgment?

This question becomes more important as AI enters the operating system.

Not everything should be automated. Not everything should be delegated. Not everything should be inferred.

Some things require human judgment because they involve authority, risk, exposure, ethics, client trust, commercial claims, or strategic direction.

A useful system should make those boundaries visible.

AI can help summarize, compare, draft, and detect inconsistencies. But it should not silently decide what is true, what is approved, what is safe to publish, or what a business now stands for.

Those are authority questions.

What the Answers Reveal

If your system can answer these five questions, it has the beginning of operational continuity.

If it cannot, the issue is not just organization.

The issue is that meaning is not yet structured enough to survive movement across people, tools, time, and AI-supported work.

That does not mean the business is broken.

It means the business has reached the point where memory, folders, and informal alignment are no longer enough.

From Diagnosis to Design

The purpose of these questions is not to create shame or complexity.

The purpose is to show where the operating system needs to become more intelligent.

A better system does not require everyone to remember everything. It does not require every decision to be re-explained. It does not require AI to guess what is authoritative. It does not require the founder to carry the full context alone.

It creates enough structure for meaning to move without becoming distorted.

Closing

Decision Drift becomes visible when your system cannot answer basic questions about its own knowledge, decisions, current state, relationships, and authority boundaries.

That is the diagnostic.

The next step is not to add more content.

The next step is to ask what your system actually knows and whether that knowledge is structured well enough to guide what happens next.

This Series: What Your System Actually Knows

This is article 5 of 5.

Previous: AI Amplifies Gaps When Meaning Is Unstructured

Start from the beginning: Your System Cannot Use What It Never Captured

View the full series

Diagnostic

Where does your system stand?

21 questions. 5 minutes. No email required. A quiet mirror for leaders who carry consequences.

Take the Explicitness Test

KEEP READING

More from Decision Drift