STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates
Collaboration has progressed from a buzzword to an article of faith in today’s organisations. Books talk about how to do it better and tools claim to make it ever easier to share ideas and plan projects. But what task are you collaborating on?
Something so simple, and yet something so often neglected—how to properly define a task. If you want to markedly improve productivity without anything other than the content of your own mind, it will pay to pay attention to the proper definition of a task.
[Listen to audio version, read by David Hodes]
But first, let’s get our language standardised. We have no issue when applying our minds to the hard sciences about the need for precision in language. A volt, an ohm and an ampere have very precise meanings and can be measured in a consistent way at any point in time and in any given place. Whether you have travelled to the moon or are in Outer Mongolia, at the bottom of the Pacific Ocean or the top of Mount Everest, the meaning and measurement of these physical properties of electricity are always the same. So, what about the terms we use when we go to work? What is work? How is it different from a task? How do you measure it? Is it similar in any way to the definition used by physicists: the product of the force applied and the distance over which it has been applied?
The late Elliott Jaques spent a lifetime using his professional skills as a psychoanalyst to give us an entire framework for understanding work in a way which allows us to derive tremendous value. It forms a part of his major contribution to the field of organisational design, Stratified Systems Theory, which he codified in his book Requisite Organisation. In that book, he gave us the following definitions:
Task: An assignment to produce specified output (including quantity and quality) within a targeted completion time, with allocated resources and within specified limits (policies, procedures etc)
Role: The position occupied in the organisation
Work: What the person has to do in order to achieve the task: use judgement and make decisions in overcoming obstacles
The focus of this article will be on how we go about defining a task, consistent with Jaques’s framework. Having the discipline to correctly and fully define a task is a prerequisite of achieving the ideal of what I call Just Work—that everyone has the right to be well managed. Amongst other things, being well managed means that people have a right to understand the context of any given task—how it fits into the bigger picture and what difference it could make to the longer horizon.
It is critical for them to know why you are calling for the task to be done. What is the purpose of the work in every circumstance a task is assigned, whether to shovel a piece of dirt or develop a new mine? What outcomes are you looking for when you issue the instruction, in terms of both the quality to which it is to be produced and the quantity required? Is it a single prototype to be used in a proof of concept or is it a final design for mass production of the first million units? What resources will be required to complete the task, be they human, material, financial or information? And by when would you like the work to be completed?
The answer to these questions represents the minimum necessary set of instructions required for anyone to reliably and successfully complete tasks assigned to them. They can be summarised in the acronym CPORT or:
C – Context
P – Purpose
O – Outcome in terms of quality and quantity
R – Resources
T – Timing
In my experience, people are quite poor at providing clarity on each of these dimensions. In addition, whilst each is a necessary condition for successfully assigning a task, individually they are insufficient to ensure consistent outcomes. Only once you have considered and communicated each dimension can you claim to have fulfilled your obligation to the idea of everyone having the right to be well managed.
Jaques discovered that complexity is correlated with the time horizon of the task being considered. These horizons can be arranged into time spans that reflect the cognitive ability required to effectively complete the given task. With each horizon, there is a distinct mode of thinking that is as different one from the other as ice is from water and water is from steam. A feature of the CPORT is that it can be used to define a task at any of Jaques’s levels of work.
The table below shows the horizon of work, the level (what Jaques calls a stratum), the mental process involved and the related position in the hierarchy of a commercial or military organisation:

