Service Blueprint Session Record

Template Overview

Delivering seamless digital experiences requires tight alignment between what users see and what back-stage systems execute. The Service Blueprint Session Record maps customer interactions, visible touchpoints, behind-the-scenes staff processes, and technical infrastructure in structured Markdown.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Service Blueprint: [Service or Product Workflow]"
date: [YYYY-MM-DD]
session_facilitator: "[[Service Designer / Architect]]"
service_scope: "Local Model Download & Vault Initialization"
participating_teams: ["Product Design", "Core Engine", "QA Engineering"]
blueprint_version: "v1.2"
tags: [service-design, blueprint, systems-architecture, operations]
---

# Service Blueprint Session Notes — [Service or Product Workflow]

## 1. Blueprint Scope & Customer Journey Phase
- **Target User Journey:** New user downloads Oyma, verifies privacy guarantees, downloads a local Whisper model, and initializes their offline vault.
- **Line of Visibility:** Clear boundary separating customer-facing UI from local background daemons and file system operations.

## 2. Multi-Tier Blueprint Architecture
| Layer | Phase 1: Onboarding | Phase 2: Model Setup | Phase 3: Live Recording | Phase 4: Vault Export |
|---|---|---|---|---|
| **Customer Actions** | Opens app, clicks Start | Selects Whisper model | Clicks record, speaks | Reviews Markdown note |
| **Front-Stage Touchpoints** | Welcome dialog, permission prompt | Model selection cards with RAM badges | Real-time waveform, timer | Formatted note preview |
| **Line of Visibility** | *--- Boundary ---* | *--- Boundary ---* | *--- Boundary ---* | *--- Boundary ---* |
| **Back-Stage Processes** | macOS TCC microphone entitlement query | Check available disk space & RAM | Stream CoreAudio buffer into ring buffer | Apply Markdown template AST |
| **Support Systems** | Apple Silicon Neural Engine detection | Hugging Face model cache (first download only) | Local whisper.cpp engine execution | macOS POSIX filesystem write |

## 3. Operational Pain Points & System Frictions
- **Fail-Safe Gap:** If a user runs out of disk space during model download, the UI currently hangs rather than returning a clean storage error.
- **Remediation:** Introduce a preliminary disk capacity check before initiating HTTP stream.

## 4. Cross-Functional Dependencies
- **Core Engine Team:** Expose storage telemetry API to the frontend Electron / native client.
- **UX Design Team:** Design an empty state screen with explicit disk space requirements.

## 5. Architectural Recommendations
> [!IMPORTANT] System Architecture
> Decouple model downloading from vault initialization so users can explore existing Markdown templates while background downloads complete.

## 6. Action Items
- [ ] Draft engineering RFC for asynchronous model download queue.
- [ ] Document fallback user flows for low-memory Mac configurations.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Service Blueprint: Local Meeting Workflow"
date: 2026-10-08
session_facilitator: "[[Devin Zhao]]"
service_scope: "End-to-End Local Meeting Recording"
participating_teams: ["Core Systems", "Product Design"]
blueprint_version: "v2.0"
tags: [service-design, systems, architecture]
---

# Service Blueprint Session Notes — Local Meeting Workflow

## 1. Session Summary
Devin Zhao facilitated a cross-functional service blueprint session aligning the Core Systems team and Product Design on the local audio pipeline.

## 2. System Decoupling Consensus
The team agreed that audio buffering must operate on an isolated high-priority thread to prevent dropped audio packets if the UI thread encounters heavy garbage collection during note rendering.

When to Use and When to Avoid

When to Use

• Use when mapping complex end-to-end services requiring coordination between frontend UI and back-end systems.
• Use during major system re-architectures or platform migrations.
• Use to identify single points of failure across operational and technical handoffs.

When to Avoid

• Avoid using for small visual tweaks or simple single-button design reviews.
• Avoid using when evaluating purely aesthetic design components in isolation.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the service blueprint workshop notes:
1. Map customer actions against front-stage touchpoints, back-stage processes, and support infrastructure.
2. Highlight operational vulnerabilities, friction points, and cross-team dependencies.
3. Generate a structured Markdown service blueprint table with prioritized action items.

Your data remains securely on your Mac with zero cloud exposure.