Field Notes  |  Roe & Associates

The system is already telling the truth.

Not through intention. Not through what people say they value. Not through the language used in meetings, plans, retreats, strategy documents, or mission statements.

The system tells the truth through repeated outcomes.

A missed follow-up may be an accident. A repeated missed follow-up is a system signal. A confusing handoff may be a mistake. A pattern of confusing handoffs is information. A delayed decision may be circumstantial. Repeated delayed decisions reveal something deeper.

The system is producing what it is currently structured to produce.

That may be uncomfortable. It is also useful.

The Problem Is Explaining Away the Pattern

Leaders often explain away repeated outcomes because the truth is inconvenient.

They say the timing was unusual. The person was busy. The team was tired. The customer was difficult. The volunteer was new. The project was special. The deadline was unrealistic. The season was abnormal. The failure was a one-off.

Sometimes those explanations are partly true. But when the same type of outcome keeps returning, the explanation must move from incident to pattern.

The question changes.

It is no longer, “Why did this happen once?”

It becomes, “Why does this keep happening here?”

That question is harder because it requires leaders to examine the structure underneath the activity. It may reveal unclear ownership, weak process, undocumented expectations, poor review rhythm, inadequate training, conflicting priorities, or leadership avoidance.

The pattern does not care what the organization intended. The pattern reveals what the organization has built.

The Visible Issue Is the Event. The Deeper Issue Is the Design.

The visible issue is usually the event.

  • The report was late.
  • The guest was not contacted.
  • The invoice was missed.
  • The client waited too long.
  • The decision stalled.
  • The meeting produced no next step.
  • The project lost momentum.

Events get attention because they are visible. But the deeper issue is design.

  • What made that outcome likely?
  • What structure allowed it to happen?
  • What ownership gap made it possible?
  • What review point was missing?
  • What standard was unclear?
  • What dependency created the bottleneck?
  • What assumption replaced assignment?

A system is not only software or a formal process document. A system is the way work actually happens — formal processes, informal workarounds, habits, expectations, tools, roles, meetings, incentives, personalities, and unspoken rules.

If the informal system is stronger than the formal one, the informal system wins. That is often where the truth lives.

Outcomes Reveal Operating Reality

Leaders need to learn to read outcomes without becoming defensive. Repeated outcomes are not always moral judgments. They are often operational diagnostics.

What Repeated Outcomes Reveal
  • If every decision waits for one person, the system is leader-dependent.
  • If every deadline needs a reminder, the review rhythm is weak.
  • If every new person gets confused, the onboarding process is unclear.
  • If every handoff requires explanation, the process is under-documented.
  • If every project stalls after the meeting, ownership is not being operationalized.
  • If every strong performer becomes overloaded, capability is substituting for structure.
  • If every important task becomes urgent, the planning cadence is insufficient.

The outcome is not random. It is pointing to the operating reality underneath the stated intention.

This is where mature leadership begins — not by defending the system, but by listening to what it is producing.

The System May Be Rewarding What You Say You Do Not Want

One of the hardest truths in organizational life is that systems often reward the behavior leaders say they dislike.

They want ownership, but every decision still comes back to them.
Dependency
They value preparation, but meetings regularly begin without agendas or pre-work.
Improvisation
They want growth, but no one owns follow-up with prospects, guests, or leads.
Leakage
They want quality, but there is no review standard before work reaches the client.
Inconsistency
They want leadership development, but the same few people carry all meaningful responsibility.
Passivity

People usually adapt to the real system, not the stated one. If the real system rewards urgency, people will wait until things become urgent. If the real system rewards overfunctioning, strong people will carry too much. If the real system rewards vagueness, people will avoid visible responsibility.

The stated values matter. But the operating system trains behavior.

The Truth Is in the Repetition

The first incident may deserve grace. The second may deserve attention. The third deserves diagnosis.

Repetition changes the category. When a pattern repeats, leaders should stop treating it as an exception — stop relying on another reminder, another speech, another general appeal, or another vague request for people to “communicate better.”

Those responses rarely fix the system. They may create temporary compliance, but the pattern usually returns because the underlying structure has not changed.

Repetition is the system raising its hand. It is saying:

  • This responsibility is unclear.
  • This process is not strong enough.
  • This cadence is missing.
  • This standard is not visible.
  • This decision authority is unresolved.
  • This dependency is too fragile.
  • This handoff needs design.
  • This value has not become operational.

