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

Culture | Language | Organisation | People | Process

View all articles SUBSCRIBE TO NEWSLETTER to get articles and more

STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates

Subscribe

Working between the silos

David Hodes

What are you accountable for? And what kind of authority do you have to properly acquit that accountability? Whom do you report to? How do you get inducted into the role? Who decides which tasks are to be done, of what type and by when?

Everyone craves clarity in their role. We want to know who makes decisions about hiring and firing from the team and who will do the appraisals. Who has the authority to negotiate pay, whether up or down? The classic job description often covers many aspects of your role. But what happens when you get assigned to a project outside of your functional home?

[Listen to audio version, read by David Hodes]

What is the relationship between you and a person in a horizontal business function who has a different boss to you? Who has authority when you need to get a task done for which you are held accountable, but for which you don’t have direct authority over the person you need to do the work? Job descriptions get hazy when it comes to the nature of the horizontal relationships between the silos. A prerequisite of effective collaboration is having a consistent means by which work is assigned from one part of the management accountability hierarchy to another without having to go to that place in the hierarchy to seek permission from the manager who spans both silos.

Elliott Jaques, a pioneer in organisational design, came up with the idea of TARRs and TIRRs, which stand for Task Assigning Role Relationships and Task Initiating Role Relationships.

Task Assigning Role Relationships (TARRs)

Let’s say Alice is Bob’s boss. Not only is she authorised to get Bob to do something but is also held accountable by her own manager for Bob’s output (and its quantity, quality and delivery time, within resources and procedures). These are the classic vertical relationships defined by the org chart.

Task Initiating Role Relationships (TIRRs)

Now imagine Alice is not Bob’s boss, but wants to initiate a task for which Bob is qualified. Usually it is Bob’s manager (not Alice) who is held accountable for whether or not Bob does the task, and is further held accountable for Bob’s output. TIRRs define who can ask what of whom when it’s outside of the vertical silo.

In this article, I’ll focus on the different types of horizontal relationships and how they contribute to running the business more effectively.

We’ve all come across ‘dotted line’ relationships where someone informally reports to a manager from another silo. But while Alice may be Bob’s senior (say she is a manager and Bob is a superintendent), in horizontal relationships she is often his peer and sometimes even his junior. By way of example, it’s clear that a military policeman of lowly rank can prevent a General from gaining access to a part of a military base, or a safety officer can instruct the CEO to don her personal protective equipment before entering a site. In most organisations, though, roles and responsibilities can quickly get tangled.

Fortunately, Jaques came up with seven different types of relationship that bring clarity: Advisory, Auditing, Collateral, Coordinative, Monitoring, Prescribing, and Service.

Let’s say Alice belongs to the Engineering function and is running a large project to implement a new asset management system. As such, she’ll need access to people from Production, Maintenance, Finance, IT, HR and the like. Alice’s position description contains nothing about her authority over the many people with whom she has to interact. The project affects the whole business and has been identified by the executive as critical to its future success.

“What happens when you get assigned to
a project outside of your functional home?”

As you read through these horizontal role relationships bear in mind that, once set in place, you no longer need to seek permission for every interaction you have from the manager of the person you wish to interact with. Moreover, that manager’s subordinate is obliged to cooperate to the extent required by the type of role relationship put in place. This can have a positive impact on productivity, as work can flow according to the structure and procedures made explicit by the role relationships. There is no need to wait and stop and start your task whilst waiting for permission to keep your work flowing.

Advisory: Alice is accountable for deciding on opportunities to help Bob by advising him and trying to persuade him to take that advice. Bob is accountable for deciding whether or not to take the advice. If he decides not to, then Alice is not authorised to go further. Bob has production targets to reach and has his own plan of how to go about reaching those targets in a safe, reliable and cost-effective way. He cannot merely dismiss the advice offered by Alice but is free to reject it once it has been properly considered.

Auditing: Alice is accountable for inspecting Bob’s work and deciding whether it is satisfactorily within limits. If Alice decides it isn’t, she has the authority to instruct Bob to stop that particular activity, and Bob must do so. For example, the new asset management system has improved standards for safety and the way maintenance engineers go about their tasks. If Bob has failed to take these new standards into account, Alice instructs him to stop until the new standards can be incorporated into his work.

