Ensemble Ensemble
Menu
Home
  • SOLUTIONS
  • Method
    • A Systemic Approach
    • Theory of Constraints
    • Working with us
  • RESOURCES
    • Productivity Scorecard
    • Articles
    • MedTech
    • Subscribe
    • Our book
  • Results
  • ABOUT
    • The Just Work Manifesto
    • Our Story
    • Location
  • MedTech
Book a call
loader

Operations | Organisation | People | Process | Strategy

View all articles SUBSCRIBE TO NEWSLETTER to get articles and more

STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates

Subscribe

Act by Priority

David Hodes

Of all life’s gifts, time is the most precious. None of us escapes its clutches. As every minute ticks by, our quota is relentlessly reduced by that minute, then the next and the next. Prioritising how we spend our allotted time is one of our most consequential challenges.

[ Listen to audio version, read by David Hodes]

This is part 5 of the series. For more on this, see Part 1 | Part 2 | Part 3 | Part 4

Since most of us spend most of our non-sleeping time at work, let’s focus on the work arena and see how we might make a difference there. If we are to make a meaningful contribution to our organisations, either before we retire, or once it’s our turn to ‘hop the twig’, we clearly have to sift the important from the urgent and then act on those areas of highest leverage.

But how do we know what’s most important? How do we come to grips with what’s important today, and how that changes day to day, week to week and on into the longer horizons?

“Before even taking the first step to plan the work,
we must establish our goal”

If we are going to act by priority, it is essential that we have an understanding of the system as a whole, that system being the organisation within which we do our work. Let us restrict ourselves to thinking about a business, and understand that we generally organise work into strategic business units, and then into portfolios, programmes, projects, workplans and all the way down to tasks.

Those tasks, which are at the lowest level of the work breakdown structure, are how we give explicit instructions to specific people to fulfil a business requirement. The task or quantum packet of work may be part of a project or, equally, could be derived from the week’s production schedule. The tasks may be routine, such as participating in a regular meeting, or could be ad hoc when attending to something broken.

Establishing your goal

At every level of the business, then, we need to be aware of the two components of managing work—that is, planning and execution. Before even taking the first step to plan the work, we must establish our goal. At least how much of what by no later than when would be a good start. And since we are talking about a business, it will be framed in terms that everyone is familiar with—that is, to provide the shareholders with a sustainable and competitive return on investment. Setting this goal has to be priority number one, because if you don’t know where you’re going, anywhere will do. Establishing a realistic but achievable goal has the effect of aligning people and encourages them to think about what critical success factors will lead to its achievement.

Next comes the issue of how you are going to measure success. If the goal is to deliver a sustainable competitive return on investment, then you need to know how much profit you’re expected to generate and how much capital you’ll need to invest in getting you there. To deliver a healthy profit, clearly the bigger the margin between sales and costs, the better. And, to keep investment to a minimum, you want to minimise work in process by accelerating speed to market.

Now, we’re all set. We know what our system is, we have established a goal, and we’ve got ourselves some critical measures to track how we’re going relative to that goal. Then we encounter the laws of physics in the form of constraints. We can’t do everything; and, indeed, neither can we do all that we have chosen to do all at once. We have to prioritise. But how do we decide how to go about the process of prioritisation? What means can we use that will apply equally at the level of the business as it does through the whole chain of the work breakdown structure—from the portfolios through the programs, projects, workplans and tasks?

“The laws of physics make the idea
of limiting factors incontestable”

Theory of Constraints (TOC) is quite simple. It says that for all systems, the rate at which we create value is governed by very few limiting factors. Often, just one. If our system had no constraints at all, we would have a magical machine that could produce infinite widgets instantly. We would complete our projects’ critical paths in no time, manufacture our replenishment items in an instant and fulfil every request at the moment it’s made. The laws of physics make the idea of limiting factors incontestable. But, it’s easy to lose sight of what it means in reality. Often, a single constraint severely limits the throughput of a system. Prioritising work on the constraint is therefore of the essence when in pursuit of a high-performance result.

Non-constraints have capacity

There’s another profound—and counterintuitive—consequence that few consider. If we agree there is a constraint, then those people or machines that are not the constraint will, by definition, have capacity to spare. When you know where the constraint is at any given moment, you also see where you have reserve capacity. We should make every effort to deploy non-constrained resources in a systemic and systematic way to focus on supporting and collaborating with the prime resource assigned to work on the rate-determining activity.

Let’s take a simple example. Say there are two tasks to complete on a project, and one of them is on the critical path. The other has some slack. The one on the critical path could go faster if the person working on the one with the slack helped out. Thus, prioritising the work of the latter to help out the former is being systemically responsive to resource constraints. It may be the case that the latter’s KPIs are in jeopardy, but the prioritisation measure has to be to do what is best for the organisation as a whole. Or, as Deming put it, ‘The object of any component is to contribute its best to the system, not to maximise its own production […] Some components may operate at a loss themselves in order to optimise the whole system.’

As a prioritisation mechanism, there is a simple brilliance to the 5-Step FOCUS process used in the practice of the Theory of Constraints:

1. Find the constraint
2. Optimise it
3. Collaborate around the optimisation decision
4. Uplift the constraint
5. Start again

So let’s see if it can help us at all levels of the work breakdown structure. First up is the portfolio of work for the strategic business unit. However we select the work comprising the enterprise portfolio, it will make a demand on the human, material, information and financial resources of the business.

