TBT — The Business TherapistTBTThe Business Therapist
Explore knowledge

CONCEPT · INTRODUCTION

A symptom is not always the root cause

What we notice provides a starting point for examination, not proof of a cause.

Why it matters

Jumping from a visible indicator to a solution may direct effort away from decisive factors that have not yet been examined.

Understanding the idea

A symptom is something observed: falling sales, late delivery, cash pressure, or changing customer behaviour. Interpretation requires context and evidence.

Pricing, positioning, operations, capability, and market conditions may interact. Multiple possibilities are not multiple proven causes; they are a reason to distinguish what is known from what is assumed.

We preserve the client’s original account separately from classifications, structured signals, and professional interpretation. Evidence may change the initial hypothesis.

In practice

Fictional illustration: enquiries may rise after an advertising campaign while completed orders fall because delivery is delayed. Fulfilment deserves examination here; the illustration does not establish the cause in another business.

Basis and limitations

A TBT architecture principle separates visitor-reported experience from professional interpretation. The example is fictional, not a client case or published research finding.

These are illustrative possibilities, not confirmed causes or a self-diagnosis tool. One indicator does not establish a root cause.

About this knowledge page
Editorial owner
TBT — The Business Therapist
Content status
Conceptual introduction — no empirical validation claimed
Page edition
1.2
Editorial review date
Wording approval date

References and source sections

These references identify the basis of the wording and the relevant source sections. Citation alone does not establish empirical effectiveness of a method or intervention.

  1. TBT Master Architecture v1.0 — Approved Baseline (30 September 2026)
    §7: DIAGNOSE and visitor experience versus professional interpretation

  2. TBT Level 3 Experience Information Architecture — Approved Baseline (17 October 2026)
    §6 WORK: Raw Narrative / Self-Reported Structure / System-Structured Signals / Professional Interpretation

What changed?

This concise page history begins with edition 1.1. A page edition does not indicate a new version of the method or intellectual system.

  1. Edition 1.1 ·

    Published the approved introduction with its conceptual basis and limitations.

  2. Edition 1.2 ·

    Aligned the page edition with the other knowledge introductions; this page’s text was unchanged.

Connected thinking

What would be useful next?

Continue exploring, discover learning, or discuss how the idea relates to your business. Reading an idea alone does not diagnose a situation.