Collateral: Alice and Bob are accountable for making mutual adjustments in their work in line with their manager’s context so that the best overall outcome for the business is achieved. The managers for Engineering and Maintenance have agreed on the asset management plans and have asked Alice and Bob to work out the ideal asset strategies to ensure they achieve the desired outcome contained in the plan. Alice might privilege reliability over cost whereas Bob might have a tight budget to work to, which doesn’t allow for all of what Alice would like to incorporate. The two of them work out a solution within the context set by their respective managers.

Coordinative: Alice not only has monitoring authority with respect to Bob and Bob’s peers, but also has the authority to bring them all together and try to persuade them to take a common course of action. Alice knows that to get the best bang for buck with the new asset management system she will have to get input from maintenance, operations, HR and IT. She decides that the best way to do this is to hold a series of workshops at which Bob and his peers will have to be present. She coordinates the meetings without further reference to Bob’s manager and all must do everything reasonable and possible to attend and contribute.

Monitoring: Alice is accountable for keeping abreast of what Bob is doing and for taking opportunities to persuade Bob to take alternative courses of action which Alice thinks are more in line with policy. If Bob does not accept Alice’s persuasion and she considers the matter to be serious, she must report to a higher authority. Alice has a schedule to complete the first phase of the project and is being held to account for its delivery. Failure to meet the schedule milestones would have serious implications for other aspects of the integration of her project with other projects currently running in the business. Bob feels under the pump with work assigned to him by his boss and has a natural tendency to do what he thinks will please his boss rather than what Alice is recommending. If Alice and Bob cannot agree, Alice is obliged to escalate, without any fear that she is dobbing in Bob.

Prescribing: If Alice judges that Bob is doing something that may have seriously destructive consequences, Alice has the authority to instruct Bob to carry out corrective activities, and he is accountable for doing so at the time prescribed. Alice does not have managerial accountability or authority with respect to Bob. She determines that Bob’s attitude to her project is having serious consequence across the whole of Bob’s function. He doesn’t like the asset management project, feeling that it’s interfering in his obligation to keep the plant running. He has told anyone who cares to listen that he will only do what Alice is calling for when it suits him.

Both the engineering and maintenance managers are resolute in their desire to get the new asset management system in place as soon as possible, knowing that the VP Operations, their mutual boss, has made clear it is a critical means for delivering his mandate of safety, volume and cost. To move matters along, Alice is equipped with a prescribing role relationship with respect to Bob who is then compelled to do what Alice calls for. Although Alice now has project authority over Bob, she does not have managerial authority or accountability—that role resides with the maintenance manager.

Service (getting and giving): The service-getter, Alice, has the authority to go to the service-giver, Bob, and to instruct him to provide an authorised service. Bob is accountable for providing the service unless he lacks the resources to do so, in which case he must indicate to Alice whether and when it will be possible to provide the authorised service. Alice goes to IT and asks them to stand up the new asset management software application and configure it in a way that is fit for purpose for the project’s User Acceptance Testing phase. There is a service-level agreement between Engineering and IT, which allows for the required service to be accomplished within seven days of an authorised request. IT receives the authorised request and apologises to Alice that due to an extraordinary workload and the absence of some critical staff members, they’ll only be able to stand up the application in three weeks.

Alice goes ballistic, releasing a tirade of unmentionable invective, and fires the IT manager on the spot. Fortunately for the IT manager, Alice is not his boss, and he has years of experience in dealing with colleagues who can’t believe it takes IT a week merely to turn on the switch of a new machine. ‘Just kidding,’ he replies when Alice finally calms down, ‘I can get it done in a day. We just implemented the TOC-based Dev Ops, and the difference it has made is awesome.’

The different types of horizontal relationships are summarised in the table below:

Elliott Jaques horizontal relationships matrix

It may sound like a lot of bother to define these horizontal relationships, but it’s worth investing the time in advance. The clarity you gain not only minimises headaches from personality clashes and unvoiced assumptions but prevents buck-passing and arse-covering. Do it for one key project, learn some lessons and adapt it to create the future standard. Best of all, removing the frustration and procrastination of the old ways of doing things leads to huge increases in engagement and productivity.

____________________________

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____________________________

    Spiral staircase
    [Background photo by Alain Pham on Unsplash]

    “A round man cannot be expected to fit in a square hole
    right away. He must have time to modify his shape”
    —Mark Twain

    ____________________________

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