But what will the return be? Typically that is measured by looking at the NPV (net present value) of all future cash flows associated with each project in the portfolio. This method, on its own, is a poor way of prioritising, as it takes no heed of that fundamental of systems thinking—the existence of a constraint.

A much better means of prioritisation is to understand the portfolio constraint—that is, the resource with the highest ratio of load to capacity—then calculate the project octane of every project using this critically constrained resource. The project octane is a measure of how much throughput we generate per unit used of the critically constrained resource used.

If this prioritisation of the pipeline doesn’t deliver the desired organisational goal, then you can readily calculate how much more resource of which type do we need for how long to open the project pipeline sufficiently to deliver the requisite throughput. Applying a constraints-based approach to portfolio selection and prioritisation is the first big step to exceeding what you would otherwise think of as being reasonable and possible. It also sets up the programs of work in the right relationship with each other.

From critical path to critical chain

But, what about down at the project level? Well, we all know that the critical path determines the time it takes to complete a project. The longest chain of events from beginning to end. Or is it? Well, not quite. We have to once again take into account whether or not there are any resource constraints. If you’re in the happy position that you can get as many of whatever you need as the plan calls for, then the critical chain equals the critical path.

However, if we extend the lead time of the project by virtue of having to resolve contention for critically constrained resources, then we have a critical chain—a resource-levelled critical path. Through some intelligent management of task variation, we actually define the critical chain as the longest chain of events calculated at the average touch time for a task (eliminating any waiting time) with an aggregated buffer added to the longest chain, equal in time to half as long as that longest chain. Some workstreams feeding into the critical chain can have their own buffers.

What does this have to do with prioritisation? Well, in execution, we monitor not only the rate at which we complete the work on the chain but also the rate at which we consume the buffer. The relationship between the percentage completion of each at any given time is called the critical ratio, and it gives us a clear prioritisation signal for the number-one task. If by virtue of Murphy, a feeding chain has become longer than the critical chain, then that chain assumes the mantle of ‘penetrating chain’. Whether critical or penetrating chain, we can identify rapidly and unambiguously as the priority, the first task in the sequence which makes up the chain.

Production systems, through the use of Drum Buffer Rope (DBR), similarly uses the 5-Step FOCUS to produce a ‘drum’ schedule and execute against that schedule. Buffers are used in a similar way to Critical Chain to create a prioritisation signal. We divide the time between the release of raw materials and the production step on the drum into three zones—green, orange and red. We can keep track of whether or not a task is fully-kitted as it moves towards its targeted time at the drum. If we haven’t fully kitted, we have a means of creating a valid priority signal to the expediting team as to where to focus their efforts.

TOC provides a valid and scaleable answer to the question of how to work by priority, whether the prioritisation question concerns the daily assignment of the humble task or the strategic allocation of resources to the organisational portfolio. Along with the other four commandments of high-performance execution, the application of TOC can create the difference between failure and success—or between the ordinary and the remarkable.

Making mastery of TOC a priority of yours appears to me to be a sensible way to spend at least some of that limited time you have left.

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

____________________________

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:

  • download the brochure (no email required)
  • schedule a call
    ____________________________

    Watch on hand

    [Background image: Hourglass on log, Sahin Sezer Dincer on Unsplash]

     

     

     

     
    ____________________________

  • Organisation
  • People
  • Process
  • Strategy
  • Technology

An AI Enabled Mining and Metals Operating Model

David Hodes

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.


AI enabled mining and metals operating model: Requisite Organisation and human accountability across seven life-of-mine stages, supported by integrated knowledge and reasoning.
An integrated operating model across the life of mine, connecting human accountability, technical work and AI supported reasoning. Click the diagram to enlarge.

Requisite Organisation: put accountability where the work sits

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 and Resource Definition: reduce the uncertainty that matters

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 and Project Definition: shape options before locking in capital

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.”

Projects and Capex Delivery: keep the investment case alive

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.

Mining and Processing: manage the constraint governing saleable output

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.

Operations and Maintenance: protect the flow of value

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 Dam Remediation: connect obligations with operating decisions

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.

Decommissioning and Closure: design the legacy into the economics

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.

Integrated Knowledge and Reasoning: connect evidence with action

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.”


What’s next?

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.

READ MORE

  • MedTech

Validating medical device concepts before major investment

David Hodes

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.”

Begin with a question that can change the decision

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.

Choose the simplest useful representation

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.

Recruit people who represent the intended use

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.

Create an Experience Café around real tasks

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.

Listen without teaching away the problem

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.”

Examine the complete experience

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.

Make cognitive burden visible

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.

Measure effort alongside task success

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.

Test demand separately from technical feasibility

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.

Refine the value proposition with evidence

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.

Keep early findings within their proper limits

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.”


What comes next

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.

READ MORE

More than just work

Discover better ways to do better work.

Fresh insights, every Friday

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

    Subscribe to 'Perspectives'

    [recaptcha id:cf7note]

    More Than Just Work
    Weekly productivity insights

    Subscribe
    • EnsembleConsultingGroup
    • Share Page
    • +61 2 9387 3955
    • info@EnsembleConsultingGroup.com

    Site proudly designed by Brand Fibre

    What is to get in touch with you?



    More than just work

    Discover better ways to do better work.

    Fresh insights, every Friday

    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

    white_arrow white_bidirection_arrow arrow-right-green arrow-right-orange arrow-right arrow-left blue_arrow blue_round_arrow tick

    Want us to get in touch with you?

     
    Thank you for your interest. We will call you back.