Articles on: Decisions and Actions

How Decisions Evolve Over Time

Decisions aren't static objects you make once and never touch again. They're living agreements that flow and shift as your group learns and as circumstances change. Understanding this changes everything about how you approach decision-making.

Note: The concepts in this article about decisions as flows rather than objects resonate deeply with the work of Indy Johar (see his essay "Decisions & Decisioning"). JOD independently developed the JOD Decision Path concept, and we were excited to discover Johar's theoretical framework, which aligns beautifully with what we'd built. We're grateful for his thinking on this topic.

← Back to Overview

What This Means in Practice

Decisions are living and they are very likely to change.

JOD recognizes and accommodates this reality. Our progressive decision management system is designed for how decisions actually work in the real world—not how we wish they worked.

Why Decisions Change

You might make a strategic decision based on current information, then discover:

The external environment shifted (funding disappeared, partners backed out, community needs changed)
You learned something new that changes feasibility
Another group's work impacts your approach
Your initial assumptions weren't quite right
The path forward revealed unexpected obstacles or opportunities

This is normal and expected. It's not a sign of poor planning—it's a sign you're paying attention to reality.

How JOD Supports Living Decisions

When a Decision needs to change, you update it in the system. But here's what makes JOD different: the system captures the complete Decision Path.

What gets captured in the Decision Path:

The original Decision
What changed and when
Why it changed (your notes)
Who made the update
The complete journey of the decision over time

The Decision Path Interface:

JOD presents the Decision Path as an easy-to-read journal. When you view a Decision, you see:

The current Decision text and status at the top
When it was last updated and by whom
A chronological timeline below showing every change, update, and milestone
Notes explaining why changes were made
The complete flow of how the decision evolved

This journal view makes the decision's journey visible to everyone with access. You can see how your group's thinking developed, what you learned along the way, and how reality shaped your commitments.

Why this matters:

You can see how your group's thinking developed
Others can understand the learning journey
Patterns emerge (what kinds of things tend to shift? why?)
Institutional knowledge is preserved, not lost
The "flow" becomes visible, not hidden

Example: A Decision Evolving

March: Original Decision

"Launch youth leadership cohort in Chicago, Atlanta, and Phoenix by June"

Context: Three partner organizations confirmed. Funding secured. Team excited and ready.

April: Reality Teaches Something New

Phoenix partner organization's Program Director resigned unexpectedly. Interim staff don't have bandwidth to co-design curriculum. Hiring new Director takes until August.

April: Updated Decision

"Launch youth leadership cohort in Chicago and Atlanta by June. Phoenix launch delayed to September due to partner organization staffing changes"

Notes added: "Phoenix partner informed us their new Program Director doesn't start until August. Rather than rush or launch without their full participation, we're building the Phoenix cohort with their new leadership starting in fall. This maintains the partnership strength and ensures quality."

What Changed

The decision evolved based on new information. The change history shows:

What you learned (staffing transition at partner)
Why you adapted (maintaining partnership quality)
The thoughtfulness of your response (delaying rather than rushing)

This isn't failure. It's your group responding intelligently to reality.

Recommitment, Not Just Commitment

When you update a Decision, you're not admitting failure. You're recommitting based on what you've learned.

This is how organizations get smarter over time instead of just busier.

The old way:

Make decision
Reality proves it unworkable
Quietly abandon it or push forward despite problems
No record of what was learned

The JOD way:

Make decision
Reality provides new information
Update the Decision with notes on what changed
Create record of learning
Organization gets smarter

Practical Implications

For Group Leads

During meetings:

Don't treat Decisions as locked in stone
When someone says "but we already decided," ask "What have we learned since then?"
Create space for honest reflection on whether Decisions are working

Between meetings:

Watch for signals that a Decision needs updating
When you learn something new, update the Decision promptly
Add clear notes about why it changed
Mark significant changes as "Material Changes" when they warrant notification

About Material Changes:

When you update a Decision, you can mark the change as "Material" if it's significant enough that Group Sponsors and Conveners should be notified. JOD will send an email notification to all Group Leads, letting them know:

What Decision was changed
What the change was
Any notes you added about why

This ensures important changes don't go unnoticed, even between meetings.

Important: Deleting a Decision also triggers a Material Change notification. However, JOD strongly advises against deletion since it erases the Decision Path entirely. Consider "Closing" the Decision instead to preserve the learning journey while indicating it's no longer active.

In planning:

Review Decisions periodically—are they still working?
Look at the Decision Path for patterns in what changes and why
Share learning with other groups

For All Team Members

Speak up when you learn something:

If you discover information that affects a Decision, share it. You're not "questioning the decision"—you're helping the group stay aligned with reality.

Expect evolution:

Don't be surprised when Decisions change. Be surprised if they don't—it might mean your group isn't learning.

Read the Decision Path:

When you look at a Decision, review its Decision Path (the change history). There's learning in how it evolved—what changed, why, and what that tells you about your group's work.

Common Concerns

"Won't this create chaos? We'll never actually commit to anything!"

No. You still make commitments—clear ones with names, timelines, and responsibilities. But you recognize those commitments may need to evolve. That's not chaos—it's adaptive capacity.

"How do we know when to update vs. when to stay the course?"

Update when you have new information that materially affects the Decision's feasibility or wisdom. Stay the course when obstacles are expected and surmountable. Over time, your group will develop judgment about this.

"Won't people lose trust if Decisions keep changing?"

The opposite. People lose trust when Decisions clearly aren't working but no one acknowledges it. Transparent updates with clear reasoning build trust.

The Bottom Line

Decisions are living agreements. They emerge through dialogue, get captured in moments, and continue to evolve as your group learns.

JOD's progressive decision management system helps you:

Capture strategic agreements clearly
Update them as you learn
Track the complete Decision Path—the journey of how your thinking evolved
Build institutional knowledge over time

This isn't a weakness of the system—it's the core strength. In a complex, changing world, the organizations that thrive are the ones that can learn and adapt.

Updating Decisions based on new information isn't failure. It's intelligent adaptation. It's how your group gets smarter.

Remember: The goal isn't to make perfect decisions that never change. The goal is to make good decisions, watch what happens, learn from reality, and adapt thoughtfully. The Decision Path shows this journey—making the flow visible to everyone.

Learn about Decisions → | Learn about Actions → | See the workflow →

Updated on: 05/01/2026

Was this article helpful?

Thank you!