Designing for Experience

The design team meets in a conference room in Nashville. Eight consultants, a state health department director, two CMS representatives, and a facilitator with a whiteboard. The agenda reads “Community-Centered Transformation Design.” The room contains no one from a rural community.

The facilitator draws a diagram. At the center: “Patient.” Radiating outward: “Access,” “Quality,” “Coordination,” “Technology,” “Workforce.” The consultants nod. The CMS representatives take notes. The design will be patient-centered. It says so on the whiteboard.

Six months later, Loretta Whitaker in Claiborne County, Tennessee receives a letter informing her that her new care coordinator will be calling to schedule a wellness visit. Loretta does not know what a care coordinator is. She does not have a phone that receives calls reliably. She has been driving 52 miles to see the same doctor for eleven years, and the last time she went, the receptionist told her the practice was “transitioning to a new model” and handed her a tablet to complete an intake form. Loretta is 71 and has never used a tablet. She sat in the waiting room for twenty minutes pressing the screen before a medical assistant took it back and filled it in for her, asking questions Loretta did not understand about “social determinants” and “care goals.”

She drove home and told her neighbor she was not going back.

The Nashville conference room designed a patient-centered system. Loretta experienced something done to her rather than for her. The gap between design intent and lived experience is not a failure of execution. It is a failure of methodology. The system was designed by people who understand healthcare infrastructure. It was not designed by people who understand Loretta.

The Series 13 Synthesis documented four dimensions of experience that matter most to rural patients, trust, navigation burden, isolation, and dignity, and found that RHTP is least equipped to address them. This companion asks: how would transformation be designed differently if experience were the starting point rather than the evaluation metric?

Part I: Why Experience-Centered Design Is Not Patient-Centered Care

#

The Patient-Centered Confusion

#

Healthcare adopted “patient-centered” language two decades ago. The concept has been absorbed into policy requirements, quality metrics, accreditation standards, and organizational mission statements. Virtually every RHTP state application claims patient-centered design. The phrase has become so universal that it has lost specificity.

What “patient-centered” typically means in practice: clinical processes organized to be more convenient for patients. Shorter wait times. Patient portals. Care coordination. Shared decision-making tools. Survey-based satisfaction measurement. These improvements have value. They do not constitute experience-centered design.

The distinction is directional. Patient-centered care improves the system’s interface with the patient. Experience-centered design builds the system from the patient’s reality outward. The first adjusts what exists. The second constructs from what is needed.

Patient-centered care asks: how can we make this appointment easier for the patient? Experience-centered design asks: should there be an appointment at all, or should the interaction happen differently?

Patient-centered care asks: how can we reduce wait times? Experience-centered design asks: why is the patient waiting, and what system design would eliminate the conditions that create waiting?

Patient-centered care asks: how can we improve the patient portal? Experience-centered design asks: who decided a portal was the right interface, and what would the patient design instead?

Loretta does not need a better portal. She needs a system that knows she does not use tablets, does not understand “social determinants” language, and has built her healthcare around an eleven-year relationship with a physician she trusts. Experience-centered design starts from those facts. Patient-centered care starts from the system and works toward Loretta, arriving with a tablet and a letter about a care coordinator she did not ask for.

What Series 13 Revealed About the Gap

#

The four experiential dimensions documented in Series 13 are not implementation problems to be solved. They are design specifications to be met.

Trust is the precondition. Without it, nothing else works. Series 13A documented that rural distrust of healthcare institutions is rational, learned, and based on accumulated experience of institutional departure. Trust cannot be manufactured through communication strategies or engagement processes. It requires changed institutional behavior sustained over time: promises kept, presence maintained, power shared.

Design specification: any system element that cannot be sustained for at least a decade should not be introduced as permanent. Anything temporary should be explicitly labeled as temporary and include transition planning from day one.

Navigation burden is the tax the system imposes on patients. Series 13B documented that what institutions call “non-compliance” often reflects system design extracting more than patients can give: reliable transportation, flexible employment, digital literacy, administrative capacity. Prior authorization alone consumes 13 physician hours per week, with 79% of physicians reporting patients abandon treatment due to authorization barriers.

Design specification: every system interaction should be evaluated from the patient’s total cost perspective, including travel time, lost wages, cognitive load, and administrative complexity. If the interaction costs the patient more than the benefit it delivers, the interaction should be redesigned or eliminated.

