STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates
Releasing new work at the rate you’re completing old work is one of the most productivity-enhancing actions you can take, and yet equally, one of the most challenging improvements to accomplish.
[ Listen to audio version, read by David Hodes]
This is part 3 of the series. For more on this, see Part 1 | Part 2 | Part 4 | Part 5
If we know we are paying for a service by the hour, we like to think we are dutiful when we ensure we keep the providers of that service busy. It matters not if the provider is an employee or a contractor; the mental model is that busyness equates to, or at least somehow correlates with, value. Withholding work from a crew who would otherwise be idle seems almost sacrilege. Thus, ensuring all have work piled in front of them should be an axiomatic virtue built, in whole cloth, from the Protestant work ethic.
“Withholding work from a crew who would
otherwise be idle seems almost sacrilege”
It’s all very well being busy, but the difficulty arises, though, when faced with a variety of work options, as to where to focus your effort. If each discrete piece of work is considered a master to the labourer, then the inclination is to keep each of those masters at least somewhat happy. You never know who is going to ask for a progress report, nor when they might ask that question. So, if you can demonstrate at least some progress since the question of progress was last asked, you provide some protection from blame.
Furthermore, no man (or woman for that matter) is an island, and there is the issue of coordination of work coming from different sources, each with their own dependencies and deadlines. How do you come to know the correct sequence of work which will maximise benefits, minimise costs and keep the customer happy enough to continue coming back for more? If everything is thrown at you as soon as it’s ready from an upstream process, your island will quickly be overwhelmed by the tsunami of the push of work.
Expressed a little more formally, we know from Little’s Law that the long-term average quantity L of inventory in a stationary system is equal to the long-term average effective arrival rate λ multiplied by the average time W that the inventory spends in the system. Expressed algebraically the law is:
Although the formula looks intuitively simple, it is quite a remarkable result, as the relationship is ‘not influenced by the arrival process distribution, the service distribution, the service order, or practically anything else’.
If we think of inventory as being the number of tasks in our work queue, it’s pretty evident that if we have an optimum rate of processing that work—and the rate of arrival of work is faster than the rate at which we process it—then we will have a buildup of inventory. And then we’re into a vicious circle in that the more inventory we have in the system, the lower the likelihood that the worker will be in flow, and the lower the rate of task completion.
Why would productivity suffer when there is a surplus of new tasks arriving faster than the rate at which we can complete the existing tasks? The truth is that we are not well equipped to deal with rapid switching between tasks, otherwise known as multitasking. The part of our brains accountable for executive function, and hence the planning and execution of tasks, is the prefrontal cortex. It’s the most recently evolved part, and it’s not especially big. Think of it as the central processor, having to call whatever is to be worked on into its rather crowded memory bank.
Every time a new task arrives, time is lost in putting down the existing work, assessing the new piece, kitting the mind with whatever it needs to draw on from the deeper recesses of memory and then executing according to whatever drives your sense of priority. Sometimes the decision may be to not change tasks. However, the effort in making the decision still robs the existing task of the benefit of its manager’s ability to work in flow, to focus, and to finish before assessing what to do next.
To test and prove the impact of multitasking on productivity, you can do the very quick experiment outlined below.
– You have been assigned to a program, composed of 3 projects, to be finished ASAP and with high quality.
– The goal for Project 1 is to write 20 letters in alphabetic order from A to T
– The goal for Project 2 is to draw 20 symbols in this repeating sequence:
-The goal for Project 3 is to write numbers from 1 to 20
In the first test, we are going to try to keep all three project managers a little bit happy. Thus, take a blank sheet of paper and divide it into three columns, headed Project 1, Project 2 and Project 3. Now find a stopwatch. (Go ahead, I’ll wait.)
When you are ready, press ‘Go’ on your stopwatch and work across each row: A, followed by ∆, followed by 1; then B followed by O, followed by 2 and so on, all the way until you have got to the row you fill with T, followed by ∞, followed by 20. It’s essential to work across the rows as you make your way down the columns. As soon as you’re done completing all the cells, record the finish time from your stopwatch.
For the second test, we want to simulate working in flow, without forcing the brain to change continually between letters, symbols and numbers. Thus, once again mark up a blank piece of paper with three columns, headed Project 1, Project 2 and Project 3. Start your stopwatch and go down the whole of column 1, marking off all the letters from A to T, before moving across to the repeating pattern of symbols. Once you have placed the infinity symbol in the last box, jump over to Project 3 and complete the column with numbers 1 through 20. Once again, as soon as you have completed the entries into all the cells, record the finish time on the stopwatch.
I would be very surprised if you took longer working in flow than you did when multitasking. Even when you are in the process of completing each box, when executing the multitasking option, you can feel the brain-strain of switching from letter to symbol to number and back again. By contrast, when working in flow, there is far less mental effort running through first the alphabet, then a symbolic sequence and finally a logical numeric one.
Think of your work as soft rubber balls flowing through a well-oiled pipe, in the middle of which is a valve. Imagine that the valve has a diameter which is 25% smaller than the pipe on either side of it. At the beginning of the flow, you’ve installed a bloody great pump, calibrated to deliver a steady flow of these soft rubber balls, based on the diameter of the pipe—not the valve. Pretty soon, you’re going to gum up the works, and the whole system will come to a standstill, smashing the pump, breaking the valve or puncturing the pipe—perhaps all three.
Wouldn’t it be better to have a pump controlled by the rate at which the squishy balls exited the valve? Wouldn’t you want to have the release of new work tied by a rope to the exit of existing work from the production system? To achieve this end, you have to control work release. It allows the people who have started work, to focus and finish it—provided, of course, they are fully kitted and are working off true data.
You enable production flow by matching the release of work to the capacity of the system constraint—the bottleneck. In Theory of Constraints (TOC), we call this bottleneck the ‘drum’ because its beat synchronises all parts of the whole. Push work into the system faster than the drum can complete it and you create a logjam. Release work too slowly and the drum misses a beat. Flow stutters and production drops for minutes or hours, with the inevitable consequence of degraded performance.
When you know the capacity of the drum, you can release the appropriate amount of work to keep things flowing through the bottleneck at the optimum speed. TOC’s production and project management systems—Drum Buffer Rope and Critical Chain—were invented to solve the challenge of releasing work in the Goldilocks zone: not too much, not too little, but just right.
But, a sound method is not enough. So important is the idea of the control of work release and its companion idea of full kitting, that each of those activities should separately have a manager with these specific accountabilities included in their job role. The work-release manager depends on the full-kitting manager to have everything ready for the timeline dictated by the schedule. Crucially, the work-release manager must have the full authority to prevent work from starting whenever he or she knows that whoever is allocated a task cannot complete it.
You now appreciate why releasing new work at the rate you’re completing old work is one of the most productivity-enhancing actions you can take. So why is it so challenging to accomplish?
Most of us have no trouble, in theory, of grasping the concept of controlling the flow of work. In practice, however, it’s remarkably difficult to convince our own brains not to jump from task to task—despite the knowledge that we’re hobbling our productivity. If we struggle even with tasks we’ve assigned ourselves, imagine how much harder it is to manage the flow of work through our whole system—and actually encourage those working at non-constrained points to mindfully manage their slack.
To know what work to control, and how to control it, as a start, use the 5-Step FOCUS to identify and optimise the constraint. Then take time out to think about how you would implement the 5 Commandments of High Performance Execution. Previously we covered Maintain True Data and Work Fully Kitted. We’ll have a more detailed look at the other two commandments in the last two articles in this series: ‘Resolve Issues Rapidly’ and ‘Act by Priority’.
____________________________
This article is part of our series: Five commandments for high-performance execution
Part 1: Maintain True Data
Part 2: Work Fully Kitted
Part 3: Control Work Release
Part 4: Resolve Issues Rapidly
Part 5: Act by Priority
____________________________
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: Traffic Lights, Tim Gouw 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