Insights · Questions That Decide

What would change our mind?

Decide in advance what evidence would send you back to the table, and write it down. Choosing between Agile and traditional systems engineering is a good place to start.

Epic Solutions Group · October 2026 · 2 min read

Every program decision carries risk the team has chosen to accept. Testing and analysis reduce that risk. They rarely remove it. The question that keeps accepted risk visible is: what would change our mind?

Answering it before the decision does two things. It tells the team what to watch for. And if a later failure review asks why the program chose as it did, the reasoning is already on paper.

An example: Agile or traditional?

Few choices start more debate than whether to run development with Agile methods or a traditional, plan-driven systems engineering approach. The answer often depends less on preference than on where the interfaces are.

Many programs land on a hybrid: Agile inside the boundary, traditional discipline at it.

Write down what would change the choice

The method decision deserves its own “what would change our mind” list. For example:

Any one of those is a signal to revisit the method for that part of the system.

Where AI helps

AI is well suited to this kind of watching. It can sort an interface list into internal and external, compare the current list against the baseline, scan change requests and test results for the signals the team wrote down, and raise a flag when one appears. The team still makes the call. AI makes sure the question gets asked on time.

Working through a decision like this?

Our systems engineers can help you frame the question, weigh the options and keep the evidence traceable.

Book a 20-minute call