ECP Churn: Why God Keeps Sending the Same Lesson

There's a pattern every systems engineer has seen.

A decision gets "closed."

The program moves on.

Then a few months later—it's back.

Same issue.

Same interface.

Same argument.

New slide deck.

Different packaging. Same problem.

We call it ECP churn—decisions that don't stay closed.

And when it shows up in a program, it's not a paperwork problem.

It's a decision quality problem.

The Hidden Truth About Reopened Decisions

Every reopened Engineering Change Proposal is telling you something:

"The original decision didn't propagate correctly—or it was made without sufficient truth."

The INCOSE Systems Engineering Handbook defines a change proposal as requiring not just technical review but impact analysis across all affected baselines—requirements, design, verification, and operations.[^1] When that propagation is incomplete, the decision doesn't close. It defers.

Either:

The architecture wasn't aligned

The dependencies weren't understood

Or the decision was made to relieve pressure—not to resolve reality

NASA's Systems Engineering Handbook notes that "the root cause of most system failures can be traced to decisions made early in the life cycle that were not well-informed or well-documented."[^2]

So the system does what systems always do.

It pushes the decision back to the surface.

Your Life Has a Decision Architecture Too

Now zoom out.

Your life is a system.

It has:

beliefs (requirements)

identity (architecture)

behaviors (implementation)

outcomes (performance)

And just like an engineered system, your life runs on decisions.

ISO/IEC/IEEE 15288 identifies decision management as a core technical process precisely because decisions are not events—they are structures that shape every downstream element of a system.[^3]

Some of those decisions get made cleanly.

Others don't.

Spiritual ECP Churn

You ever notice how certain struggles keep coming back?

The same insecurity

The same conflict

The same temptation

The same frustration

You thought you dealt with it.

You "closed the decision."

But it reopens.

That's not random.

That's spiritual ECP churn.

"As a dog returns to its vomit, so fools repeat their folly."

— Proverbs 26:11

The repetition isn't the problem. It's the signal.

God Doesn't Repeat Himself—We Do

It can feel like:

"Why does God keep putting me through the same thing?"

But what's actually happening is:

The decision never truly closed.

Because the decision wasn't:

rooted in truth

aligned with identity

propagated through your life

"There is a way that appears to be right, but in the end it leads to death."

— Proverbs 14:12

A decision that feels closed—but isn't anchored to truth—is just latency. The failure is already accumulating.

So God, in His mercy, doesn't let the system drift.

He brings it back.

Not as punishment.

As realignment.

"My son, do not despise the Lord's discipline, and do not resent his rebuke, because the Lord disciplines those he loves."

— Proverbs 3:11–12

The Root Cause: Architecture Misalignment

In engineering, churn usually traces back to one thing:

"The architecture and the decisions don't match."

Rechtin and Maier's foundational work on systems architecting identifies architectural incoherence—where system decisions contradict the governing structure—as the primary generator of rework and instability.[^4] You can't issue decisions downstream that violate the architecture upstream and expect them to hold.

In life, it's the same.

You can't make a decision like:

"I trust God"

and still operate from an identity of:

"I'm on my own."

That's an architectural contradiction.

And contradictions create churn.

"Do not conform to the pattern of this world, but be transformed by the renewing of your mind."

— Romans 12:2

Paul isn't describing behavior modification. He's describing an architecture change—the kind that makes downstream decisions coherent.

The Decision That Actually Closes

A decision only stays closed when it is:

true (aligned with God's word)

owned (not outsourced to emotion or circumstance)

propagated (affects how you think, act, and respond)

The SEBoK's decision analysis framework calls this traceability: a decision must be traceable to its rationale and must have documented effects on the baseline it governs.[^5] A decision with no traceable propagation is, technically, no decision at all.

That's what transformation actually is.

Not behavior modification.

Decision coherence.

"If you hold to my teaching, you are really my disciples. Then you will know the truth, and the truth will set you free."

— John 8:31–32

Truth-anchored decisions propagate. They hold. They close.

The Mercy of Reopened Decisions

Here's the part that changes how you see it:

Reopened decisions are not failure. They're feedback.

God is not frustrated that you're revisiting something.

He's committed to closing it correctly.

Because He knows:

A misaligned decision today becomes a structural failure tomorrow.

The MIL-HDBK-61B configuration management guidance makes exactly this point in an engineering context: deferring a legitimate change to avoid disruption doesn't eliminate the cost—it compounds it.[^6]

"He who began a good work in you will carry it on to completion until the day of Christ Jesus."

— Philippians 1:6

God isn't abandoning the process. He's completing it. The loop reopens because the work isn't finished—not because He's given up.

Breaking the Cycle

If something keeps coming back in your life, don't just try to fix the symptom.

Ask:

What decision did I think I made?

What truth is that decision anchored to?

Where is my life still contradicting it?

This is root cause analysis—not surface-level corrective action. NASA's Root Cause Analysis Guide distinguishes between causal factors (symptoms that can be treated) and root causes (architectural deficiencies that must be corrected).[^7]

Then go deeper.

"Trust in the Lord with all your heart and lean not on your own understanding; in all your ways submit to him, and he will make your paths straight."

— Proverbs 3:5–6

Submitting is the propagation step. It's how the decision actually reaches the baseline it's meant to govern.

Because the goal isn't to get past the issue.

It's to resolve the decision at the root.

Final Thought

In engineering, we say:

"The system always tells the truth."

Your life does too.

"Do not be deceived: God cannot be mocked. A man reaps what he sows."

— Galatians 6:7

If something keeps resurfacing, it's not because you're stuck.

It's because something deeper is still unresolved.

God doesn't keep sending the same lesson.

He keeps giving you the opportunity to close the right decision.

For real this time.

References

[^1]: INCOSE. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, 4th ed. Wiley, 2015. Section 4.3, Technical Management Processes—Decision Management.

[^2]: NASA. Systems Engineering Handbook, Rev. 2. NASA/SP-2016-6105. Washington, D.C.: NASA, 2016. Section 6.8.

[^3]: ISO/IEC/IEEE 15288:2023. Systems and Software Engineering—System Life Cycle Processes. Decision Management Process, §6.3.8.

[^4]: Maier, M. W., and Rechtin, E. The Art of Systems Architecting, 3rd ed. CRC Press, 2009. Chapter 4: Architecting for Coherence.

[^5]: Pyster, A., et al. (Eds.). Systems Engineering Body of Knowledge (SEBoK), v. 2.7. BKCASE, 2023. Part 3: Systems Engineering and Management—Decision Analysis.

[^6]: MIL-HDBK-61B. Configuration Management Guidance. U.S. Department of Defense, 2020. Section 5.4: Change Control and Disposition.

[^7]: NASA. Root Cause Analysis Guide. NASA/SP-2014-3699. Section 3.2: Distinguishing Causal Factors from Root Causes.