STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates
All improvement is change, but not all change is improvement. Organisations typically change because they want to improve their competitive advantage. How do we give ourselves the best possible chance of success?
[Listen to audio version, read by David Hodes]
Change resides in the domain of projects and project management. We most often think of the word project as a noun. But treat the word as a verb and we get a more accurate rendition of what projects are there to do—that is, to project a vision of an improvement into the future.
Even the simplest of businesses have many projects running at any given time, whether formally recognised or not. Larger organisations encompass marketing, business development, product and service development, technology, capital, business improvement, finance, HR and the list goes on. More sophisticated organisations govern many, if not all, of these initiatives through a Project Management Office, or PMO. These PMOs are usually organised along the lines of an accepted Project Management Body of Knowledge (PMBoK) and will cover areas such as scope, cost, schedule, communications, HR, risk, quality, procurement, stakeholder engagement and integration.
For what they do, PMOs are neither good nor bad; it depends on the capability of the executives charged with the managerial leadership of the function, and how much authority they have to define and fulfil its mandate. My experience, though, has taught me that the whole idea of a PMO is a necessary but not sufficient condition for delivering value. Those charged with running PMOs easily get side-tracked into getting better and better at their technical proficiency in planning and executing projects while losing sight of the value such projects are there to deliver. Or, as one wit put it, ‘great landing, wrong airport’.
“A PMO is a necessary but not sufficient
condition for delivering value”
Since all TOC implementations are projects, I have long wrestled with the conundrum of how TOC fits into the world of project management. On the one hand there is the obvious connection to Critical Chain Project Management, but on the other, there is so much more: Drum Buffer Rope, The Replenishment Solution, the Logical Thinking Process, Constraint Accounting. And then there is the deep question of how to bring these innovations in productivity into the day to day—how people learn how to use the methods and tools and what kind of organisational design liberates the full flow of value contained in the science of the theory.
Delivering value at scale
A few years ago, I developed a new model for the traditional PMO and called it the Value Management Office, or VMO. The primary purpose of the VMO, as its name implies, is to deliver value. Its architecture is designed to be scalable. At the highest level, it defines and governs global processes for all initiatives and projects. As the ultimate repository of value initiatives, it provides the framework, processes and capabilities required to ensure that the right initiatives are chosen and prioritised from amongst the many, and that they are successfully led and managed to their conclusion.
Importantly, the conclusion of any given initiative may not be the delivery of the end-product or service. Within the VMO resides the governance mechanism to define the stage-gates which articulate deliverables for each stage and ensure cancellation or delay if circumstances prove the initial assumptions invalid. Stage-gates are where projects go to die when they are no longer able to carry the burden of their initial expectations.
Furthermore, a critical part of the VMO is the idea of benefits tracking—that is, ensuring that what was promised as an improvement is actually delivered; and if not, then why. In a fundamental way, the VMO is an instrument of organisational learning and systems thinking that looks not only to improve on the given way of doing work, but to ask the question about how to continuously innovate for better ways. These better ways can be achieved through questioning assumptions about existing methods or inventing new methods based on a vision of what the future can teach us.
At Ensemble, we have designed the VMO with twelve interacting panels—akin to the instrumentation of a complex piece of technology.
These twelve tiles are grouped together under four major themes:

