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 | Process | Resources | Strategy

View all articles SUBSCRIBE TO NEWSLETTER to get articles and more

STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates

Subscribe

Practical Wisdom: Drum Buffer Rope

David Hodes

Think of a production system and you’ll probably conjure up some kind of assembly line. Whether you imagine humans or machines doing the work, this mental model feels wedded to manufacturing. It needn’t be—production principles are universal.

An airline’s check-in desk is part of a production line. So is the hospital’s procedure for admitting patients. Running scripts in software development is production. As is the sales pipeline that gets software to market. Insurance claims and loan applications? Production systems. And the barista in the café offers a vivid everyday production system—so obvious we almost don’t see it as such.

Perhaps we don’t naturally think of these examples as production environments because they don’t result in physical products that would hurt if you dropped it on your toe. But even the kind of heavy industrial environments we at Ensemble operate in offer plenty of counterintuitive examples, including:

  • managing technical service requests in an engineering environment
  • processing contractor applications for mobilisation to site
  • onboarding employees into vacant project positions
  • processing accounts payable and receivable

Drum Buffer Rope1

All these examples are production systems that benefit from a systemic approach. Let’s examine a simple process made up of four steps, each of which is linked to the other. And let’s say the capacity to do work for each step is as shown in the diagram. It doesn’t really matter what the process is, but let’s use technical notifications as an example.

Let’s say that the person at the first work-centre, an inspector, generates 20 notifications per day. The person at the second work-centre has the capacity to assess 14 of those notifications per day. The highly skilled planner can only manage to plan 10 notifications per day and, at the end of the process, back office has capacity to close out 20 notifications per day.

On the demand side, the manager of the process has been told to allow for a regular demand of 10 notifications per day. In the majority of cases, the manager would be looking very closely at costs and would wonder:

Why do I have all this extra capacity? The planner can only handle 10 units per day, so she’s the bottleneck. Yet this capacity perfectly meets demand.

So I’ll scale back the capacity of all the work-centres to 10. This will balance the system to match the demand while reducing costs by removing unneeded extra capacity.

The manager who thinks this way, trying to perfectly balance supply and demand across a connected sequence of steps is in for a nasty surprise. With the newly ‘balanced system’ (all work-centres at 10 capacity), production consistently falls short. Why? The manager discovers that common cause variation means that each of the steps in the process has only a 90% chance of processing their full quota of 10 notifications per day.

By the laws of statistics, the cumulative probability of getting ten completed is reduced to 90% to the power of 4—that is, 90% x 90% x90% x90%—or a cumulative 65%. In other words, almost one in three notifications would not be completed on time. The name of this statistical fact is covariance—when there are individual fluctuations between dependent events.

And of course, over in the real world of the plant, what if equipment failure increases and demand changes? If it’s lower than forecast, we end up with people standing round idle. While if it’s higher than forecast, we delay return to service.

First, find your constraint
If, as per the Theory of Constraints, systems are governed by their constraints, the first thing we must do, is to find the constraint. What’s yours? Do you know? Is it where it is because you’ve designed your value-creation engine to take advantage of the laws of physics? Or are you forever its victim, watching it turn up, unannounced, in a different place every day…like whack-a-mole?

Once we find our constraint, if we want to optimise its performance for value creation. How can we go about doing that?

The TOC approach to managing production systems is called Drum Buffer Rope (DBR). Let’s take a closer look at how Dr Eli Goldratt, the physicist founder of the method came up with such a name.

Drum Buffer Rope2

The constraint in our example is the planner, who can only plan 10 jobs per day. We call this bottleneck resource the drum, because it beats the rhythm of value creation. The power of the solution lies in the fact that a 10% gain at the drum is a 10% gain for the system as a whole. That is, 10% more capacity for the planner means 10% more production for the whole maintenance system. 10% more production for the maintenance system means less downtime, more reliable performance and more throughput. By the same logic, increasing the capacity of a non-constraint by 10% has no positive effect on the system and, in fact, may produce a negative effect by increasing the backlog and stress at the bottleneck.

“A 10% gain at the drum is a 10%
gain for the system as a whole”

