CLN Wiki · Article 10

Analyzing Complex Systems with MDA

Seeing the invisible: First-order vs Third-order effects

@target: Analysts / Researchers

Why Linear Thinking Fails

Most analysis stops at first-order effects. You raise the price — revenue goes up. But second-order? Customers churn. Third-order? Competitors capture your former customers and build a larger base. By the time you see it, the damage is systemic.

CLN's ^mda (Multi-Dimensional Analysis) template forces you to think in cascading layers. It's not optional depth — it's structural depth, built into the notation itself.

The MDA Template

MDA organizes analysis into four orders of effect. Each order has its own section separator, making it impossible to confuse immediate causes with systemic consequences.

MDA: Price Increase Impact — depth 3

    —— ORDER 1: FIRST-ORDER (what is it?) ——

    . Dimension: Revenue
        = 15% price increase on core product
        + immediate revenue bump: +$2.4M/quarter
        @metric: ARPU increases from $89 to $102

    . Dimension: Customer Sentiment
        = price-sensitive segment (38% of base) will react
        ! NPS expected drop: 12-18 points
        @signal: support ticket volume

    —— ORDER 2: SECOND-ORDER (what follows?) ——

    . Effect: Churn acceleration in SMB segment
        * historical pattern: 2019 increase led to 8% churn spike
        @action: prepare retention offers for at-risk accounts

    . Effect: Competitor opportunity window
        * CompetitorX already 20% cheaper — now 35% cheaper
        ! their sales team will use this in every pitch

    —— ORDER 3: CASCADING (where does it lead?) ——

    . Cascade: Market share erosion in mid-market
        = lost customers become competitor references
        @strategy: lock in annual contracts before announcement
        ? can we offer grandfathered pricing to top 50 accounts?

Why This Works

Notice what happens when you scan the left column alone. The ! operators jump out — two risks, immediately visible. The @action and @strategy lines give you the response plan without re-reading the analysis. The order separators create cognitive "floors" that prevent you from mixing up causes and consequences.

When to Use MDA

MDA isn't for every question. Use it when the system is complex enough that first-order analysis would be misleading. Some typical use cases: pricing decisions, organizational restructuring, technology migrations, regulatory impact assessment, competitive strategy shifts.

Depth Selection

Depth 1: Simple review — "what is it?" only. Good for status reports.

Depth 2: Standard analysis — adds "what follows?". Most business decisions.

Depth 3: Strategic analysis — adds cascading effects. High-stakes decisions.

Depth 4: Foresight — reveals fundamental truths. Rare, but transformative.

From Analysis to Action

The power of MDA is that it doesn't just reveal the problem — it embeds the response. Every @action and @strategy line is a task you can extract directly. Every ? line is a research item for your team. The analysis is the action plan.

First-order thinkers react to events. Third-order thinkers shape the conditions that determine events. — Systems thinking principle

Start Thinking in CLN

Nine symbols. Four spaces. Infinite clarity.

Read the Spec All Articles