Dr. Alan Barnard's ProConCloud is a way to understand a conflict deeply enough that a better option can appear.
I used a pro/con cloud in my previous post about the agent loop conflict. The shape was useful because it made the conflict visible. It showed the goal, the opposing actions, the good reasons behind each action, the bad outcomes each action could create, and the next move that might escape the conflict.
The idea comes from Dr. Alan Barnard. He developed the ProConCloud by combining several tools from the Theory of Constraints tradition, including Dr. Eli Goldratt's Change Matrix and Evaporating Cloud, also called the Conflict Cloud.
What I like about it is that it treats conflict as useful information. A conflict is not just a disagreement to settle. It is evidence that different people, or different parts of the same person, are trying to protect something important.
The conflict is the material
The first useful move is to stop treating one side as obviously wrong. In a real conflict, both sides often have a good reason to exist.
One side might protect speed. The other protects quality. One side protects autonomy. The other protects coordination. One side protects attention. The other protects judgment.
If you only argue for one side, the conflict stays hidden. If you map both sides, the structure starts to appear. You can see what each side is trying to preserve, and you can see the damage each side might cause if it wins too completely.
The five-step shape
Barnard presents the ProConCloud as a five-step method for making better, faster decisions when the decision matters.
- Define the problem and why it is important.
- Define your conflict and their conflict.
- Resolve the conflict with win/win options.
- Use “yes, but” reservations to strengthen the plan.
- Design a good experiment.
That sequence is important. It starts with attention: is this problem worth thinking about? Then it moves into empathy: what conflict am I in, and what conflict might the other person be in? Then it moves into design, planning, and learning.
Four ways to escape the either/or
The part I find most useful is the set of four win/win directions: Change++, No Change++, When / When Not, and Another Change.
Those four directions give the mind somewhere to go when it is stuck. You can improve the change. You can improve the no-change option. You can decide when each option applies and when it does not. Or you can invent another change that satisfies the goal with fewer negative effects.
This is the part that makes the tool feel alive. The first options are not necessarily the answer. They are raw material for finding a better answer.
Reservations are design input
I also like the way the ProConCloud treats “yes, but.” In many planning conversations, objections are treated as resistance. Someone raises a risk, and the room hears negativity.
But a valid reservation is useful. It tells you where the plan is still fragile. It can show where the change needs an extra condition, a boundary, a safety check, or a smaller first step.
That feels especially relevant for software work. Many good engineering objections are not attempts to block change. They are early warnings from someone who can already see where the change will break.
The decision becomes an experiment
The final step is to design a good experiment. This keeps the method from becoming only a diagram. A decision is not done when the picture looks tidy. It has to survive contact with reality.
I like that because it lowers the drama around decisions. You are not trying to prove that your idea is perfect. You are trying to create a test that can teach you something.
The decision becomes less like a verdict and more like a learning loop.
Why this fits agent work
I keep running into conflicts like this with coding agents. Make the agent more autonomous, but do not lose control. Add more tools, but keep the environment understandable. Move faster, but do not produce shallow work.
The ProConCloud gives me a way to slow those conflicts down without killing the momentum. It helps separate the goal from the tactic, the good reason from the bad outcome, and the reservation from the refusal.
That is the lesson I want to keep: when a decision feels stuck, do not only argue harder for one side. Understand why the conflict exists, then create a change that makes the conflict less necessary.