In most cases, the value of that gain in throughput dwarfs whatever gain there might be in micromanaging the operating expense of each component part. Moreover, designing your production around your drum lets you use it as a synchronisation tool for the whole—everyone marches to the same drum beat. And, it bears repeating, because by definition everyone has more capacity than the drum, 10% gained at the drum is 10% gained for the system as a whole.

Understanding this requires a mindset shift. Everyone has to play as one band. If the drum is starved because the upstream process was goofing off or produced the wrong component, the whole system loses out. So how do we ensure that the drum never runs out of work? Well, we place a buffer in front of it. This buffer is in effect the stored capacity of the upstream functions. We want to size the buffer so that it’s not so big as to flood the engine with work in progress, but not so small that the drum misses a beat because it’s starved. This is why everyone on the team has to understand the idea of supporting the constraint—their colleagues working at the drum.

To keep the size of the buffer right, we tie a rope to the release of inputs at the entry point to our engine. The buffer is sized to be big enough to accommodate the time it takes from the input step until it is ready to be processed by the drum. As soon as the drum has begun work on the buffer, it gives a tug on the rope to release the next work packet, such that it arrives in good time to keep the whole value-creation engine running smoothly.

And, yes, the rope means that occasionally those working in non-constrained work-centres will be asked to slow down, or even stop work, so as not to flood the engine. This is profoundly counter-intuitive to our natural assumption of what it means to be ‘productive’.

With our drum-buffer-rope system in place, we give our system its best chance of 10 out of 10 performance. At this point, there is no way to squeeze more juice out of the system in its current configuration. If we want to uplift the system now, we need to invest in additional resources. Most organisations jump straight to this step long before they need to—and often with unintended consequences.

Drum Buffer Rope3

Adding another planner at the drum takes the combined uplifted capacity to 20 jobs, which is at first glance more than the plant demands. The internal constraint of the production system has become external. It’s time to find new tasks to which we can put this hitherto hidden capacity. Could we encourage the team to be more proactive in bringing innovation to their work? How might they use the time dividend released to contribute to ensuring that ever shorter turn-times deliver ever more throughput—reliably, on time and at the requisite quality?

Let’s recap the steps to implementing DBR—one of the twentieth century’s least known, but most effective, innovations in productivity:

  1. Establish your process flow
  2. Quantify the capacity available at each process step based on the demand for each unit of production
  3. Find which process step represents the bottleneck to overall process productivity and declare it the ‘drum’
  4. Establish how long it takes for work to flow from the start of the process to the drum, then create a ‘buffer’ that keeps the drum fed for at least that lead-time
  5. Develop a mechanism to signal release of the inputs by tying a ‘rope’ from the drum to input release
  6. Monitor when the drum is running at or near systemic capacity (say 80% of maximum nameplate) and prepare to uplift system capacity and reassign the drum

One final note. It is a tragic truth that most managerial leaders are all too keen to use the productivity gain of DBR to fire people who they believe are now surplus to their requirements. This mindset completely misunderstands the ‘systems thinking’ approach to improving production. Firing people may provide a short-term cost-saving, but is foolish in the medium- and long-term if you want to develop a culture of continuous improvement which, after all, is the only way you can sustainably compete. Why would employees wish to improve production if they knew that in doing so, they would be putting their own jobs at risk?

To accomplish the principles of Just Work—in which everyone has the right to be well-managed—we must rather tap into aspiration and imagination. Do the hard yards of gaining the trust of your workforce to co-create better ways to do better work.

____________________________

The Theory of Constraints offers a new operating system fit for our complex world of change. To learn what that operating system might look like, we invite you to download our Executive Guide to Critical Chain Project Management [PDF].

The change of mindset 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. Just as astronauts need a few zero-gravity rides in a special aircraft before they experience the real thing in space, the game simulates the effects of TOC. We call it The Right Stuff workshop and we’d love to run it with you.

____________________________

Coffee smarts[Background photo: ‘Coffee smarts’ by Nathan Dumlao on Unsplash]

“Every situation, no matter how complex
it initially looks, is exceedingly simple”
—Eliyahu Goldratt

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