> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://blueprint.ziro.health/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://blueprint.ziro.health/_mcp/server.

# Stakeholder Map

## Overview

Health products serve a complex ecosystem of stakeholders — often with competing needs, priorities, and constraints. Successful health products design for the entire ecosystem, not just the end user.

***

## Primary Stakeholders

### Patients

The most important stakeholder. Patients are the ultimate beneficiaries of health technology, but they are not a monolith.

**Needs**: Accessible care, understanding, convenience, trust, affordability
**Constraints**: Health literacy, emotional state, physical limitations, financial resources
**Design implications**: Empathetic UX, plain language, accessibility, transparent data practices

### Clinicians & Providers

Clinicians are both users and gatekeepers of health technology. If a tool doesn't fit their workflow, it won't be used.

**Needs**: Efficiency, accuracy, clinical decision support, minimal documentation burden
**Constraints**: Time pressure, cognitive load, EMR fatigue, liability concerns
**Design implications**: Keyboard-optimized workflows, at-a-glance dashboards, EHR integration

### Caregivers

Family members and professional caregivers who support patients outside clinical settings.

**Needs**: Coordination, visibility into patient status, communication with care team
**Constraints**: Emotional burden, fragmented information, their own time constraints
**Design implications**: Shared access models, notification preferences, emergency contact flows

### Healthcare Administrators

Hospital and practice administrators responsible for operations, compliance, and financial performance.

**Needs**: Workflow efficiency, compliance, reporting, cost reduction
**Constraints**: Budget, legacy system dependencies, staff training burden
**Design implications**: Admin dashboards, audit reports, role-based access

### Payers (Insurers)

Insurance companies, self-insured employers, and government health programs.

**Needs**: Cost reduction, outcome improvement, risk management
**Constraints**: ROI requirements, regulatory compliance, member privacy
**Design implications**: Outcomes measurement, risk stratification, value-based care alignment

***

## Secondary Stakeholders

| Stakeholder                  | Interest                              | Engagement Strategy                                 |
| ---------------------------- | ------------------------------------- | --------------------------------------------------- |
| Regulators (FDA, EMA, etc.)  | Safety, efficacy, compliance          | Build compliance by design, prepare for submissions |
| Health IT departments        | Security, integration, supportability | Provide integration guides, security documentation  |
| Research institutions        | Data access, clinical evidence        | Offer de-identified data exports, IRB support       |
| Pharmacies                   | Prescription fulfillment              | Integration with pharmacy systems                   |
| Labs                         | Test ordering and results             | HL7/FHIR lab interface                              |
| Medical device manufacturers | Device data integration               | Support device connectivity standards               |

***

## Stakeholder Conflicts & Resolution

Common tensions arise between stakeholder needs:

| Conflict                                                  | Resolution Strategy                                       |
| --------------------------------------------------------- | --------------------------------------------------------- |
| Patient wants simplicity, clinician wants depth           | Role-based interfaces with progressive disclosure         |
| Provider wants data collection, patient wants privacy     | Transparent consent flows, granular data sharing controls |
| Payer wants cost reduction, user wants premium experience | Value-based design that aligns outcomes with satisfaction |
| IT wants security, users want convenience                 | Passwordless MFA, SSO, contextual security                |

***

## Designing for Multi-Stakeholder Systems

Identify every person and organization that touches your product. Include indirect stakeholders

What is each stakeholder trying to accomplish? What does success look like for them?

Where do stakeholder needs conflict? These are your highest-risk design challenges

The stakeholder with the least power often suffers the most from bad design. Prioritize their experience

Don't just test with patients. Test with clinicians, administrators, and caregivers too

***

## Related Chapters

* [Patient-Centered Design](/design-patterns/patient-centered-design) — Designing for the primary stakeholder
* [Service Design](/product-lifecycle/service-design) — Designing multi-stakeholder journeys
* [Payer & Provider Sales](/business-gtm/payer-sales) — Selling to institutional stakeholders