You will notice in the table that the mental processes repeat themselves from stratum V to stratum VIII. It is analogous to a note played on the piano, followed by one played an octave higher. They both share fundamental characteristics but are nevertheless different in their nature. This is because the object of the mental processing has moved from the task of the individual as a unit within the stratum to the single business unit within the larger enterprise.
From stratum I-IV, the mental processing is largely symbolic and verbal and addresses the specific case in hand, such as the business or military unit. From strata V to VIII it is conceptual and abstract, meaning that the thinking generally involves the class of problem being solved and how the specific instance can be understood as but an example of the general case.
Here’s one for someone at stratum one:
THE TASK
Inspect and repair pump #1234
Context: As we operate a plant which requires fluids containing corrosive mineral elements to be pumped around the purification circuit, we need to regularly maintain those pumps to avoid unplanned breakdowns. Our reliability engineers have determined the optimum interval for inspections of all pumps and developed a task list to repair or replace them if they are at the end of their planned life or if any faults are found.
Purpose: The purpose of the task is to ensure the safe and reliable operation of the pump.
Outcomes: The following outcomes are required for this task.
Resources: The following resource will be required to complete this work.
Timing: The inspection and repair of the pump must be completed no later than 25th July, 2019.
By way of contrast and as an example, what might a stratum four CPORT look like?
THE TASK
Implement Theory of Constraints scheduling methods of Critical Chain Project Management (CCPM) and Drum Buffer Rope (DBR) across all engineering projects at EngCo.
Context: Our engineering division, has a record amount of capital spend over the next five years for sustaining, improving and expanding the business. As an organisation, we are not very good at running our capital projects to deliver the full scope, on time and on or below budget. As the biggest asset in the business our division will lead the adoption of TOC, given its proven ability to deliver superior outcomes to any comparable method. For many years we have struggled to effectively use the pool of engineering resources we have in a way that does justice to the demand generated by both technical queries and capital projects.
Purpose: The purpose of this task is to secure the long-term benefits of using TOC as a competitive operating philosophy for our business.
Outcomes: The project will be run in accordance with the newly released corporate standard for projects and project management. The first phase, pre-feasibility, will require the following deliverables:
Resources: The following resources will be required to complete phase one of the work.
Timing: Whilst it is expected that EngCo will be able to achieve the quick wins achieved by most companies who adopt TOC, our intention is that this endeavour is for the long haul. We therefore expect the new TOC system of engineering management will be fully mature within the next three years. That is, the standard operating procedures will have been documented, and people will have been educated and trained to the level required by their roles. Online and class-based training will be available as well as a suite of quick reference guides (QRGs). We will have integrated our variety of vendors and business partners into our new ways of working and will be a learning centre of excellence for the broader Eng Holdings business.
In summary, at all levels of work, we have:
Context: How does this work fit in with the big picture?
Purpose: Why is this task or project necessary? What do you want to achieve with it?
Outcomes: You’re probably familiar with SMART objectives: Specific, Measurable, Ambitious, Realistic and Time-bound. (The A and R often stand for different things: achievable/agreed, say, or relevant/reasonable. The SMT are universal.)
Resources: What human, material, financial and information resources do you need to achieve the outcome you desire? How much estimated actual touch time, by resource?
Timing: If your outcome is SMART, timing will be included. But, how much calendar time will the work take. When will be required to finish it?
Like Jaques’s time horizon strata, the CPORT is also fractal; it works for everything from small tasks to large projects. So, the next time you’re briefing someone—even for a smallish task due, say, next week—ask yourself if you’ve been as clear about the context, purpose, outcomes and resources as you’ve been about the timing.
Making the CPORT standard procedure also encourages written requests. For small tasks, sent by email, you may decide you don’t need explicit CPORT headings. But do mentally check you’ve covered them. You’ll often discover you’ve been assuming too much on the part of your recipient. Much better to make your expectations clear than just chat it through and hope for the best. If you want a high-quality result, set yourself up for success at the outset.
____________________________
What’s next?
The change from standard thinking to Theory of Constraints (TOC) is both profound and exhilarating. To make it both fun and memorable, we use a business simulation we call The Right Stuff Workshop.
We’d love to run it with you. To learn more:
____________________________

