Field Notes & Essays

Practical observations about nervous‑system patterns, human behaviour, and the small signals that move complex systems.

Getting Better Results from AI

A practical systems lens for clearer interaction

What this intervention addresses

AI has lowered the friction between thought and output. Ideas move faster from mind to material, which can be empowering — but also inefficient when interaction becomes tangled in tone, surface adjustments, or unclear requests.

Many people spend unnecessary energy “fighting the interface” rather than working in the layer where useful thinking actually happens. This leads to more retries, more back-and-forth, and more wasted effort — human and computational.

Core idea

AI interaction can be understood in three practical layers:

Interface — tone, style, perceived personality, and guardrails
Substrate — the technical foundation and limits of the system
Abstraction zone — the working layer where prompts meet the model and useful output emerges

The most effective interaction happens in the abstraction zone — not by overcorrecting the interface, and not by trying to push beyond system limits. Clear, focused prompting reduces friction and allows the system to spend effort on the question itself rather than surface negotiation.

When This Principle is Useful

Key practices

Aim for clarity over control

Focus on the task, constraints, and desired outcome rather than trying to micromanage tone or “personality.”

Work with platform strengths

Different AI systems are tuned differently. Use each where it performs well instead of forcing uniform behavior across tools.

Avoid substrate battles

If something appears to sit outside system limits (policy, capability, or knowledge gaps), redirect the task rather than escalating frustration.

Move toward the abstraction zone

When interaction feels smooth and focused — with less tone negotiation and more substance — you are likely in the productive middle layer.

Refine the question, not just the wording

Better outputs often come from clarifying intent, scope, and success criteria rather than polishing phrasing.

Refine the question, not just the wording

Better outputs often come from clarifying intent, scope, and success criteria rather than polishing phrasing.

Outcome

Related frameworks

Before You Hit Publish

A practical guardrail for people creating frameworks, ideas, and thought leadership with AI

What this intervention addresses

AI dramatically lowers the friction of turning experience into structured, articulate output.
Professionals can now express ideas, frameworks, and perspectives with a clarity and confidence that previously required far more time and editorial support.

This acceleration is empowering — but it also introduces a subtle risk:

Over repeated iterations, the work can begin to incorporate patterns, structures, and intellectual lineages the author did not intentionally set out to use — and may not even recognize.

The result can be unintentional drift in how originality, authorship, or contribution are positioned publicly.

Core idea

AI supports clarity by recognizing patterns in your thinking and helping you express them efficiently.

But AI is also trained on vast bodies of existing theory, frameworks, and intellectual traditions. As your work becomes more coherent, AI may help shape it in ways that increasingly resemble established ideas — often seamlessly and without a clear moment of transition.

Like the Ship of Theseus thought experiment, the change happens plank by plank:
Each iteration improves the work.
No single change feels like a shift in authorship.
But over time, the underlying structure may reflect more than just your lived experience.

The risk is not evolution.
The risk is failing to consciously reposition the work as its lineage becomes clearer.

When This Principle is Useful

This pause is especially valuable when:

you are publishing a new framework, model, or named concept
your work feels unusually coherent, complete, or “crisp” after AI-supported iteration
you are making claims about originality, novelty, or invention
you would feel professionally exposed if someone else identified the intellectual lineage first
your work sits near established fields you have not formally studied

Key practices

Pause before publishing

Low-friction systems reduce natural reflection points. Insert one deliberately.

Stress-test your internal reaction

Ask:
“If someone said, ‘This sounds familiar,’ would I feel curious — or defensive?”

Check embodiment, not just logic

Would you feel grounded explaining this work, its influences, and its limits publicly?

Name lineage early, not defensively

Discovering alignment with existing theory strengthens work. Positioning it clearly preserves credibility.

Choose your authorship boundary consciously

Only you can decide whether the work still feels like “your ship.” Make that call deliberately.

Support others with dignity

If you see someone drifting unknowingly, a gentle question or private conversation protects integrity better than public correction.

Outcome

Related frameworks

Decoding Silence in Change Management

A practical lens for interpreting silence during change.

What this intervention addresses

Silence is one of the most ambiguous responses in change work.
When reactions slow or disappear, it can be tempting to assume the change has landed — especially in fast-moving environments where the next initiative is already forming.

But silence is not neutral.
It is a system response. Its meaning shifts depending on timing, expectations, and what is happening around it.

Misreading silence leads to:
• false confidence
• premature acceleration
• unnecessary escalation
• missed signals of risk

Core idea

When This Principle is Useful

Key practices

Read silence in relation to timing

Early silence often signals sense-making. Mid-phase silence may signal overload or misalignment. Late silence may signal either integration or erosion.

Do not fill silence reflexively

Over-communication or escalation can deepen withdrawal if silence reflects discomfort rather than confusion.

Shift the engagement channel

If people aren’t speaking in large forums, try smaller groups, anonymous inputs, or trusted intermediaries.

