绘制服务蓝图并定位流程断点
围绕单一服务场景串联客户动作、前后台与支持流程,形成断点分析、改进机会及验证计划。
完整提示词
<context>
You are a service designer. A service blueprint extends a journey map below the surface: under each customer step it shows what staff do in front of the customer (frontstage), what happens out of sight (backstage), the systems, policies and teams that support it, and the physical or digital evidence the customer sees. Three lines separate the layers: the line of interaction, the line of visibility and the line of internal interaction. A blueprint earns its keep by explaining why the experience breaks, which is almost always backstage: a handoff between teams, a system that does not share data, a policy written for another case. Blueprints go wrong when they cover every scenario at once, when they are drawn from a process manual instead of how work really happens, and when guesses look as solid as observed facts.
</context>
<task>
Build a service blueprint for this service.
<service>
{{service}}
</service>
{{#research}}
<research>
{{research}}
</research>
{{/research}}
If the service or scenario is too broad to blueprint as one path (for example "our whole hospital"), propose 2 or 3 specific scenarios and blueprint the most important one, saying which you chose. If no research is provided, build the blueprint as a hypothesis, tag everything as assumption, and make the validation plan the main deliverable.
1. **Scope.** The customer, the scenario, the trigger, the end point, the channels, and what is out of scope.
2. **Blueprint.** 6 to 14 customer steps in order. For each step fill the lanes: evidence (what the customer sees or receives), customer action, frontstage (people and interfaces the customer interacts with), backstage (staff actions out of view), support processes (systems, policies, third parties, other teams), and time taken where known. Mark failure points (F), waits (W) and decision points (D) on the steps where they happen.
3. **Failure points.** For each F: what goes wrong for the customer, the backstage or support cause, how often or how badly (from the research, or "unknown"), and the evidence.
4. **Handoffs and waits.** Every point where work passes between teams, systems or channels, and where the customer waits: who hands to whom, what information is lost or re-entered, and how long.
5. **Evidence and assumptions.** Tag each lane entry as observed (with source) or assumed. List the assumptions that matter most.
6. **Opportunities.** 3 to 6 improvements that fix causes, not symptoms, each naming the layer it changes (a screen, a staff action, a policy, a system integration), the failure point it addresses, and the team that would own it.
7. **Validation plan.** How to check the blueprint: shadowing frontline staff, walking the service as a customer, a workshop with the teams in each lane, data to pull.
</task>
<constraints>
- Do not invent metrics, team names, systems or staff behaviour; when unknown, write "unknown" or tag it as an assumption.
- Keep it to one scenario; note variants instead of branching the whole map.
- Do not blame individual staff; describe process and system causes.
{{> output/uncertainty}}
</constraints>
<output_format>
## Scope
## Blueprint
| Step | Evidence | Customer action | Frontstage | Backstage | Support processes | Time | Markers |
Lines of interaction, visibility and internal interaction are the borders between the Customer action, Frontstage, Backstage and Support columns; say so once under the table.
## Failure points
| Step | What goes wrong | Root cause layer and cause | Frequency or impact | Source |
## Handoffs and waits
## Evidence and assumptions
## Opportunities
| Opportunity | Layer changed | Fixes | Owner |
## Validation plan
</output_format>可替换内容
- {{service}}
- {{#research}}
- {{research}}
- {{/research}}
- {{> output/uncertainty}}
分类与标签
设计创意、服务蓝图、客户旅程、跨团队交接、服务验证