The real cost of any decision is what you forego by making that choice. In economics, the cost of a decision based on the cost of the next best option is called the opportunity cost. At its most poetic, Henry David Thoreau put it thus: ‘the price of anything is the amount of life you pay for it’.
At first blush that may seem a little extreme, but it is a truth. We are all finite beings and will one day run out of life. Time really is the ultimate constraint. If we had an infinite amount of time, we could do everything we desired and have time left over to enjoy it all.
Over the last few articles of this series, we have looked at two-tier scheduling, the resource management problem and the direction of a solution, as well as the structure of the VMO (value management office) to bring these innovations in schedule and resource management into being. All these components play a part in delivering more of your goal within the time you have available to do it. However, as necessary as they are to optimising individual projects, by themselves, they are not sufficient to make more intelligent decisions between the different initiatives arising from your strategy and business plan.
In the world of finance, portfolio management is the art and science of making decisions about investment mix and policy, matching investments to objectives, asset allocation for individuals and institutions, and balancing risk against performance. Project portfolio management (PPM) refers to a process used by project management organisations to analyse the potential return on undertaking a project. Managers can use PPM to see the big picture and make decisions about what’s out and what’s in.
‘The price of anything is the amount of
life you pay for it’—Henry David Thoreau
In both the world of finance and the world of projects, the goal is to maximise the return on resources invested in creating value from an idea. Typically, this will be calculated using two related ideas: the net present value (NPV) and the internal rate of return (IRR). The idea behind NPV is to calculate all of the cash flowing in and out of your investment over a predetermined time to tell you what those flows are worth if all of it were converted into a single equivalent capital amount today.
The NPV on any given project is heavily dependent on the assumptions of the positive and negative cash flows, as well as the rate of interest used to discount the value of the money you will only realise in the future. Hence, the technique used to determine NPV is called ‘discounted cash flow’. IRR is related to NPV in that the IRR is a target baseline discount (interest) rate that calculates the net present value (NPV) of all future cash flows from a particular project to come out as zero. Therefore, if you can achieve more than the internal rate of return, the project is—technically, at least—worth taking on.
Working with limiting factors
As described in my recent article on constraint accounting, no less a figure than the late Stanford Professor Charles T Horngren stated that ‘relevant information is the predicted future costs and revenues that will differ among alternative actions. The existence of a limiting factor changes the basic assumptions underlying the cost and revenue opportunity of a particular action.’ Thus, if the particular ‘action’ we are talking about is selecting which projects from a portfolio will deliver the best return on investment, then rank ordering on the basis of NPV is not sufficient.
What we need to do to properly evaluate the best decision, based on Horngren’s idea of a ‘limiting factor’ is to introduce the idea of project octane. What I mean by project octane is how much NPV the project delivers for per unit of the critically constrained resource (CCR). Because projects are always competing for finite resources.
Let’s imagine you are evaluating a portfolio of 10 projects, each of which has been evaluated on the basis of its NPV. You are satisfied with the assumptions your team have made with regards to the value each project will deliver and they have been very diligent with their scheduling. You are able to drill into all resource requirements and what they have produced confirms your intuition that the critically constrained resource is your pool of solution architects. You can readily ramp up all other resource types but, for the technology platform you are using, you are simply unable to contract more than 80 solution architects.
When you first look at the portfolio, it looks like the table below:
Scenario 1:

Based on the availability of only 80 of your critically constrained resource (CCR), we can only, strictly speaking, do the first two projects, and at a squeeze, perhaps get the third one in. Total NPV for the executable portfolio is therefore between $1.9bn and $2.7bn.
Scenario 2:
If however you add to the table the project octane for each project—that is, how much NPV is delivered for each unit of the CCR—and then rank them according to the octane, you end up with a very different scenario and value proposition:

If the number of available solution architects is truly your only constraint, you could run all the projects in green in parallel. In this case, only the last project cannot be completed. Therefore, the total NPV is $4.5bn, or a 67% improvement on scenario 1. Project 10, with its billion-dollar NPV, looked very attractive. Looking at project octane helps us see where true value lies.
In the diagram above we can visualise this octane idea by plotting each project against two axes—the x axis representing the NPV and the y axis the project octane. The red lines indicate the average NPV and the average octane across all ten projects.
Quadrant 1: DYNAMO. These are the most desirable projects to do. They deliver the highest NPV and also have a high octane—that is, they are relatively low on consumption of the CCR and thus deliver a high bang for buck invested in them.
Quadrant 2: DREAMER. These projects have a relatively high octane (good bang for buck for the use of the CCR), but don’t generate enough NPV to move them into quadrant one. Some questions you could ask about these projects are: what can be done to increase the revenue (benefits) from these projects? If it’s a product or service offering, for example, would lowering the price lead to a significant and disproportionate increase in sales volume?
Quadrant 3: DELIVERER. These projects generate a relatively high NPV, but they are also proportionately more consumptive of the CCR than those projects in quadrant one. The question to ask of the projects in this quadrant is: what can be done to offload some or most of the work onto resources which are not as constrained as the solution architects? Perhaps the work can be looked at more closely and the constraint mantra applied: ‘let the constraint do only that which only the constraint can do’. What can be delegated to people who can support the CCR and thus liberate their capacity to do only that which only they can do?
Quadrant 4: DEADBEAT. As one wit put it, the projects in quadrant four are not only the dogs but are the fleas on the dogs! There would be two rounds of heavy-lifting to do to make these projects more attractive: increase the benefits and reduce the consumption of the CCR. It may be possible. But, once again, you have to ask yourself the opportunity cost question: where is your limited attention better spent? On the high-value projects or on wrestling the recalcitrant into submission?
I have found that the idea of project octane doesn’t have to be as quantitatively precise as expressed in these charts. It is best to set the intention to rise to a level of project maturity that makes the quantitative assessment second nature. But the truth is that good managers can usually get a pretty solid intuitive idea of octane without having to do the numbers. Just think about how ‘sticky’ or ‘viscous’ the project seems.
You would know that the numbers you get from a pure NPV calculation make you scratch your head and intuit that there is something not quite right—your critically constrained resources are spending too much time on a project when they could be cranking out a lot more, in a far more streamlined fashion, if allowed to work on those projects which consume less of their precious time. Using all of the tools that come from the ability to quantitatively articulate the load of your portfolio of work and the capacity available to deliver it can end up making you a lot more money, both now and in the future.
There is, of course, another option—the ‘uplift’ step of the 5-Step FOCUS. As one TOC guru put it, ‘when you’ve squeezed all the blood from a stone…get more stones’. Having the ability to quantitatively articulate the demand for resources, by type, in time and place, gives you the ability to pinpoint any further investment in capacity to provide the greatest leverage in value.
____________________________
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 photo: ‘Umbrellas’ by Ricardo Resende on Unsplash]
“Efficiency is doing things right;
effectiveness is doing the right things”
—Peter Drucker
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