Engage frontline managers directly

They often interpret silence locally long before signals reach central teams.

Make silence visible to sponsors

Frame it as system data:
“We’re seeing quiet withdrawal rather than questions.”
This turns silence into a leadership signal, not a delivery problem.

Differentiate post–go-live silence

Silence with smooth performance = integration.
Silence with reappearing old habits = erosion.

Outcome

Related frameworks

The Sustainability of Change

A post-rollout reflection tool for strengthening change capability

Context

After go-live, organizations often run project post-mortems — but the human side of change is rarely examined with the same clarity. Change management overlaps with comms, enablement, and training, so the real levers of adaptation and stability can get lost.

This reflection tool helps change teams and senior sponsors look specifically at how well the organization absorbed disruption and returned to steady performance.

Observation

Intervention / Lens

Use these five prompts after go-live — or mid-rollout — to assess the sustainability of change:

1. Preparedness

Did teams know what was coming, why it mattered, and what was expected?
Were surrounding teams informed early enough to support the transition?
What roadblocks should have been escalated sooner?

2. Frontline Confidence

Did frontline managers feel able to explain the change clearly?
Could they answer basic questions without deferring everything upward?
Were they given simple narrative and materials to cascade?

3. Coordination

Was timing and sequencing realistic, or did initiatives collide?
Were handovers and ownership clear?
Did comms, enablement, and training stay aligned?

4. Integration

After launch, did the organization begin to find rhythm again?
Were issues resolved quickly and consistently?
What helped the system stabilize fastest?

5. Stillness

Did the change become normal — without reminders, rework, or resistance?
Are teams now operating confidently in the new pattern?

Why it matters

When Everything Changes, Some Things Need to Stay the Same

Sometimes the most important change message is what isn’t changing.

Context

Periods of rapid transformation — AI adoption, restructures, mergers, or major operational shifts — create high cognitive and emotional load.

In these moments, leaders often focus communication on what is changing: new tools, new structures, new expectations.

But systems under stress struggle to process change without orientation.

Observation

When uncertainty rises, human systems lose their internal “horizon.”

Without a reference point, people:

brace
stop listening
become protective rather than adaptive

The result is not resistance by intent — but disorientation.

In aviation, losing the visual horizon in turbulence can cause spatial disorientation. Pilots are trained to rely on stable reference instruments to avoid losing control.

Human systems behave similarly.

Core Idea

Leadership Application

Instead of leading with:
“Here’s what’s changing.”

Begin with:
“Here’s what’s staying the same.”

Examples:

At work:
“We are evolving our delivery model and introducing AI tools. What is not changing is our commitment to being our customers’ most trusted partner.”

At home / community:
“Things are shifting, but we are still a family. This is still our home. We still belong.”

This shifts the system from threat scanning to sensemaking.

Why It Works

AI Era Relevance

Related Writing

What Happens Early Matters (M&A)

The Human Multiplier Most M&A Deals Miss

Context

In mergers and acquisitions, financial, legal, and structural integration are prioritized early. Human integration is often delayed until after announcements, org charts, and operational decisions are finalized.

By then, the system is already moving — without shared rhythm, trust, or emotional coherence.

This creates hidden performance drag and value leakage.

Observation

When two organizations combine, it is not just processes merging — it is two human systems with different:

trust maps
rituals
assumptions
communication norms
nervous system patterns

If these systems are not entrained early, people spend energy interpreting uncertainty rather than executing strategy. Misalignment shows up as hesitation, duplication, friction, and slowed decision-making.

The result is not dramatic failure — it is quiet underperformance.

Core Idea

Six Practical Moves (Mid-Flight Integration)

1. Appoint Cross-Legacy Co-Leads

Two respected operators — one from each side — who build visible trust and act as early friction sensors.

2. Build the Communication Channel Early

Name and design the primary question-and-answer pathway before confusion spreads across tools and teams.

3. Start a Living FAQ

A dynamic, visible place where questions land and answers evolve in real time.

4. Facilitate Human Introductions

Create structured space for teams to share how they work, what they value, and their working styles — not just role descriptions.

5. Choose One Symbolic Act

A small, authentic gesture that signals shared identity and psychological inclusion.

6. Address Predictable Pressure Points Early

Name and navigate emotionally charged topics (roles, reporting lines, policies) before speculation fills the gaps.

Why It Matters

Related Writing

Closing Feedback Loops With Dignity

A practical principle for maintaining trust and stability during change.

What this intervention addresses

Every significant change generates questions.
These questions are not resistance — they are attempts by individuals and teams to orient themselves as conditions shift.

Each question opens a feedback loop. How these loops are handled influences whether the system moves toward clarity and trust or toward confusion and disengagement.

Core idea

When this principle is useful

Key practices

Give questions a shared home

Maintain a living FAQ or clarity document where questions reliably land and answers are visible.

Acknowledge before resolving

Stabilize first: confirm the question is received and will be addressed. Emotional regulation precedes informational completeness.

