STAY CONNECTED AND SIGNUP TO RECEIVE INSIGHT updates
The latest in our series that uses the ‘book review’ format as a springboard into a wider conversation about the world of work—and how to do it better.
One Mission by Chris Fussell
____________________________
It’s become fashionable to rail against hierarchy and to assume that people, once energised by their mission, can organise themselves into structures which are flat—at least in intent. But as with the flat-earthers, facts get in the way. Not only do we each have different cognitive capacities, we have different modes of thinking about complexity and the time horizon we can comfortably operate at. The essential question is: How do you get the speed that comes from allowing autonomous action, but maintain coordination and control?

You can’t simply wish away bureaucracies; they fulfil too vital a purpose. Someone has to make decisions, and the power to do so rests within a nested hierarchy. Whether you like them or not, hierarchies are a feature of nature itself and, rather than think of them as always being malevolent and tyrannical, most often they are based on competence and necessity. To avoid the chaos that attends anarchy, we need rules of engagement, lines of accountability and matching levels of authority.
Until I read General Stanley McChrystal’s ground-breaking book, Team of Teams, I felt that every new fad proposed by the supposed gurus of organisational design just didn’t pass muster against the rigour developed by Dr Elliott Jaques with his Stratified Systems Theory and associated book Requisite Organisation. Besides his theory about the three-way correlation between cognitive ability, time-horizon of work and complexity, he also developed a means by which management accountability could be exercised both functionally and cross-functionally.
The means of addressing the accountability hierarchies were contained in the idea of TARRs and TIRRs. A TARR is a Task Assigning Role Relationship in which a manager can assign work to a subordinate by virtue of their position in the overall management accountability hierarchy—they are in the same silo. A TIRR is a Task Initiating Role Relationship in which a manager in a ‘collateral’ function can have differing degrees of authority over resources in another silo by virtue of declared rules. The conception of these relationships is contained in the tables below.
Task Assigning Role Relationships (TARR)

Task Initiating Role Relationships (TIRRs)

