STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates
Complex systems, by their nature, generate a tangled web of connecting causes and effects. So it’s surprising how often solutions aimed at fixing root-cause issues come down to a binary choice: do ‘X’, or don’t do ‘X’. Both can seem necessary—the classic dilemma. So what’s the way out?
[Listen to audio version, read by David Hodes]
This is Part 4 of our series on the Logical Thinking Process: Part 1 | Part 2 | Part 3 | Part 4 | Part 5
Of all the tools of the Logical Thinking Process, the one I find myself using the most is the Evaporating Cloud, or more prosaically the conflict resolution diagram. Legend has it that Eli Goldratt, who invented the tool, was inspired by Richard Bach and his 1977 book Illusions, in which the main characters remove storm clouds from the sky by thinking them away:
‘If you really want to remove a cloud from your life, you do not make a big production out of it, you just relax and remove it from your thinking. That’s all there is to it.’
The Evaporating Cloud tool intends to similarly ‘vapourise’ difficult problems by resolving an underlying conflict. If you share a goal with the person, people or organisation with whom you’re in conflict, Goldratt teaches that there is not really a conflict. Rather, one or more assumptions made about the situation is false, and once you unearth it or them, you have a pathway to a win-win solution without the usual compromises.
We always construct the evaporating cloud the same way. The entity at A is the goal or the objective. Entities B and C are two requirements (necessary conditions) which both must be met if you are to achieve your goal. D and D’ (pronounced D prime) are where the conflict resides—the pre-requisites to the earlier requirements.
The evaporating cloud uses necessary condition logic, and therefore it is read: In order to [entity at the tip of the arrow] I must [entity at the base of the arrow]. I usually begin with the goal statement, which should come from the building of the goal tree. I then put in place the two prerequisites at D and D’, representing the horns of the dilemma. While B and C must coexist to deliver on the goal, D and D’ are assumed not to be able to coexist simultaneously and are thus the subject of the dilemma. Using Visio, or similar software tools, I usually slap down the first draft of these five essential elements pretty quickly. It is easy enough to do the editing of the entities once you have cleared your mind of the burden of holding all of these conflicting thoughts at the same time.
One of the great benefits of developing the evaporating cloud is that it allows you to see the whole structure of the argument. I have found that every time I think I know the answer to a dilemma and want to go with my fast-thinking problem-solver mind, I force myself to slow down and construct the argument. I invariably find a deeper level of insight that, in turn, helps produce a more imaginative and better-argued solution. If I have developed the cloud by myself, it acts as a powerful means of communicating what’s on my mind. If it is built collaboratively, it provides a real focusing tool for the team to have the requisite conversations which lead to a lasting solution.
Once the five building blocks are in place, it’s time to do the tour around the cloud to ‘surface’ the assumptions which hold it together. Based on the typical example below, we read In order to [entity at the tip of the arrow] I must [entity at the base of the arrow] because [assumptions]. For the novice users of the cloud, there is usually a trap in this step. A practised logical thinker will raise as many assumptions as their mind will provide them. It is a skill to be able to think of assumptions which are contrary to your prejudices and cognitive biases.
However, when the novice listens in, they usually think that when you call out an assumption you are advocating the position articulated by that assumption and get ready with their defensive routines. Remind them, indeed remind yourself, that it is vital that you give free expression to every view. It’s the way we come to discern what’s true and valuable and what we can discard. Its power lies in removing the person from the argument and liberating any and all to speak their truth without fear of retribution or shame. If we are intentionally asking people to surface all assumptions, there can be none which we would consider superfluous or too stupid to be mentioned. This is the spirit in which we conduct the analysis of the cloud.
Let’s have a look now at an example. We start with the goal at A: ‘grow competitive returns for our shareholders now and in the future’. If we were dealing with a specific organisation, we’d have to be more precise than that, asking the question of at least how much, by no later than when. But, for this exercise, that will suffice. In our hypothetical case, this business has hit a bump. Their budgeted profits are under attack, and they are under pressure to cut back on investment in new capabilities.
On the one hand, at D, they have to perform against the cost and revenue budget. On the other hand, they have to invest in new capabilities. Once I have the goal and the dilemma, I ask the question: ‘why do I need to have D (perform against our cost and revenue budget) if I need to achieve my goal at A (grow competitive returns for our shareholders now and in the future)? Well, I figure it’s because of what I have placed in B—I must safeguard today’s results.
We follow the same process when I ask the question between D’: ‘why would I invest in new capabilities’ if I need to achieve my goal (grow competitive returns for our shareholders now and in the future’?) Again, the answer comes back: because I must ‘live into a bold vision’. So there is a natural and creative tension between B and C. But they both must be true if the goal is to be achieved, locked as it is into providing growth now and in the future.
If we are happy with the underlying construct, we can move onto surfacing the assumptions. I won’t cover them all, but invite you to do your scrutiny and see what you might want to add. Let’s take one from each branch of the cloud.
A-B: In order to [grow competitive returns for our shareholders now and in the future], we must [safeguard today’s results] because [safeguarding today’s results gives us the credibility we need for our shareholders to continue investing in our business]. Under what circumstances would this not be true? What if your shareholders understand the difficult times the organisation finds itself in and knows that by cleaving to today’s results, they will be sacrificing a much larger value over the life of the business? What case could you make to the shareholders that would persuade them that you predicated today’s results on an idea of what you thought the market was looking like six months ago, but now, all that has changed?
B-D: In order to [safeguard today’s results] we must [perform against our cost and revenue budget] because [performing against our cost and revenue budget is the key indicator of our ability to safeguard our results]. What if the market had moved in such a way that, for a marginal increase in investment, you could fundamentally change the cost and revenue mix? Of what use would the budget be then? What if the price of a strategic material input has increased as a result of a global shortage of it? And, what if the competitive nature of the market for your product and service will not allow you to pass on any price increase without materially affecting your market share?
A-C: In order to [grow competitive returns for our shareholders now and in the future], we must [live into a bold vision] because [you cannot get superior returns doing the same thing, year in and year out]. It would usually be the case that as your competitors continue to innovate, if you stand still, they will overtake you. But maybe you have a monopoly, by way of a patent for example, so perhaps you can maintain a lead for an extended period.
C-D’: In order to [live into a bold vision] we must [invest in new capabilities] because [our existing capabilities in terms of people, process and technology are not sufficient for us to live into our bold vision]. Perhaps the bold vision included a significant program to digitalise the business, with a backbone of a new core platform. Such a program would imply that to transform with the latest technologies, the legacy systems would be retired; you would need to develop new processes around that technology and people would need training in both the new processes and technology. So, it’s a valid assumption.
D-D’: We must also pay heed to the assumption that sits between the horns of the dilemma. Here we state that [we cannot perform against our cost and revenue budget and invest in new capabilities]. Well, is this a false dichotomy? What is the specific circumstance of the business that would make this true? A cash crunch? A major disruption in the market? Loss of a significant customer? A strategic change in the supply chain brought on by regulatory requirements? Coronavirus?
Once you have surfaced and scrutinised all of the links and assumptions, it’s time to make a decision. Sometimes it is obvious, as one of the links between any two of the entities proves to be held together by invalid assumptions. On some rare occasions, the whole argument seems to be held together as tight as the bolts on a high speed turbine. On these occasions, it is necessary to think of an injection which doesn’t exist in the current reality, but could be introduced to make a high-leverage difference.
As productivity is the tide to lift all ships, it could be that the introduction of some fresh thinking about how work is planned and performed could both safeguard today’s results and allow progress on the bold vision. Perhaps the injection is to think about what the risk-adjusted discounted cash flow is for several different plausible and relevant scenarios, then choose one that has the best chance of securing the desired outcome. After all, Amazon, the world’s most valuable company, did just that—foregoing today’s profits for an indomitable position in its market over the long haul. Perhaps it’s also no coincidence that Goldratt’s The Goal is one of three books that Jeff Bezos recommends to all his executive team.
____________________________
This is Part 4 of our series on the Logical Thinking Process.
Part 1: Intro to the Logical Thinking Process
Part 2: Setting your goal
Part 3: Mapping your current reality
Part 4: Deciding with the evaporating cloud
Part 5: Realising the future
____________________________
What’s next?
The change from standard thinking to Theory of Constraints (TOC) is both profound and exhilarating. To make it both fun and memorable, we use a business simulation we call The Right Stuff Workshop.
We’d love to run it with you. To learn more:

