STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates
My previous article, The U Journey: Stepping into Design, introduced a key part of the Design phase—the Learning Journey. This includes developing and testing hypotheses, soliciting innovative ideas from wherever they might arise, exploring the psychological and cultural frontiers of your people and organisation, and trying on new ways of working.
The principle purpose of the learning journeys is to create conditions that reduce the anxiety associated with change so the people charged with bringing the new into the world can have a safe space in which to practice the mantra ‘fail often to succeed sooner’.
[Listen to audio version, read by David Hodes]
This is Part 5 of our series on The U Journey: Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6 | Part 7 | Part 8
The evolving trend toward design thinking demands that—whatever your imagined future reality—you pay particular attention to the people you’re hoping will use your product or service. They may be your own staff, your customers or any other stakeholder you need to influence favourably with regard to the change you are trying to bring into the world. Engaging them in its development—and inviting them to participate in its design and testing—will make all the difference to that change’s ultimate success. For it is never easy to bring about change. Most people prefer the certainty of current reality over the risk attached to stepping outside the walled garden and into the wild frontier—often with wilful disregard for how sterile or tyrannical the garden has become.
“If you’re not part of the problem,
you can’t be part of the solution.”
Furthermore, as individuals and collectively, there is often shame and pain associated with letting go of the past. Real change demands fronting up to culpability for the inevitable errors made. The road more frequently travelled has us sitting in judgement of others and failing to truthfully answer the question of how every one of us has some degree of responsibility for having got us to the place in which we find ourselves, and at least a degree of accountability for developing and executing a plan to get out. We must ask what kind of courageous leadership it will take to hold a mirror up to self, team and organisation and accept the systems thinking truism: ‘If you’re not part of the problem, you can’t be part of the solution.’
A visit to another organisation as outlined in my last article is a powerful way of escaping the gravitational pull of your organisation’s existing worldview and opening up the possibility for something new to emerge.
Communicating the work
Once you have clarity on what you want to accomplish in your exchange, think how you’ll communicate this to your hosts in advance. This may be a written document or a slide deck. Even better, you could use more innovative means now that anyone with a computer, a camera and a microphone can produce a video. At a minimum, you should cover off the following topics:
Context: Let them know as much as you’re willing to share about your organisation, the history of the initiative you are working on, the change you wish to bring about, and how you believe an exchange between you and them will add value for both parties.
Purpose: Be specific on the ‘why’ of the exchange. What is most meaningful about what you are setting out to do with them? What is the potential of the exchange if fully realised, and how much poorer would you each be if it was not to occur at all?
Outcomes: What are the specific outcomes you are looking for, such as plant tours, meetings with people from the executive suite to the shop floor, insights into how technology is being used and so on? Also, what will be the outputs from the visit? Will you take pictures and videos, do interviews, write journals, do some detailed analytics, study process differences? The clearer your desired outcomes—the more specific the better—the more likely the exchange will be a success.
Resources: Careful consideration of the resources required for the exchange will significantly enhance the chances of success. Think of logistics such as flights, local transfers, accommodation and meals. What kind of venues will you need for your exchanges? Meeting rooms, conference rooms, digital projectors, whiteboards. Also, be specific about whom you want to meet, in what kind of forum, and for how long. When it comes time to reciprocate, be sure that you have all the questions answered for the return trip.
I strongly recommend you make a single person accountable for project managing the whole exchange. They should have a counterpart in the host organisation; between them, they assign to the other participants accountability for the different aspects of the work that go into making the exchange a success.
At the host’s location
Once on site, be sure to use deep listening as a tool to hold the space of the conversation. Begin by bringing their story and yours into the room. Not simply your work story, but something of who you are, where you come from, what you studied, what the big turning points have been in your life, and what inspires you. What is meaningful about what you are trying to achieve and how the world would be poorer if you didn’t do it to the best of your ability.
In addition to the questions mentioned on the previous article, here are some additional avenues to explore:
The Big Idea: What’s your goal? What big idea are you pursuing to help you achieve it?
Strategy: By what means do you go about addressing the key strategic questions: What to change? What to change to? And how to change?
Innovation: How do you apply your organisation’s knowledge to deliver additional value and wealth?
Technology: How has all the technology you use shaped the business you are in? How could you improve the value delivered by your existing suite of technologies? What technology trends do you see having a major impact in your business and industry going forward?
People: How do you inspire and empower your people to be the best they can be in service of the greater good? What emphasis do you place on autonomy, learning and transcendent purpose as levers of motivation?
Process: What efforts have been undertaken to engineer simple standard processes? What systematic means do you have in place to ensure continuous systemic improvement?
Culture: What active steps are taken to cultivate a winning culture? What has been done to understand, codify and develop the shared assumptions and behaviours of your team to work together energetically toward a common goal?
Language: What are the verbal, written, visual, aural and bodily ways by which meaning is made in your organisation—from performance dashboards to office layouts and from project reporting to health and safety routines?
Organisation: By what means do you match accountability with authority at all levels of work, so your people can feel ownership and take pride in all that they do?
Resources: How do you know that you have the right amount of human, material, financial and information resources required to turn your intention into reality?
Operations: What constraints prevent you achieving more from your resources in and across time and place? What theories, methods and tools do you use to know that you’re right? How do you go about the business of continuous improvement?
Reflections after the visit
To capture and leverage the findings of your inquiry, conduct a disciplined debriefing process immediately after each visit. Don’t get distracted by cell phones or anything else until the debriefing is complete.
Here are a few sample questions for the debriefing, taken from Otto Scharmer’s insights:
1. What struck me most? What stood out?
2. What was most surprising or unexpected?
3. What touched me? What connected with me personally?
4. If the living system of the visited organisation were a living being, what would it look and feel like?
5. If that being could talk: what would it say (to us)?
6. If that being could develop—what would it want to morph into next?
7. What is the generative source that allows this living system to develop and thrive?
8. What limiting factors prevent this living system from developing further?
9. Moving in and out of this system, what did you notice about yourself?
10. What ideas does this experience spark for possible prototyping initiatives that you may want to take on?
Closing the loop
Be sure to share your gratitude and relevant findings with your hosts. Give them the benefit of some key insights you took away from the visit. If you suggested a reciprocal visit, be sure to honour that commitment.
As the group who had the privilege of undertaking the learning journey, convene as soon as possible to determine how you will present your findings to the broader change initiative. Get everyone on the same page so they know where you went, whom you talked to, what you did and how it has changed or reinforced your thinking.
Open the conversation from your findings into one which generates new ideas for redefining what’s possible for your own bold initiative.
____________________________
This article is Part 5 of our series on The U Journey.
Part 1: How to change: Introducing Theory U
Part 2: Preparing for the Foundation Workshop
Part 3: Running the Foundation Workshop
Part 4: Stepping into Design
Part 5: Wisdom from outside your domain
Part 6: Retreat and Reflect
Part 7: Crystallise Intent
Part 8: Deliver
____________________________
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 Jorik Kleen on Unsplash]
“You don’t learn to walk by following rules.
You learn by doing, and by falling over.”—Richard Branson
____________________________
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