In a final grouping together, these four pillars of the VMO resolve into the central idea of ‘Plan the Work’ and ‘Work the Plan’.
Let’s take a closer look at the individual tiles and try to understand them through the questions each tile is designed to resolve:
| Phase | Tile | Questions |
|---|---|---|
| DEFINITION | Governance & Standards | - Who’s in charge? - Under what authority? - How do policies get set, implemented and changed? |
| Context, Purpose & Scope | - How does the project fit into the bigger picture? - Why do it at all? - What’s in and what’s out? |
|
| ICT Management & Version Control | - What technology will help you plan and perform the work? - How do you control files, code and other project artefacts? |
|
| PREPARATION | Learning, Leadership & Culture | - How will you inspire your teams to learn together? - How will new ways of working be accepted into your culture? |
| Mindset & Behaviour Analytics | - How can you objectively assess team performance? - How do high-performance teams think, feel and act? |
|
| Accountability Hierarchies | - From CEO to frontline, who carries the can? - How do you give people ownership, yet keep control? |
|
| OPTIMISATION | Planning, Scheduling & Process Management | - How do you decide who works on what? - By when? - How do you define and control the development of processes? |
| Resource Management | - What capabilities do you need in your project pool? - How will people come on and off the project? - At what cost? |
|
| Scenario Testing | - Scope, cost, schedule? How do you decide the best trade-offs? - Which scenarios are most relevant to the business needs? |
|
| PERFORMANCE | Ways of Working | - How do you keep everyone in sync? - What are your meeting rituals? - Who attends? - When, and why? |
| Reporting & Analytics | - How do you instrument and control the creation of value? - How do you use data to improve performance? |
|
| Requirements & deliverables tracking | - How do you map completed work to required outcomes? - How do you manage changes to the baseline plan? |
To systemically improve production, Theory of Constraints itself is necessary but not sufficient. To harness its power, it’s best to systematically address all the core ideas contained in the tiles, which represent an operating system for your organisation. By design, you would want an overarching VMO that acts as the repository of standards, processes, governance and knowledge for the organisation as a whole. The architecture of a VMO should allow for strategic business units to have their own satellite VMOs, responsible for maintaining systemwide standards, but developing documentation and guidelines specific to those units where deemed necessary.
Standardisation is not about everyone marching in lockstep within a mechanical system but rather about serving the higher objectives. Think of it as moving up a ladder of capability. You want to put foundations in place that can apply to the next project so people don’t have to reinvent that part of the system every time. Musicians build their technique through scales, arpeggios and etudes but the goal is to use them to help make music. Formalising elements of the operating system expressed in the VMO tiles creates better soil in which ideas and people can learn and grow.
One of the problems of trying to organise work is that of classification. It exists in every sphere of life. Think of a library of books. You can store them by author, by title, by year published, by genre, by language, by number of pages, by the colour of the cover, by the type of paper it’s printed on, by the font used, by author’s birthday, by popularity, by physical size, and on and on it goes. To store and retrieve books in a consistent, universally usable way was a problem largely solved in the nineteenth century by Melvil Dewey and his Dewey Decimal Classification.
“The VMO turns theory into practice
while measuring tangible business benefits”
Unfortunately, there’s no universal agreement on the perfect way to order the world of work. I view the system of the VMO as a constant work in process. If your processes are too rigid and try to cover every eventuality, the organisation becomes sclerotic, unable to improvise when a new situation inevitably occurs. But if you put off the work of defining standards, you lurch from one crisis to the next, never leaving the realm of the chaotic. Jazz musicians typically decide in advance on structure and tempo by choosing a tune and counting it off. They are then free to create something new together.
Building the learning organisation
As I wrote above, the VMO is an artefact of the learning organisation and is therefore subject to the well-worn rhythm of the plan-do-check-act cycle. It’s a theory of how to organise a better way to do better work. And, as the doyen of systems thinking, W Edwards Deming, put it: ‘Experience by itself teaches nothing. […] Without theory, experience has no meaning. Without theory, one has no questions to ask. Hence, without theory, there is no learning.’
The VMO turns theory into practice while measuring tangible business benefits, such as the realisation of value through increased throughput, lower operating expense, superior ROI, faster speed to market and more reliable delivery to promise.
To take the first step down this route, you could get together with a colleague or two and go through all twelve tiles. Simply ask yourselves the questions, noting how you currently address these issues—and how consistently successful your organisation is at handling them.
____________________________
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:
____________________________

“Try not to become a man of success,
but rather try to become a man of value”
—Albert Einstein
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