Isolation is a community condition, not an individual symptom. Series 13C documented that social isolation carries mortality risk comparable to smoking fifteen cigarettes daily. Screening for isolation without capacity to address it performs documentation rather than care. The isolated elder who discloses loneliness and receives a referral to a closed senior center learns that disclosure is pointless.

Design specification: isolation interventions must operate at community scale, not individual scale. Building gathering places, maintaining institutions, creating reasons for connection. Clinical screening for a community condition is a category error.

Dignity is about who holds authority. Series 13D documented the distinction between being helped and being fixed. Deficit framing pervades transformation design: grant applications document what communities lack, research measures disparities, policy briefs compile statistics on absence. This framing positions communities as objects of intervention.

Design specification: communities must hold meaningful authority over what transformation looks like, what it prioritizes, and how success is defined. Advisory roles with no decision authority do not meet this specification.

Part II: Five Shifts in Design Methodology

#

Experience-centered design requires five methodological shifts from how RHTP transformation is typically designed. Each shift is specific, actionable, and challenging.

Shift 1: From Needs Assessment to Experience Mapping

#

Current methodology: States conduct needs assessments documenting health outcomes, provider shortages, infrastructure gaps, and population demographics. The assessment identifies problems the program will address. Problems are defined in system terms: shortage, gap, barrier, disparity.

Experience-centered alternative: Map what seeking and receiving healthcare actually involves for specific people in specific places. Not aggregate statistics. Individual journeys.

Follow Loretta through a healthcare interaction from the moment she recognizes a symptom to the moment the episode resolves or does not resolve. Document every step: the decision to seek care, the phone call, the scheduling, the transportation, the arrival, the intake, the waiting, the encounter, the departure, the follow-up, the medication acquisition, the next episode. At each step, note what worked, what did not, what required effort disproportionate to benefit, and what Loretta would change if she could.

This produces different intelligence than needs assessment. A needs assessment would identify that Claiborne County has a primary care provider shortage. Experience mapping reveals that Loretta has a provider she trusts 52 miles away, that the drive takes 80 minutes on mountain roads, that she must arrange the trip around her neighbor’s work schedule because her neighbor drives, that the visit costs a full day when accounting for preparation, travel, waiting, encounter, pharmacy stop, and return, and that she delays care because the total extraction exceeds what she can afford to give.

The needs assessment recommends recruiting a provider closer to Loretta. Experience mapping reveals that proximity is not Loretta’s primary constraint. Her constraint is the total cost of each healthcare interaction. A closer provider she does not trust may produce worse outcomes than a distant provider she does trust, because she will not go. Experience-centered design solves for total interaction cost, including the trust component, not just geographic distance.

Practical implementation: Train community health workers as experience mappers. CHWs recruited from the community understand the context that external assessors miss. Equip them with structured observation tools that document individual healthcare journeys. Aggregate individual maps into community-level experience profiles that inform design. Update maps annually as conditions change.

Shift 2: From Service Design to Friction Elimination

#

Current methodology: Transformation programs design services: telehealth platforms, care coordination programs, community health worker networks, behavioral health integration. Services are evaluated by whether they exist and whether people use them.

Experience-centered alternative: Identify every point of friction in the healthcare experience and systematically eliminate or reduce it. Friction is anything that makes healthcare harder to access, navigate, or benefit from than it needs to be.

Friction audit methodology:

Identify each interaction between patient and system. For each interaction, assess:

Is this interaction necessary? Some interactions exist because the system requires them, not because the patient benefits from them. Insurance eligibility verification, prior authorization, duplicate intake forms, unnecessary follow-up visits: each is friction that serves institutional needs rather than patient needs. Eliminate interactions that do not benefit the patient.

Could this interaction happen differently? The patient currently travels to the system. Could the system travel to the patient? The patient currently completes forms. Could someone complete forms on their behalf? The patient currently waits for appointments. Could the system respond when the patient is ready?

What does this interaction cost the patient? Not the copay. The total cost: time, travel, wages lost, childcare arranged, cognitive load invested, dignity expended. If the total cost exceeds what the patient can afford, the interaction either will not happen or will produce resentment that erodes trust.

Who benefits from how this interaction is currently structured? Honest friction audit reveals that many healthcare processes are designed for institutional convenience, regulatory compliance, or liability protection rather than patient benefit. The intake tablet in Loretta’s waiting room was efficient for the practice. It was a barrier for Loretta. Whose convenience should prevail?