[Background photo by Waldemar Brandt on Unsplash]
“Work as though you would live forever,
and live as though you would die today”
—Og Mandino
____________________________
Healthcare professionals are central to the patient’s progress from awareness of a therapy to successful long-term use. They identify risk, interpret evidence, diagnose conditions, discuss options, perform procedures, provide training and monitor outcomes.
Yet many medical device development programs treat healthcare professionals primarily as users to be trained or customers to be persuaded.
HCP-Centered Design takes a wider view. It examines the work healthcare professionals must perform, the system in which they perform it and the constraints that limit their ability to move suitable patients through the care pathway.
“If patient flow depends on a healthcare professional, that professional’s available capacity may determine how many patients ultimately receive the therapy.”
A medical device patient journey commonly depends on several healthcare professionals:
Each professional governs a transition in the flow of patients.
If one transition lacks sufficient capacity, information or clarity, the whole pathway slows. More marketing, sales activity or production capacity will not compensate for a shortage of specialist time or a burdensome diagnostic process.
This is why HCP-Centered Design is not simply about making an interface easier to use. It is about enabling the system of care to perform.
A healthcare professional’s work depends on information and actions supplied by others. They may rely on referrals, patient histories, pathology, imaging, electronic records, clinical guidelines and the availability of equipment or trained colleagues.
After reaching a decision, they may need to explain it, document it, arrange authorization, coordinate treatment and prepare the next person in the pathway.
A technically strong solution can still create difficulty if it:
The relevant design question is not merely, “Can the HCP use this product?”
It is, “Does this solution improve the HCP’s ability to complete important clinical work within the conditions in which care is actually delivered?”
“HCP” is not one persona.
A general practitioner, specialist, interventional physician, nurse, technician and clinical administrator encounter different stages of the pathway. Each has different responsibilities, authority, expertise and exposure to risk.
Even within a profession, context matters. An experienced specialist in a major hospital may approach the same task differently from a professional who encounters the condition infrequently or works without immediate specialist support.
Useful HCP personas distinguish factors that influence work:
These personas clarify who performs each job and what support each person requires.
The HCP journey often begins before the visible clinical procedure.
It may include receiving a referral, gathering information, forming an initial view, ordering investigations, interpreting results, deciding whether the patient is eligible, discussing treatment, obtaining authorization, preparing for the procedure, delivering care and arranging follow-up.
At each stage, ask:
The resulting journey map should distinguish processing time from waiting time. A decision may require only minutes of specialist attention while patients wait weeks to access that attention.
This reveals the practical relationship between HCP capacity and patient flow.
The Theory of Constraints directs attention to the factor limiting the performance of the entire system.
In some pathways, the constraint may be the number of qualified interventional specialists. In others, it may be diagnostic capacity, physician confidence, authorization effort, operating room access or the time required to train patients.
The constraint may also be hidden inside the HCP’s working day.
A specialist supporting a therapy must still manage other clinical duties, administration, meetings, documentation and urgent cases. The question is not simply how many specialists exist. It is how much of their usable capacity is available for the activities upon which patient flow depends.
“The scarcest resource may not be the healthcare professional. It may be the few hours of focused capacity available for the critical work.”
Improvement away from this constraint can make performance worse. Sending more referrals to an already overloaded specialist increases the queue. Adding information may increase cognitive burden. Creating another approval may consume the capacity required to treat patients.
HCP-Centered Design seeks to protect and expand the capacity that governs flow.
Policies and procedures describe how clinical work should happen. Observation reveals how it actually happens.
Healthcare professionals routinely compensate for missing information, awkward interfaces and unreliable handovers. These workarounds may become so familiar that nobody reports them as problems.
Gemba research should examine:
The purpose is not to judge the healthcare professional. It is to understand the system surrounding the work.
“A workaround is often evidence that the system has failed to support the person doing the work.”
Healthcare professionals do not simply use devices. They use them to make progress in clinical work.
An HCP may need to identify risk, reach a confident diagnosis, select an intervention, perform a procedure safely, explain options, monitor progress or recognize deterioration.
A structured job map divides this work into eight stages:
This wider view prevents the product team from concentrating exclusively on the procedure.
The greatest value may come from reducing preparation, improving decision confidence, clarifying an exception, simplifying documentation or improving the handover to follow-up care.
Comments such as “the interface is difficult” or “we need better information” indicate dissatisfaction, but do not provide sufficient direction for design.
They should be translated into measurable outcome statements, such as:
“Minimize the time required to identify which clinical information is missing before making a treatment decision.”
Or:
“Reduce the likelihood that a clinically significant change goes unrecognized between scheduled reviews.”
A broader population of healthcare professionals can then assess the importance of each outcome and their satisfaction with their current ability to achieve it.
Highly important and poorly satisfied outcomes provide a rational basis for prioritizing innovation.
“Adoption follows when a solution makes important clinical work safer, clearer or easier to complete.”
The five-step FOCUS process creates a practical improvement cycle.
Find the constraint. Determine which HCP activity or resource currently limits patient flow.
Optimise for it. Protect the constraint from avoidable work, missing information, interruptions and rework.
Collaborate around it. Align upstream and downstream teams so patients, information and resources arrive when required.
Uplift it. Add capacity, redesign responsibilities, improve technology or remove restrictive policies.
Start Again. Identify the new constraint once flow improves.
This approach allows the organization to distinguish activity from value. It also turns HCP engagement into an ongoing management discipline.
HCP-Centered Design must connect clinical reality with patient needs, technology, regulation and business strategy.
A Value Management Office can help coordinate these perspectives across the product lifecycle. Its role is to ensure that projects, resources and stage-gate decisions remain connected to patient flow and business value.
The organization should be able to show:
The goal is not simply a device that healthcare professionals can operate. It is a solution they can confidently incorporate into care and a delivery system capable of getting that solution to more patients.
Use the HCP-Centered Design assessment to determine how well your organization understands clinical work, HCP capacity and the constraints governing patient flow.
The resulting evidence should guide product design, process improvement and investment toward better products, delivered faster, with more lives changed for good.
Medical device companies devote enormous skill and investment to developing safe, effective products. Yet a technically successful device changes no lives while suitable patients remain unable to reach it.
Between a patient becoming aware of a therapy and receiving its intended benefit lies a pathway of referrals, consultations, diagnostics, approvals, procedures, training and follow-up. Every step consumes time. Between the steps, patients wait. At some points, they become confused, discouraged, ineligible or lost to the process.
Patient Centered Design must therefore address more than the design of the device. It must improve the performance of the entire system through which patients reach, receive and live successfully with the solution.
“A life-changing therapy changes no lives while patients remain trapped in the pathway leading to it.”
A typical medical device journey may include:
Companies often manage these stages as separate functions. Marketing works on awareness. Medical affairs supports clinicians. Market access addresses reimbursement. Sales works with specialists. Clinical teams gather evidence. Training teams support adoption.
The patient, however, experiences one journey.
From the patient’s perspective, a delay between two organizational functions remains a delay. A repeated test remains repeated work. An unclear handover creates uncertainty regardless of which department owns it.
Patient Centered Design begins when the organization sees and manages this journey as a connected system.
Every step contains some necessary processing time. A consultation takes time. A diagnostic test takes time. An authorization must be assessed. A procedure must be performed.
The patient’s total lead time, however, also includes the waiting between these activities.
A consultation may take 30 minutes, but the patient could wait six weeks for it. A diagnostic test may take an hour, followed by another delay before a specialist reviews the result. Prior authorization may require little actual work while adding weeks to the pathway.
This distinction matters because organizations often improve processing time while leaving the larger queues untouched. Saving five minutes during an appointment produces little benefit if the patient waits months to reach it.
Patient Centered Design therefore asks:
The answers reveal the true performance of the patient system.
Theory of Constraints teaches that the performance of any system is limited by a constraint. Improving a part of the system that is not constraining flow may create more activity without increasing results.
If diagnostic capacity is the constraint, generating more awareness may simply produce a longer queue for diagnosis. If specialist capacity is the constraint, accelerating authorization may move patients more quickly into another wait. If training after first use is inadequate, increasing procedures may produce poor experiences and avoidable follow-up demand.
“More activity at a non-constraint creates work in process. More capability at the constraint improves the system.”
The constraint is not always a physical resource. It may be a policy, an eligibility rule, missing evidence, a fragmented handover, an information delay or the cognitive burden placed on the patient.
The most important question is therefore not, “How do we improve every step?”
It is, “What currently limits the flow of suitable patients to successful use of the therapy?”
Numbers show where patients are lost. Patient research helps explain why.
Two patients with the same diagnosis may respond very differently. One may actively seek new treatment options. Another may delay action until symptoms become severe. A third may want help but lack confidence in navigating the healthcare system.
Meaningful patient segmentation considers characteristics that influence behavior:
These differences affect whether patients enter the pathway, remain engaged and successfully adopt the solution.
The Gemba is the place where work actually happens. For patients, this includes the home, clinic, hospital and all the places where they manage their condition between formal encounters.
Interviews alone may miss important evidence. People normalize inconvenience, forget workarounds and simplify their past decisions. Observation allows the development team to see what patients actually do.
Good research combines three activities.
Observe. Watch how patients obtain information, prepare, use the solution and respond when something goes wrong.
Immerse. Understand the physical, emotional and practical conditions surrounding the experience.
Engage. Ask open questions that allow patients to describe their goals, fears and frustrations in their own language.
The purpose is to discover the patient’s reality before asking them to evaluate the organization’s preferred answer.
Patients rarely want a medical device for its own sake. They want the progress it may enable.
They may want to recognize deterioration earlier, preserve independence, reduce pain, avoid repeated visits, return to work or prevent a disease from controlling daily life.
A useful job map examines eight recurring stages:
This reveals opportunities beyond the immediate use of the device. The most valuable improvement may involve helping patients prepare, confirm readiness, recognize an exception or understand what happens next.
Stories create understanding, but investment decisions require structured evidence.
Patient observations and comments should be converted into outcome statements that identify:
For example:
“Minimize the time required to recognize that my condition has changed sufficiently to require clinical help.”
Patients can then assess the importance of each outcome and their satisfaction with their current ability to achieve it.
Highly important and poorly satisfied outcomes represent genuine opportunities. This prevents teams from prioritizing attractive features that do not materially improve the patient’s life or progress through the pathway.
“Innovation becomes valuable when it improves an outcome that matters and remains poorly served.”
The Patient Centered Design pathway can be improved through a repeating discipline:
Find the constraint. Identify what currently limits patient flow or successful use.
Optimise for it. Make the best possible use of existing constraint capacity.
Collaborate around it. Align functions and partners so their actions support the constraint.
Uplift it. Add capability, remove restrictive policies or redesign the pathway.
Start Again. Once the constraint moves, identify and address the next limiting factor.
This prevents improvement from becoming a collection of disconnected initiatives. It directs scarce resources toward the factor that most strongly governs the result.
Patient insight should influence more than early product design. It should shape clinical evidence, regulatory strategy, reimbursement, manufacturing, education, market development and post-market support.
The organization should be able to show:
The goal is not simply to place the patient at the center of a diagram. It is to organize the enterprise around delivering better products faster, so that more lives can be changed for good.
Use the Patient Centered Design assessment to determine how well your organization understands its patient journeys, priority outcomes and constraints to patient flow.
The result should be more than another collection of patient opinions. It should provide evidence that directs strategy, investment and execution toward the changes that matter most.
Discover better ways to do better work.
We alternate our own actionable articles with three relevant links from other authorities.
We’ll only use your email address for this newsletter. No sales callsDiscover better ways to do better work.
We alternate our own actionable articles with three relevant links from other authorities.
We’ll only use your email address for this newsletter. No sales calls