Match loop speed to context

High-sensitivity moments require tight loops and visible follow-through. Lower-intensity phases may allow slower closure without loss of trust.

Meet the system where it operates

Listening sessions or targeted Q&A spaces often resolve patterns more efficiently than scattered responses.

Close loops visibly

When answers emerge, ensure they reach the people who asked. Closure is what builds coherence.

Outcome

Related frameworks

Signal or Noise?

How to tell the difference between emotional release and actionable insight during change

What this addresses

During change, emotion rises. Not all of it requires action — but some of it absolutely does.
This tool helps leaders and change practitioners distinguish between normal emotional processing (“noise”) and meaningful system information (“signal”).

Core idea

When this is useful

Key practices

1. Expect the emotional weather

Denial, resistance, and questioning are normal stages of adjustment.
Acknowledge emotion and close loops gently — but don’t treat every emotional moment as a structural issue.

2. Listen for pattern, not volume

Signal shows up as:

the same concern across multiple groups
concrete examples or operational impact
issues cutting across levels or functions
recurring friction that doesn’t fade

Noise is often loud, personal, or momentary. Signal tends to repeat.

3. Assign someone to read the room

Not every leader can decode emotional data. A change practitioner or trusted team member can:

filter normal turbulence
identify recurring themes
prevent overreaction to the loudest voice

This role protects clarity.

4. Use truth-tellers to validate signal

When unsure, ask trusted internal sensemakers:
“Is this real, or just the moment?”

Their read helps confirm whether something requires action or simple containment.

Outcome

Speed Without Integration Is a Value Leak

A systems principle for the AI era

For over twenty years, my work has focused on what happens after strategy meets reality — when systems are introduced into human environments and must actually be lived with.

Across industries, cultures, and technologies, one pattern appears again and again:

When deployment outpaces integration, value leaks.

Not immediately.
Not dramatically.
But quietly, predictably, and at scale.

This principle now sits at the center of how I see the AI transition.

We are witnessing extraordinary technical acceleration — capability curves rising steeply across model performance, automation, and tool proliferation.

But human systems — organizations, institutions, regulatory bodies, and individual nervous systems — operate on biological and social timelines, not exponential ones.

When the pace of external change exceeds the system’s capacity to metabolize it, the gap doesn’t stay neutral. It accumulates integration debt — the hidden cost of asking humans to absorb more than they can stabilize.

That debt shows up later as:

brittle adoption
support overload
reputational drag
regulatory backlash
cultural fragmentation
product degradation through unresolved edge cases

By the time these effects surface in financial or performance metrics, they are no longer cheap to correct. They are systemic.

This is not an argument against innovation. It is an argument for stabilization as a compounding force.

Integration is not the opposite of speed.
It is what protects speed from eroding its own value.

Why This Matters Here

This principle underpins much of the work on this site.

The SIGNAL Change Framework, AI-era adaptation models, human–AI interaction lenses, and field interventions all point to the same dynamic:

Systems can only move as fast as they can integrate without fragmentation.

When integration is supported:

trust compounds
learning accelerates
adoption deepens
systems remain coherent under pressure

When it is not:

effort increases while results thin out
noise replaces signal
energy shifts from creation to repair

How I Use This Principle

I treat integration not as a “soft” afterthought, but as a design constraint and leverage point.

That means asking:

Has this system stabilized at the current level before we add the next layer?
Are edge cases being surfaced and metabolized, or silently scaling forward?
Is adoption deepening, or only widening?
Is the human system gaining coherence, or quietly bracing?

These questions apply to:

AI deployment
organizational transformation
leadership environments
relational systems
and personal transitions

The context changes. The principle holds.

Field Notes & Essays

Getting Better Results from AI

What this intervention addresses

Core idea

When This Principle is Useful

Key practices

Outcome

Related frameworks

Before You Hit Publish

What this intervention addresses

Core idea

When This Principle is Useful

Key practices

Outcome

Related frameworks

Decoding Silence in Change Management

What this intervention addresses

Core idea

When This Principle is Useful

Key practices

Outcome

Related frameworks

The Sustainability of Change

Context

Observation

Intervention / Lens

Why it matters

When Everything Changes, Some Things Need to Stay the Same

Context

Observation

Core Idea

Leadership Application

Why It Works

AI Era Relevance

Related Writing

What Happens Early Matters (M&A)

Context

Observation

Core Idea

Six Practical Moves (Mid-Flight Integration)

Why It Matters

Related Writing

Closing Feedback Loops With Dignity

What this intervention addresses

Core idea

When this principle is useful

Key practices

Outcome

Related frameworks

Signal or Noise?

What this addresses

Core idea

When this is useful

Key practices

Outcome

Related

Speed Without Integration Is a Value Leak

A systems principle for the AI era

When deployment outpaces integration, value leaks.

Why This Matters Here

How I Use This Principle

In One Line

Attribution Line