Practical implementation: Conduct friction audits for each major healthcare pathway in the community. Prioritize eliminating frictions with highest patient cost and lowest institutional benefit. Track friction reduction as a primary transformation metric alongside clinical outcomes.

Shift 3: From Community Engagement to Community Authority

#

Current methodology: States conduct community engagement: town halls, listening sessions, advisory committees, surveys. Engagement documents community input. Programs incorporate what they can. Communities are informed of decisions.

Experience-centered alternative: Transfer meaningful design authority to communities. Not input. Authority.

The distinction is structural, not rhetorical. Community engagement asks communities what they think about plans designed elsewhere. Community authority gives communities control over plan design. The difference manifests in who sets the agenda, who allocates resources, who defines success, and who evaluates outcomes.

Authority models:

Community health boards with budget authority. Not advisory boards that recommend. Governance boards that decide. A community health board controlling 20% of local RHTP allocation directs resources toward priorities the community identifies rather than priorities the state assigns.

Community-defined success metrics. Federal programs measure what federal programs value. Communities may value different things. A community where trust in institutions has collapsed may define success as “providers who stayed longer than three years.” A community experiencing isolation may define success as “number of community gathering events per month.” These metrics may not appear in federal reporting requirements. Experience-centered design measures them anyway.

Design authority over delivery model. When the Nashville conference room decides that Claiborne County needs a care coordinator, the design flows from institutional logic about what transformation should include. When Claiborne County decides what it needs, the answer might be different: a community van that takes people to the trusted doctor 52 miles away, a nurse who comes to the senior center on Tuesdays, a pharmacist who delivers medications monthly. Communities know what would help them. The question is whether systems will let communities say so with authority rather than as input.

Practical implementation: Establish community governance structures with real authority over local transformation design. Define the scope of authority clearly: what communities control, what states control, what is negotiated. Provide communities with technical support (data, options, cost information) without providing communities with predetermined answers.

Shift 4: From Individual Intervention to Relational Infrastructure

#

Current methodology: Programs address individual patients through individual interventions: screenings, referrals, care plans, navigation. The unit of analysis is the person. The unit of intervention is the encounter.

Experience-centered alternative: Build relational infrastructure, the sustained human connections through which healthcare becomes trustworthy, navigable, and dignified.

Relational infrastructure has three components:

Continuity of person. Loretta’s eleven-year relationship with her physician is relational infrastructure. She trusts him because he has stayed. She follows his advice because she believes he understands her. She tolerates the 52-mile drive because the relationship justifies the cost. Programs that rotate personnel, cycle through grant-funded staff, and replace trusted individuals with new faces destroy relational infrastructure faster than they build clinical infrastructure.

Design specification: minimize personnel turnover in community-facing roles. Fund positions rather than projects. Create career pathways that allow community health workers, care coordinators, and primary care providers to remain in communities for decades rather than cycling through on three-year grant periods. The most important metric for relational infrastructure is tenure.

Community connectors. Some people in every community serve as informal health resources: the neighbor who drives people to appointments, the church member who checks on shut-ins, the school secretary who notices when children seem unwell. These connectors are not in any organizational chart. They are relational infrastructure that no program created and no program can replace.

Design specification: identify community connectors and support their work without formalizing it to the point of destroying what makes it effective. The neighbor who drives Loretta to appointments does so as a friend. Making her a “volunteer patient transportation coordinator” with documentation requirements and liability waivers transforms relationship into bureaucracy. Support connectors with resources (gas money, flexible schedules, training opportunities they request) while preserving the informal relationships that make them trusted.

Institutional memory. When the hospital closes or the clinic changes ownership, institutional memory of community health needs disappears. The new organization does not know that the trailer park floods every spring producing mold-related asthma, that the chemical plant three miles east produced elevated cancer rates in the 1990s, or that the community has distrusted the county health department since a botched water quality response in 2012.

Design specification: create community health memory systems, documentation of community health history, institutional relationships, trust dynamics, and local knowledge that persists across organizational changes. Community health workers who stay in communities are living memory. Written records, community health profiles, and relationship maps supplement individual memory with institutional durability.

Shift 5: From Deficit Documentation to Capacity Activation

#

Current methodology: Transformation design begins with documenting deficits: what communities lack, what populations suffer, what systems fail to provide. Grant applications require deficit documentation. Performance metrics measure deficit reduction. The entire orientation assumes communities are defined by what is wrong.

Experience-centered alternative: Begin with what communities have and build from existing capacity rather than importing solutions for documented deficits.

