STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates
How do we decide whether we should adopt a new technology? It needn’t be new to the world, but new to our organisation. After all, Peter Drucker noted that selling Eskimos a fridge to keep meat from freezing was a creative new use of current technology.
[ Listen to audio version, read by David Hodes]
This is Part 1 of our series on Six Technology Questions: Part 1 | Part 2
First, let’s cast our minds back a couple of decades. When the Y2K threat hit the world in the late 1990s, Eli Goldratt, along with Eli Schragenheim and Carol Ptak, wrote a novel, Necessary but Not Sufficient. The story revolved around a company that sells and develops ERP (Enterprise Resource Planning) software. In the process, we see that the fortune spent by companies looking to enhance performance while mitigating their Y2K risks was often money thrown down the drain.
The twin virtues the ERP salespeople were selling—risk mitigation and enterprise-wide process automation—may have been necessary for the desired outcome but, in the telling by the authors, they were by no means sufficient. The gap lay in what you did with the new technology once you had it. Merely automating the practices of the past would yield little for the cost and effort required for implementation.
Woven into its narrative, Goldratt’s novel presented four ‘new technology’ questions to which he later added two more. These six questions apply equally well to a new product, a new service, or the repurposing of an existing product for an original purpose, as with Drucker’s Eskimo example.
1. What is the power of the new technology? What are the boundaries where it will and will not work?
2. What current limitation or barrier does the new technology eliminate or vastly reduce?
3. What policies, norms or behaviour patterns do we use today to bypass the limitation?
4. What policies, norms and behaviour patterns should we use once the new technology is in place?
5. Given the above, what changes and additions to the new technology should we introduce?
6. How do we integrate the new technology with the overall strategy?
Since we are living through the age of Industry 4.0 and the digitalisation of the means of production, distribution and exchange, I’ll illustrate with an example from a recent assignment. I hope this will convey the power of these questions and encourage you to apply them to whatever technology change you are looking at adopting.
The problem we were trying to solve was how to determine and then control the right quantity of resources required to fulfil the scope of the large number of capital projects slated for execution over the following two years. Our client, a mining house, was planning on spending more than they had ever done before, and the senior management was acutely aware of the risk to the bottom line of both cost and schedule overrun.
They had the experience of using Critical Chain Project Management (CCPM) in their engineering function during the selection and design phases of the portfolio. As they got ready for the first of the pipeline of execution phases, they were staring into the mobilisation of thousands of tradies and associated management teams from a multiplicity of vendors.
Historically, they managed the articulation of resource needs on a variety of spreadsheets. A resource estimate plan, by craft, was prepared with each vendor. Each vendor’s resource plan had a tab with the quantity required by day and night shift for the duration of the given project. Another tab recorded the schedule of negotiated rates used for that vendor, by craft, by shift and the penalty rates applicable for weekend and public holiday work.
Planners passed the spreadsheets down from project to project, and there were inevitable errors in cross-casting and summing. Superintendents used these estimates to develop detailed budgets for the cost of these scopes of work and used those budgets to raise the necessary purchase orders once their managers approved the contracts.
These spreadsheets were sent by email attachment to the vendors, who replied in kind with spreadsheets of their own. Contained within them were the names of the people they had in mind to fulfil the approved project roles, along with a column to indicate they had the craft required to meet the need expressed in the resource plan. The project administrators routed the vendor spreadsheets to the training department for them to validate the qualifications of each candidate.
This vetting task was particularly onerous for anyone who had never worked on this site before, as the team had to vet all the quals by contacting the registered training organisation responsible for issuing them. On many occasions, the faded photo of a grubby certificate was the last remnant of a training organisation which had long since gone broke.
“What current limitation or barrier does the
new technology eliminate or vastly reduce?”
Even if the intrepid training team could validate the formal quals, there was still the hurdle of health and safety inductions onto site, monitoring of the mandatory renewal of technical and safety clearances, and recording of the issue of PPE and other prerequisites of being ‘good to go’.
Once the training team had completed their work, the job was back in the hands of the project administrators. Every week they would have to assemble thousands of records from the time and attendance system, download them into a spreadsheet and reconcile what was being demanded by the vendors against the client’s system of record. There were pivot tables, VLOOKUPs and all the tricks of the advanced Excel user. It was in any practical way impossible to multiply all the hours by the correct rate for any given person, add any overtime at the penalty rates and come up with a number they could confidently say represented a true reflection of the amount owing.
Historically, whenever there was a query about, for example, overtime worked by a specific contractor on a particular work package, the administrators would have to go back to paper-based timesheets, signed off by one of the supervisors at the prestart and end-of-shift meetings, sometimes days or even weeks before. These physical timesheets were kept by the vendor’s administrators, logged, batched and summed in yet another spreadsheet.
On many occasions, on such a large site, to make the best use of the contractors, it would be necessary to move them from one project to another. For example, once scaffolders had erected the scaffolding, they would have to wait for demolition before they could go in and dismantle. Meantime, another project could be in a prework phase looking for just such scaffolding capability. However, each project ran their own budgets, had their own purchase orders and needed their own supervisor signatures to validate that the individual in question had worked part of their day at the second work front.
“How do we integrate the new technology
with the overall strategy?”
It was not unknown for the more wily of the contractors to get two signatures, one from each supervisor and claim two full shifts of pay for one day’s work. But for the vigilance of the project administrators, the practice would have been far more commonplace than it was.
Of course, it wasn’t as if the vendors escaped the pain. When they got either the paper-based timesheets signed off by the supervisors or the electronic download from the time-and-attendance system, they had to code it for the employee ID within their systems before they could pay their staff.
Given this synopsis as context, we asked the first of the six questions, made up of two sub-questions:
We determined that, at a minimum, the new system should have the power to do the following:
• Forecast resource requirement for the next 12 months at an increasing resolution as we move closer to each project
• Develop a finite-schedule-based resource requirement for any given project
• Provide accurate contractor resource cost estimates for each project based on craft, shift and penalty rates
• Be able to assign individual contractor candidates to the open positions generated by our resource requirements ensuring the correct fit of qualifications held in the learning management system
• Determine what stage each candidate contractor is at in the mobilisation process and what we need to do to get them to be ‘good to go’
• Ensure that any time-based constraint on qualifications is notified well in advance
• Know who’s authorised as ‘good to go’ and who is on site on any given day
• Continuously monitor daily project load by craft against capacity provided
• Report daily on absenteeism
• Know which projects every contractor has worked on and for how long, on any given day
• Know which supervisor(s) they report to on any given day
• Determine every contractor’s swipe times from the moment they enter the premises until they leave and know how much of that time is chargeable to which project
• Instantly know how much we owe each vendor based on the contracted rates and swipe times
• Provide the vendors with a self-service capability to easily monitor time, attendance and value and, where possible, help them integrate it into their systems of record
• Know what has been invoiced by a vendor and what we have accrued for services performed but not yet invoiced
• Continuously monitor the variance of budgeted contract costs to actuals
Those are a lot of capability requirements to extract from two simple sub-questions making up the first of the six technology questions. Yet you can see how asking them leads to an understanding of what the ideal version of your new technology might do.
In the next article, we’ll look at some of the remaining questions. With these, we identify amongst other things, behavioural and policy changes that must be considered to leverage the value of your new technology.
Read Part II: Six Technology Questions: Part II
____________________________
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: Electronic board, Mathew Schwartz 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