The trouble with this schema is that whilst it provides a necessary condition for understanding how an overall accountability hierarchy might function effectively—all the way from the front-line worker, through all hierarchical layers and functional silos, up to the unifying role of the CEO—it cannot move fast enough to accommodate the tempo of our modern competitive environments.
Chris Fussell was the aide-de-camp to General McChrystal during the counter-insurgency war in Iraq, a role which he describes as equivalent to a chief-of-staff in private enterprise. His book, One Mission, follows on from where McChrystal’s Team of Teams leaves off. I knew when I first read McChrystal that there was something profound in his ideas. Here was an organisation—the Joint Operations Command of all special forces in Iraq—reinventing how to get the best of bureaucratic command and control to work with the speed and adaptability of a networked organisation. They had made virtue of the necessity of moving faster than their Al Qaeda in Iraq enemy whilst bringing to bear the fearsome organised power available to the coalition forces.
Two observations stayed with me after reading Team of Teams: the degree to which Taylorism and its bureaucratic tropes had been perfected in the US military and how radical transparency and subsidiarity (devolving decision making powers to the lowest level competent to make those decisions) were used to re-energise it.
In One Mission, Fussell provides a good first cut of how a team of teams actually operates and how to go about building one. With easy-to-follow chapters, each major section has a case study to illustrate how the principles learned on the battlefield can be applied across a wide variety of industries—from software (Intuit) to merchandise (Under Armour) and from public services (Medstar) to financial services (Eastdil Secured).
In the context of the war in Iraq, McChrystal’s Joint Special Operations Command (JSOC) had to integrate the highly tribalised special forces, each with their fierce loyalty to their unit—be they Green Berets, Rangers, Navy SEALs, Delta Force and others. In addition, they had to integrate their activities with the CIA, the State Department, the FBI, all branches of the US Department of Defense, the Department of Homeland Security, and a host of other national and international entities and agencies. That they were able to achieve one mission under these circumstances proved to me that the lessons to be learned had to be relevant to any large complex organisation trying to find a new paradigm for managerial leadership in this digital age.
Building alignment through a sense of connection to the mission, echoing my own understanding of Senge’s idea of a ‘shared vision’, was the first order of business. This mission found its expression in the simple equation of what Fussell describes as their aligning narrative—the story each of the disparate teams tells themselves to transcend the tightly held, but more narrowly constructed narrative of their home unit:
Credibility = Proven Competence + Integrity + Relationships
This simple-sounding formulation of the aligning vision is repeated throughout the book and acts as a powerful anchor for everything built around it. Regardless of whom you are dealing with—be it Al Qaeda in Iraq or the President of the United States—you get to be credible by proving your competence, being true to your word and constantly cultivating strong relationships.
In developing his theme of the hybrid organisation—which is to maintain the best of what a necessary bureaucratic structure has to offer with the agility and connectedness of a network—Fussell introduces the idea of an ‘information pump’. Information is always a critical resource in any enterprise, and goal accomplishment is often tied to how fast and efficient is its flow. He quotes Duncan Watts, a network theorist, in answering the puzzle of what a manager actually produces:
The answer, from an information-processing point of view, is that a manager’s principal task is not production at all, but coordination, to serve as an information pump between the individuals whose task is production.
The rest of the book is ultimately about how to debottleneck the flow of information through an organisation so that people can take empowered action with a shared consciousness of any given situation. He starts with the introduction of the idea of people who act as ‘boundary spanners’ between their organisational or functional silo, spanning the divide to adjacent functions or even far-off organisations who all share the same mission. These boundary spanners are not usually identifiable in the hierarchy described by the org chart, but are those ‘go to’ people everyone knows as the ones who know how things actually work.
Priming the information pumps
A critical element of the team of teams idea is to ensure that the cadence of communications runs at a pace at least equal to the rate at which the external environment is changing. In the case of the war in Iraq, this meant daily. And here’s the truly staggering change in thinking—these daily 90-minute video connections called Operations and Intelligence (O&I) forums would have as many as seven thousand people on them. How, I wondered, could you actually fight a war when the majority of the people fighting it were tied up in a one-and-a-half-hour meeting every day? And, perhaps even more remarkably, all the information was shared on the video-conference with no holds barred. I was astounded by the transformation that must have occurred in such a huge military organisation where the ‘need to know’ mantra would have been bred deeply into the bones.
How, I wondered, could you actually fight a war
when the majority of the people fighting it were tied up
in a one-and-a-half-hour meeting every day?
Those meetings removed the information pumps as the bottleneck to a shared consciousness of the whole theatre of war in Iraq. I found the phrase ‘shared consciousness’ unusual for a military organisation, associating it more with revolutionary political environments. The point is, though, that once different operating units understood the whole, they could act in a way that served the greatest possible good for their mission. This modus operandi meant that spending 90 minutes across the entire network of stakeholders to establish a shared consciousness left 22.5 hours every day for empowered execution. How many hours a day, I was left wondering, are wasted in the more normal work organisation trying to get the information pumps working at a rate capable of delivering even a fraction of the shared consciousness the team of teams approach delivers?
An O&I is a virtual space wherein an organisation’s leadership can create, with the required regularity, conditions for the organic interaction of all of its teams, and reiterate an aligning narrative to the assembled organisation. It is a regular reminder of purpose and an opportunity to reconnect with the larger tribe.
Fussell goes on to describe in some detail the idea of ‘decision space’ and its importance in defining for commanders what they could and could not do in the periods of empowered execution between the O&I events. This clarity around decision space meant that real autonomy could be exercised during the empowered execution phase within a team or across the whole organisation, without the need to refer all the way back up the hierarchy and down again. With the team of teams in place, the increase in the number of missions being run was staggering, leaping from ten raids per month in the early days to more than three hundred by 2006. But having to exercise autonomy was not so easy:
Real empowerment, when supported with the correct access to information and the necessary authority to make decisions, can be a lonely place. Properly empowered leaders and teams no longer have the bureaucratic excuse matrix to fall back upon, a luxury most will not realise they depend on until it’s gone.
Another critical piece in the puzzle was the appointment of liaisons. This might seem like a quite normal activity to undertake when spanning a large organisation or having to represent your home organisation in a key stakeholder’s organisation. It’s akin to what ambassadors do for the countries they represent. But ambassadors are career posts. The difference in a team of teams is that the liaisons were drawn from the very best ‘active duty’ folk in each unit. A tough call to ask any leader to give up their best and brightest to an ambassadorial role.
Unless liaisons are selected from amongst candidates equipped to seamlessly represent your senior leadership, their utility is limited, and they may be counter-productive.
Liaisons are different from boundary spanners. The latter remain in their home unit and are valued for what they know about ‘how things get done around here’. Liaisons, though, are selected by the highest level of leadership to represent the home organisation in a key stakeholder’s organisation. Their role is to credibly convey to each party what the thinking is of the other so that all can function without any of the critical nuances being lost in translation.
The whole system is summarised in the diagram below, which provides a remarkably simple conceptualisation of a revolution in the way we conceive of how we lead and manage bureaucracies and networks. You start with a common purpose—such as destroy Al Qaeda in Iraq, double EBIT within five years or become number 1 or 2 in any market you serve.

These goals operate at the strategic, operational and tactical levels at any given moment in time. At time t1 there are all the meetings and rituals devoted to developing shared consciousness. The time between t1 and t2 is for empowered execution. At time t2, it is time again to reconvene and develop a shared consciousness around what has just transpired and how you are going to address it. During the period of empowered execution, the decision space is set out (the large arrow), with clear guidance on the necessary conditions required for you to act using your own judgement and discretion—what you do and what you don’t do.
In summary, I find the whole idea of a team of teams the most interesting innovation in managerial leadership since Elliott Jaques developed stratified systems theory and published Requisite Organization. The courage required to embrace such a radical departure from our existing norms would make most CEOs I know run a mile. But I am certain that what McChrystal led in the heat of battle—and what Fussell has written about in One Mission—represents the start of something completely new in the field of organisational design and effectiveness.
____________________________
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:
____________________________
‘The object of any component is to contribute its best to
the system, not to maximise its own production. […]
Some components may operate at a loss themselves in
order to optimise the whole system’—W Edwards Deming
____________________________
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.

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