This is not toxic positivity. Rural communities face real deficits: provider shortages, infrastructure collapse, economic decline. Acknowledging these deficits is honest. But design that starts from deficit produces solutions that come from outside. Design that starts from capacity produces solutions that build on what exists.

Claiborne County’s deficits are real. It has a primary care provider shortage, limited broadband, no public transit, and declining population. Its capacities are also real. It has churches where people gather weekly. It has a school system with nurses and counselors. It has retired healthcare workers with clinical knowledge. It has Loretta’s neighbor, who drives people to appointments without being asked. It has community gardens producing food that no federal program supplied. It has mutual aid networks that functioned during COVID when formal systems failed.

Deficit-starting design imports a care coordinator. Capacity-starting design trains Loretta’s neighbor, supports the church gathering, equips the school nurse, and connects the retired nurse to a telehealth platform. The results may be similar. The experience is fundamentally different. One feels like being fixed. The other feels like being invested in.

Part III: What This Methodology Cannot Do

#

Honest Limits

#

Experience-centered design methodology does not eliminate the structural constraints the Series 13 Synthesis documented.

It cannot extend grant timelines. Trust requires sustained presence. RHTP provides five years. Experience-centered design can maximize what five years builds, but it cannot make five years sufficient for the generational trust-building some communities require.

It cannot reform payment systems. Navigation burden is largely produced by insurance structures, regulatory requirements, and administrative processes that RHTP cannot change. Experience-centered design can reduce friction within these structures. It cannot eliminate the structures.

It cannot reverse community decline. Isolation is a community condition produced by economic forces spanning decades. Experience-centered design can build relational infrastructure that mitigates isolation. It cannot restore the economic conditions that produced community cohesion.

It cannot redistribute authority. Dignity requires communities holding real power over how transformation occurs. Federal program architecture concentrates authority in agencies and institutions. Experience-centered design can create community governance within program constraints. It cannot override the hierarchical accountability that federal programs require.

These limits are real. They do not make the methodology pointless. They make it honest. Experience-centered design within structural constraints produces better outcomes than infrastructure-centered design within the same constraints. The constraints bind both approaches. The question is which approach produces transformation that communities recognize as help rather than as one more program that understood their problems accurately and solved them for someone else.

When This Methodology Is Not Appropriate

#

Not every transformation context calls for experience-centered design at full intensity.

Emergency stabilization requires speed, not methodology. Communities losing their last provider need immediate response. Design processes that take months to map experience and build governance cost time those communities do not have. Emergency response followed by experience-centered redesign is the appropriate sequence.

Infrastructure prerequisites precede experience design. Communities without broadband, roads, or basic utilities need infrastructure before experience methodology applies. You cannot design for how people experience telehealth when connectivity does not exist.

Some populations resist engagement. Not every community wants to participate in design processes. Communities with deep institutional distrust may view design methodology as one more program demanding their participation for someone else’s benefit. Respecting that resistance, building trust first, and offering design participation as an option rather than a requirement honors the autonomy that experience-centered design claims to value.

Part IV: The Design Room Revisited

#

The Nashville conference room could work differently.

Eight seats occupied by rural community members from the state’s target regions. Two consultants present as technical resources, answering questions rather than presenting frameworks. The state director listens. The CMS representatives observe.

The facilitator does not draw a diagram. She asks: “Tell us about the last time you needed healthcare. What happened? What worked? What did not? What would you change?”

Loretta describes the 52-mile drive, the tablet she could not use, the care coordinator she did not ask for, and the doctor she trusts because he stayed eleven years. A farmworker describes visiting three emergency departments in three states during one harvest season, starting the intake process from scratch each time. A veteran describes the VA telehealth appointment where the counselor could not see his face because the broadband connection kept buffering. A mother describes waiting fourteen months for her son’s autism evaluation, driving to Knoxville because no one closer could perform it, and returning home with a diagnosis and no local provider to act on it.

The room builds a different kind of design. Not infrastructure radiating from an abstract “Patient” at the center of a whiteboard. Transformation radiating from specific people in specific places with specific experiences that specific design choices could improve.

This is what experience-centered design looks like. Not a methodology imposed on communities. A methodology that emerges from communities. Not a framework consultants bring to conference rooms. A conversation that communities lead in their own spaces, on their own terms, producing designs that reflect their reality rather than someone else’s model of it.

The method is harder. The timelines are longer. The results are less predictable. The metrics are less standardized. The accountability is less hierarchical.

The transformation feels like help.