[Background image: Bulls fighting, Richard Lee on Unsplash]
____________________________
The Shortest Path From Mineral Potential to the Highest Sustainable Cash Flow
A mining investment earns its return through the conversion of mineral potential into dependable cash flow. Every uncertainty, delay and misplaced commitment along that journey affects how much capital is required, how long it remains exposed and what the investment ultimately delivers.
For those who allocate capital, the challenge extends beyond identifying an attractive resource. The acquisition thesis depends on connected decisions across geology, studies, approvals, construction, commissioning, production and closure. Each decision can strengthen the investment case or quietly erode it.
An AI enabled Mining and Metals Operating System connects evidence, reasoning, accountability and execution across that journey. Systems Thinking provides the whole asset perspective. The Theory of Constraints directs attention towards the factor governing value today. AI helps people interpret information, examine alternatives and coordinate the work required to change the outcome.
“Where is the greatest gap between the value this asset could credibly create and the value it is currently on course to deliver?”
The operating model below brings these ideas together: human accountability above, the life of mine across the centre, and integrated knowledge and reasoning supporting every stage.

An operating system needs a clear management accountability hierarchy. Purpose and levels of work define the decisions people must make, the authority they require and the capability needed to carry their responsibilities.
A supervisor protecting today’s production, a project director preparing commissioning and a board allocating development capital face different levels of complexity and different time horizons. Each needs information appropriate to the work, clear decision rights and a reliable route for escalation.
AI makes this clarity more important. Recommendations must have accountable human owners, particularly where commitments cross the boundaries between investors, asset owners, contractors and service providers.
For investors, this provides a practical test of execution capability: can the organisation show who owns each assumption in the investment thesis, who can authorise action and how unresolved issues reach the right decision maker?
Exploration creates value when it resolves uncertainty that changes a worthwhile decision. More data becomes useful when it improves confidence about what is present, where it lies and what further work is justified.
AI can help connect geological reports, assay results, drilling records, geophysical observations and three dimensional interpretations. Shared terminology and traceable relationships allow teams to compare evidence, expose inconsistencies and distinguish observations from interpretations.
The investor’s question is which uncertainty governs the next commitment. A targeted investigation may change the development route, support further drilling or reveal that the opportunity cannot yet justify additional capital.
New sensing and interpretation methods must earn confidence through appropriate validation. The objective is a better sequence of learning and commitment, with uncertainty visible throughout.
Studies turn a resource opportunity into choices about mine planning, processing routes, infrastructure, scale and development sequence. Those choices establish much of the future cost, risk and operating flexibility of the asset.
An integrated operating system connects technical narratives, economic models, engineering constraints and spatial representations. Teams can examine whether assumptions agree across disciplines and whether the preferred option remains attractive under plausible changes in conditions.
Approvals, water, power, logistics and workforce requirements belong in this comparison from the outset. Internal experience and relevant external benchmarks can challenge optimistic estimates.
For investors, the benefit is a clearer explanation of why an option deserves funding, what could defeat it and which evidence should be obtained before the next irreversible commitment.
“The most valuable early action may be the one that changes the next capital decision.”
Once capital is committed, the central question becomes whether the project remains on course to deliver its business case. Progress percentages alone cannot answer it.
Engineering maturity, procurement, construction sequencing, approvals and commissioning readiness must be considered together. Individually manageable deviations can combine into a material threat to first production and cash flow.
AI supported delivery intelligence can connect schedules, costs, risks and physical evidence, helping teams identify contradictions and emerging dependencies between formal review gates.
Management can then assess intervention options while choices remain available. A useful assurance process explains what changed, why it matters, who must act and when. Success appears in improved delivery confidence, controlled capital exposure and a credible route into operation.
The economic performance of a mine depends on how extraction, material movement and processing work together. Improving one activity can consume capital without improving the whole.
If processing capacity governs saleable output, increasing mining volumes may simply build stockpiles and working capital. If feed variability constrains recovery, additional plant availability may deliver less benefit than expected.
Connecting mine plans, ore characteristics, plant conditions and production results helps teams investigate these relationships. AI can support the comparison of operating choices, while physical models and simulation help test their consequences.
The discipline is to find the constraint, optimise for it, collaborate around it, uplift it and start again. The measure is the resulting contribution to cash generation, with safety, quality and environmental obligations respected.
Maintenance creates value through its effect on the productive capability of the system. Equipment critical to the governing constraint deserves particular attention because its failure can interrupt the entire flow of output.
An integrated operating system connects procedures, equipment histories, sensor readings, work orders, spare parts and operating conditions. Consistent asset identities and failure classifications help teams interpret information across systems.
AI can support prioritisation and flag emerging patterns for investigation. Simulation can also help operators and maintainers rehearse commissioning, abnormal conditions and recovery from disruption.
For investors, the question is whether this changes reliability and economics: more dependable throughput, better recovery, fewer damaging interruptions and a sustainable balance between production demands and asset capability.
Tailings facilities connect engineering performance, environmental responsibility, operational continuity and long term liability. Their condition and management belong within the investment case.
Inspection reports, monitoring data, risk thresholds, drawings and terrain models can be brought into a shared context. AI can help identify inconsistent records, surface changes requiring attention and connect actions with accountable owners.
Qualified professionals must interpret the evidence and authorise decisions. Traceability matters: the organisation should be able to show what was observed, how it was assessed and what followed.
Where reprocessing or resource recovery is contemplated, the opportunity requires its own technical and economic evidence. Potential value must be considered alongside remediation obligations, additional capital and the consequences of disturbing existing facilities.
Closure decisions begin long before production ends. Land disturbance, infrastructure choices, water management and waste handling can create obligations that persist beyond an investor’s ownership period.
Connecting closure plans with operating and capital decisions helps reveal those consequences earlier. Progressive rehabilitation can be evaluated alongside production needs, while evolving assumptions remain visible in forecasts and decision records.
AI can support the organisation of obligations, evidence and dependencies across the asset’s life. Credible cost estimates and technical judgments remain essential.
For investors, better closure visibility informs valuation, capital planning and exit readiness. A future buyer needs confidence that liabilities are understood, supported by evidence and reflected in the economics.
Supporting every stage is the ability to reason across verbal, numeric, logical and spatial information. Reports explain intent; models quantify consequences; rules establish conditions; drawings and three dimensional models reveal physical relationships.
These sources need shared meaning, or semantics, and explicit relationships, or ontology, within the organisation and across customers and service providers. Otherwise, apparently connected systems can continue to describe different realities.
For example, “ready for commissioning” should connect to agreed requirements for construction completion, inspection, training and operational acceptance.
AI agents can help trace dependencies, identify conflicting assumptions and prepare options. The operating system then connects decisions to owners, scheduled work and completion evidence. Learning from the result updates the next decision.
“Enterprise value is the product. Capabilities are the machinery.”
Begin with one material value problem. Establish the economic baseline and current trajectory. Identify the governing constraint, material uncertainties and credible intervention options. Agree accountable owners, decision gates and a practical action pathway.
Measure the result through time to cash, throughput, recovery, capital exposure, operating cost and liability. Translate changes into the investment model, including implementation costs and avoiding double counting.
An AI enabled Mining and Metals Operating System earns its place when it helps change the asset’s economic trajectory. For investors, the opportunity is a repeatable capability for converting mineral potential into realised value.
Concept validation
A concept can look convincing in a presentation and still make an important task harder. A patient may misunderstand an indicator. A clinician may need information the design does not provide. A promising workflow may depend on support unavailable in the intended setting.
These problems become more expensive when the organization discovers them after committing to architecture, tooling or a launch plan.
We must ask how effectively concepts are validated before significant resources are committed. Patient Centered Design treats this as a learning discipline: turn ideas into testable solutions rapidly using low fidelity prototyping, put them in front of relevant users and gather evidence about whether they improve the outcomes that matter.
“A convincing presentation shows what the team hopes will happen. A useful test reveals what people actually do.”
A prototype without a learning objective can generate interesting comments while leaving the key decision unresolved. Start by identifying what must be true for the concept to succeed.
Does the patient intuitively understand the required action without explanation? Can the professional recognize when the result is ready to use? Does the proposed approach fit the work surrounding the task? Will people take meaningful steps toward adoption?
State the assumption and the evidence needed to assess it. Agree what would support proceeding, what would require revision and what could make the concept unviable. Gather quantitative data along with qualitative verbal feedback.
Prioritize questions with substantial consequences for the investment. An attractive enclosure deserves less attention than an unresolved issue that could prevent safe or practical use of the whole solution.
A picture is worth a thousand words. A simple user experience prototype is worth a thousand pictures. Choose artifacts that maximize learning with the least effort. The appropriate artifact depends on what the team needs to discover.
A sketch may help users explain how they interpret a proposed interaction. A physical mock-up may expose handling difficulties. A simulated interface can support a sequence of tasks. A more complete prototype may be necessary to examine timing, feedback or combined interactions.
Build enough realism to test the assumption accurately. Excessive detail can consume resources without improving the evidence, while insufficient fidelity can conceal the issue being investigated.
Make limitations clear to participants and observers. A manually simulated function may help test an experience, but it does not establish that the technology can deliver that function reliably.
Patients and healthcare professionals can differ in experience, confidence, physical ability, responsibilities, and access to support. Those differences influence whether the concept helps them complete the job.
Define the participants and contexts relevant to the test. Include people whose circumstances could expose difficulties the development team has overlooked.
A familiar expert may work around a confusing interface that challenges a new user. A clinician from a highly supported center may assume resources unavailable elsewhere. Research needs to reveal these dependencies.
Match the study to its purpose. Exploratory sessions can identify problems and guide iteration. They do not automatically establish population-wide performance or replace the evidence required for later design validation.
An Experience Café gives participants a structured opportunity to encounter concepts and talk about their experience. Its value comes from the quality of the scenario, observation and follow-up questions.
Set up situations that reflect what the person is trying to accomplish. Let participants interact with the artifact rather than rely solely on a demonstration by its designer. Build rough and rapid.
Assign roles to facilitators and observers. Agree how comments, actions and difficulties will be captured. Keep the session focused on learning rather than defending the proposed solution. Hold a conversation around the prototype. “Can you show me how you would use this?” “Tell me what you are thinking here.”
Ask participants to explain what they believe is happening and what they would do next. Observe where the concept supports that understanding and where they hesitate, improvise or seek help.
A facilitator can unintentionally make a weak concept appear successful by explaining each step or supplying missing information.
Use neutral prompts and allow participants to reveal their interpretation. When assistance is necessary, record it along with the point at which the person became stuck.
Follow observations with questions about purpose and reasoning. What did the participant expect? Which information did they look for? Why did they choose that action?
Separate a preference from evidence about task performance. “I like this one” may reflect appearance or familiarity. Successful completion, appropriate interpretation and manageable effort provide a stronger basis for assessing whether the concept addresses the need.
“Every explanation the facilitator must supply is a question about what the design expects the user to know.”
The product interaction belongs within a wider job. Test preparation, readiness, execution, monitoring and what follows, wherever these activities affect the concept’s value.
A device may work well once configured while setup introduces avoidable complexity. A result may be easy to view while the professional still needs to transfer it manually before acting.
Include relevant dependencies on caregivers, staff, information and other systems. Investigate whether the concept reduces burden for one participant by increasing it for another.
Use realistic scenarios appropriate to the development stage. Important exceptions and recovery steps deserve attention alongside routine success. An incomplete or interrupted task can reveal weaknesses that a carefully guided demonstration leaves hidden.
Ease of use involves what a person must notice, understand, remember, decide and physically do. A tidy interface can still demand substantial mental effort.
Human performance depends on limited attention, working memory and feedback. Examine how the concept supports those processes during a task.
Does it make the relevant information perceptible? Can the user understand its meaning? Is the next action clear? Can they recognize whether that action succeeded?
Look for unnecessary steps, demands to remember information across screens and alerts that interrupt without helping a decision. The best change may simplify a sequence or improve feedback rather than add another feature. Confirm its effect through observation and appropriate measures.
Choose measures that reflect the priority outcome and the study’s purpose. These may include completion time, errors, requests for help, repeated actions or failure to notice important information.
Subjective workload measures can complement observed performance. NASA Task Load Index can help structure participants’ assessment of workload, while PURE provides an expert assessment of the effort required to complete tasks. Satisfaction ratings on a Likert scale can be used to compare concepts directly with each other and a baseline solution.
Do not treat one measure as a complete account of usability. Faster completion may accompany misunderstanding. A participant may complete the task correctly while reporting effort that makes repeated use impractical.
Interpret results together and examine the conditions under which they occurred. Record the limitations so decision makers understand what the test has established.
Pretotyping examines whether people take meaningful action toward using or adopting an idea before the full solution exists. It addresses a different question from whether a working product can be engineered.
A clearly described concept, service simulation or expression-of-interest process may provide evidence about engagement. The strength of that evidence depends on the action required and the conditions surrounding it.
A click demonstrates less commitment than a substantive implementation conversation. Neither establishes clinical efficacy or successful device use.
For medical concepts, keep representations accurate and make the test status clear. Interpret behavioral evidence alongside clinical appropriateness, access requirements and the responsibilities of the people making adoption decisions. Interest alone cannot establish that the solution should proceed unchanged, particularly when workflows in the clinical setting are involved.
A value proposition explains which customer the concept serves, the job it supports and the difficulties it intends to reduce. It should connect directly with the outcomes identified through research.
Compare that proposition with the evidence from concept tests. Did participants experience the intended benefit? Did another difficulty become more important? Did the concept require assumptions that the intended setting cannot support? Did the concept do something better than a competitor’s current solution?
Capture both positive and negative findings. Use them to revise the concept, the proposition or the team’s understanding of the need.
Then test the important changes. Iteration should answer a question left open by the previous round. Repeating sessions without changing the artifact or research objective can accumulate comments while leaving uncertainty untouched.
Early concept validation supports decisions about direction and investment. It does not establish all the evidence needed for a finished medical device.
Technical performance, reliability, clinical benefit and intended-use safety require appropriate subsequent work. A convincing simulated experience may depend on functions the team has not yet demonstrated.
Make these boundaries visible in the decision record. State who participated, what was tested, the conditions, findings and unresolved issues. Explain how those findings affect the next commitment.
Overall, having a “winning concept” in hand, backed by user Experience Café data along with user needs in the form of outcome statements formally structured with a direction of improvement and unit of measure, sets a development team up for success. The outcome statement user needs provide a solid foundation for the design history file.
Rapid prototype experience testing gives the team answers to key decisions and sets a target to pursue early on. This results in faster development cycles, more robust regulatory submissions, and better returns on investment spending.
A Value Management Office can connect this learning with resources and stage decisions. Testing should help the organization commit at a pace justified by evidence and concentrate effort on the uncertainties that govern progress.
“Early validation creates value when it changes the concept or the commitment before an unresolved assumption becomes expensive.”
Examine one proposed investment. Which assumption could defeat the concept, and what is the least costly credible way to test it?
Prepare an appropriate artifact, involve representative users and observe meaningful tasks. Review the evidence, revise the concept and record the next learning decision. This gives Patient Centered Design a practical route toward solutions people can successfully use and organizations can responsibly develop.
Discover better ways to do better work.
We alternate our own actionable articles with three relevant links from other authorities.
We’ll only use your email address for this newsletter. No sales callsDiscover better ways to do better work.
We alternate our own actionable articles with three relevant links from other authorities.
We’ll only use your email address for this newsletter. No sales calls