When the same issue repeats, assume there is a structural message to read.

A Diagnostic Framework

When the system keeps producing an unwanted result, use a simple diagnostic framework.

Step 1

Name the Repeated Outcome

Be specific. Vague frustration produces vague solutions.

Instead of “Communication is bad” → say: “New guests are not receiving follow-up within forty-eight hours.”

Instead of “Projects are messy” → say: “Projects are leaving meetings without a named owner, deadline, or next review point.”

Instead of “People are not engaged” → say: “Only three members consistently accept meeting roles, and newer members are not being personally invited into responsibility.”

Specificity makes correction possible.

Step 2

Identify the Actual System

Map how the work really happens. Not how it is supposed to happen. Not how the manual says it happens. How does it actually happen?

  • Who starts the work?
  • Where does the request come from?
  • Who receives it?
  • Where is it tracked?
  • Who decides?
  • Who follows up?
  • Where does it slow down?
  • What is assumed but not written?

The actual system may be informal, fragile, and personality-dependent. That is the truth that needs to be seen.

Step 3

Locate the Missing Structure

Once the actual system is visible, ask what structure is missing.

  • Is there a missing owner?
  • A missing checklist?
  • A missing deadline?
  • A missing review point?
  • A missing standard?
  • A missing decision rule?
  • A missing communication path?
  • A missing training step?

Most repeated outcomes are not corrected by exhortation alone. They require structure.

Step 4

Change One Design Element

Do not attempt to fix everything at once. Change one design element close to the point of failure.

  • Assign the owner.
  • Write the checklist.
  • Add the review rhythm.
  • Clarify the decision authority.
  • Set the standard.
  • Build the template.
  • Create the follow-up trigger.
  • Remove the unnecessary approval step.

Then observe whether the outcome changes. A system correction is not proven by explanation. It is proven by a different repeated result.

Do Not Personalize What the System Produces

This does not mean people are never responsible. People are responsible for their actions, decisions, commitments, and integrity. A systems view should never become an excuse for poor character or chronic negligence.

But leaders must be careful not to personalize what the system is producing.

  • If good people keep failing in the same place, look at the system.
  • If new people keep getting confused in the same place, look at the system.
  • If strong people keep becoming overloaded in the same place, look at the system.
  • If leaders keep stepping into the same gap, look at the system.

A mature leader does not choose between personal responsibility and systems thinking. Both matter. People must own what is theirs. Systems must stop creating avoidable failure.

The Strategic Reframe

The system is not your enemy.

The system is your mirror. It reflects what has been clarified, what has been neglected, what has been rewarded, what has been tolerated, and what has been left informal.

That reflection may be frustrating, but it is valuable. It gives the leader something better than blame. It gives the leader diagnosis.

A repeated outcome is not merely a problem to resent. It is evidence to interpret.

This reframe changes leadership posture. The leader stops asking only, “Why won’t people do this right?” and starts asking, “What have we designed, allowed, or failed to clarify that makes this outcome predictable?”

That question opens the door to correction.

What to Do This Week

This week, identify one repeated outcome that has been frustrating you. Choose something concrete.

  • A missed follow-up.
  • A recurring delay.
  • A weak handoff.
  • A confused meeting.
  • An overloaded person.
  • A repeated customer issue.
  • A recurring volunteer gap.
  • A task that keeps returning to you.

Then work through four questions:

  1. What exactly keeps happening?
  2. How does the work actually move right now?
  3. What structure is missing?
  4. What one design change would make a better outcome more likely?
The Posture

Do not begin with blame. Begin with reality. The system is already telling the truth. Read it.

The Question to Carry Forward

The question is not, “What did we intend?”

The better question is, “What are we repeatedly producing?”

That question brings leadership back to reality. Intentions matter, but outcomes reveal the system. Repeated results show what is actually being reinforced, tolerated, hidden, rewarded, or neglected.

If the system keeps producing drift…
Design for review.
If it keeps producing delay…
Clarify ownership.
If it keeps producing confusion…
Document the process.
If it keeps producing dependency…
Distribute responsibility.
If it keeps producing inconsistency…
Define the standard.

The system is telling the truth.

The leader’s work is to listen, diagnose, and redesign.

Systems & Governance

What Is Your System Repeatedly Producing?

Schedule an operational review with Roe & Associates to identify what your current systems are repeatedly producing and where design needs to change.

Schedule a Strategic Call