digital-health-ux-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- This source file is part of the Stanford Spezi open-source project. SPDX-FileCopyrightText: 2026 Stanford University and the project authors (see CONTRIBUTORS.md) SPDX-License-Identifier: MIT -->
<!-- 本源码文件是斯坦福Spezi开源项目的一部分。 SPDX-FileCopyrightText: 2026 斯坦福大学及项目作者(详见 CONTRIBUTORS.md) SPDX-License-Identifier: MIT -->

UX Planner

UX 规划指南

Plan user experience flows for digital health products without assuming a specific client technology.
为数字健康产品规划用户体验流程,无需依赖特定客户端技术。

When to Use

适用场景

Use this skill when you need to:
  • design end-to-end journeys for patients, participants, clinicians, or coordinators
  • plan onboarding and consent-adjacent flows
  • structure recurring health tracking or task completion workflows
  • think through engagement, motivation, and accessibility
当你需要完成以下工作时,可使用本技能:
  • 为患者、参与者、临床医生或协调人员设计端到端旅程
  • 规划引导流程及知情同意相关流程
  • 构建重复的健康追踪或任务完成工作流
  • 考量用户参与度、动机及可访问性

Working Style

工作原则

Begin with the people, decisions, and moments that matter. Do not start with screens.
Clarify:
  1. primary users
  2. core jobs to be done
  3. highest-friction moments
  4. what users need to understand, decide, or complete
  5. what success looks like for both the user and the program
从用户、关键决策和重要时刻入手,而非从界面屏幕开始。
明确以下内容:
  1. 核心用户
  2. 核心待完成任务
  3. 最高摩擦点
  4. 用户需要理解、决策或完成的内容
  5. 用户与项目双方的成功标准

Planning Framework

规划框架

1. User Segments

1. 用户细分

Identify:
  • primary users
  • secondary users
  • staff or caregiver roles
  • user constraints such as health literacy, accessibility needs, fatigue, or limited time
明确:
  • 核心用户
  • 次要用户
  • 工作人员或护理人员角色
  • 用户限制条件,如健康素养、可访问性需求、疲劳或时间有限

2. Core Journeys

2. 核心旅程

Map the main flows in plain language, for example:
  • discover and enroll
  • learn what the product is for
  • provide consent or required acknowledgements
  • complete the first meaningful task
  • return for ongoing use
  • review progress or history
  • get help or recover from confusion
用平实语言梳理主要流程,例如:
  • 发现并注册
  • 了解产品用途
  • 提供知情同意或必要确认
  • 完成首个有意义的任务
  • 回访持续使用
  • 查看进度或历史记录
  • 获取帮助或解决困惑

3. Onboarding

3. 引导流程

Plan what users need at the beginning:
  • orientation and trust-building
  • account setup if applicable
  • permissions or access requests only when needed
  • profile or baseline setup
  • first action that creates value quickly
Challenge any onboarding flow that asks for too much too soon.
规划用户初始阶段所需内容:
  • 产品介绍与信任建立
  • 账户设置(如适用)
  • 仅在必要时请求权限或访问权限
  • 个人资料或基线设置
  • 能快速创造价值的首个操作
对任何要求用户过早提供过多信息的引导流程提出质疑。

4. Day-to-Day Workflow

4. 日常工作流

Describe the recurring experience:
  • what prompts the user to return
  • what they see first
  • what they are expected to do
  • how completion and progress are communicated
  • what happens when they skip, fall behind, or lose context
描述重复使用时的体验:
  • 触发用户回访的因素
  • 用户首次看到的内容
  • 用户需要完成的操作
  • 如何告知用户任务完成情况与进度
  • 用户跳过、落后或失去上下文时的处理方式

5. Engagement Strategy

5. 用户参与策略

Consider:
  • reminders
  • summaries
  • milestone feedback
  • streaks or encouragement, if appropriate
  • how to avoid manipulation, shame, or alert fatigue
考量以下内容:
  • 提醒机制
  • 内容摘要
  • 里程碑反馈
  • 连续使用奖励或鼓励(如适用)
  • 如何避免操纵、羞耻感或提醒疲劳

6. Accessibility and Inclusion

6. 可访问性与包容性

Review:
  • readability and plain language
  • color contrast and visual hierarchy
  • support for assistive technologies
  • cognitive load
  • language, cultural, and trust considerations
审查以下方面:
  • 可读性与平实语言
  • 色彩对比度与视觉层级
  • 辅助技术支持
  • 认知负荷
  • 语言、文化与信任相关考量

Deliverable Format

交付格式

Produce a concise UX planning brief with:
  • primary user segments
  • top user journeys
  • onboarding strategy
  • recurring workflow design
  • engagement principles
  • accessibility and inclusion notes
  • unresolved risks or UX questions
Save the brief as
docs/planning/ux-brief.md
in the project repository.
生成一份简洁的UX规划简报,包含:
  • 核心用户细分
  • 主要用户旅程
  • 引导策略
  • 重复工作流设计
  • 用户参与原则
  • 可访问性与包容性说明
  • 未解决的风险或UX问题
将简报保存至项目仓库的
docs/planning/ux-brief.md
路径下。

Guardrails

约束规则

  • Do not assume mobile tabs, specific screens, or platform conventions unless implementation context requires it.
  • Prefer user goals and decision points over UI inventories.
  • Keep trust, burden, and accessibility central.
  • Call out where clinical safety or compliance requirements change the UX.
  • 除非有明确的实现上下文要求,否则不要假设使用移动端标签、特定屏幕或平台惯例。
  • 优先考虑用户目标与决策点,而非UI组件清单。
  • 始终将信任、用户负担与可访问性放在核心位置。
  • 明确指出临床安全或合规要求对UX产生影响的地方。

Checklist

检查清单

  • User segments identified
  • Core journeys mapped
  • Onboarding scoped to the minimum necessary steps
  • Day-to-day workflow defined
  • Engagement strategy reviewed for burden and ethics
  • Accessibility and inclusion considerations captured
  • Major UX risks and open questions documented
  • 已明确用户细分
  • 已梳理核心用户旅程
  • 引导流程已限定为必要的最少步骤
  • 已定义日常工作流
  • 已审查用户参与策略的负担与伦理问题
  • 已记录可访问性与包容性考量
  • 已记录主要UX风险与待解决问题